A solid foundation
Design the handover too
Before building, agree who is the hosting customer, who manages the domain and who makes changes after delivery. A technically excellent website can still be hard to hand over when licences, accounts and billing are unclear.
Prepare a short handover list with plugins, licence owners, important integrations and backup locations. Give clients access matching their agreed responsibilities and avoid a shared password for several people.
Make changes repeatable
Check a change in a separate test environment first if one is available. Record which version you are changing and what you test: navigation, forms, mobile display and external integrations. Create a recovery point before a significant change.
Hostingot currently offers WordPress hosting with backup and recovery. Integrated staging is a separate product concept. White-label sales, roles for client teams and bulk management are not offered as available features on this page.
Who is responsible for what?
| Stage | Agreement to record |
|---|---|
| Kick-off | Ownership of the domain, hosting account and paid licences. |
| Handover | Access, documentation, acceptance and responsibility for support. |
| Maintenance | The update process, recovery decisions and scope of your maintenance agreement. |
A handover that works
- Record accounts and owners without copying passwords into project documents.
- Document the theme, plugins, licences and integrations.
- Test the main customer action after each relevant change.
- Agree who can start a recovery and who informs the client.
Questions about client projects
Is this a reseller programme?
No. This is an approach to client projects on our available WordPress hosting. This page does not offer a reseller contract or white-label package.
Can I use staging?
Integrated WordPress staging is still a concept. The staging page describes the intended workflow and lets you share your requirements.
Who handles maintenance after handover?
Agree that explicitly with your client. A hosting subscription does not automatically define your responsibility for plugins, content or custom code.
Discuss how you work
Describe the type of client website, who will own it and how you organise maintenance. This keeps the hosting conversation specific.