Services / hosting and care
Hosting and care.
A website does not end on launch day. I maintain the sites I build and take over sites built by someone else: hosting, certificates, backups, updates, monitoring and small content changes — so you are not looking for someone from scratch when something breaks.
The website needs to work, but nobody owns its updates, incidents and access.
Describe what you needI have a site and need care
Start with a review and clear responsibilities.
02I need a handover or migration
First establish domain, email, data and recovery access.
How the work is handled
Inventory
What runs, where it is hosted and who has access. We identify missing pieces.
Review and plan
The condition of the site, backups, updates and changes needed. You receive a care scope.
Take over or put in order
Protect the data, test and perform an agreed switch if one is needed.
Continuing contact
Monitoring, updates and small changes within the agreed scope.
Praust Moto
Praust Moto shows a local-business website where a current offer and working contact matter. It illustrates the service context; care arrangements are agreed individually.
Who this is for
Companies without an IT department, where the website matters but is nobody's job. And those whose previous developer vanished, leaving nobody sure where the domain, hosting and panel access actually are.
What it covers
- Hosting suited to the site, with SSL and uptime monitoring.
- Regular backups with tested restores — a backup nobody has tested is not a backup.
- Security updates and technical reviews.
- Small content changes: offers, hours, pricing, news, photos.
- Response when things break, including dealing with the domain operator if the problem sits there.
- Periodic performance and visibility reviews, rather than waiting for traffic to drop.
Taking over a site from another developer
The usual scenario: the site works, but nobody has full access, the domain is registered to a personal email from years ago, and hosting is paid by someone who no longer works there. I start with an inventory: where the domain is, where hosting is, where the code is, who holds access and what needs recovering.
The result is one place where it is clear what the site consists of — even if you later choose to work with someone else.
Agree who is responsible for what
Care has a specific scope. We agree response arrangements and work frequency for the site rather than treating every website as identical.
| Area | Care covers | Agreed separately |
|---|---|---|
| Availability and backups | Monitoring, backups and checking that recovery is possible. | Required frequency, retention and response arrangements. |
| Updates | Review and updates of the components covered by care. | Major version changes requiring a rebuild or additional licences. |
| Content | Small offer, hours, image and contact-detail changes. | New pages, features, substantial copy and integrations. |
| Domain and email | Configuration checks and provider contact within scope. | Mailbox migrations, provider changes and additional services. |
Your accounts and access remain yours. Care scope and external-service costs are described before work starts.
What to prepare on your side
Establish the full picture before switching
A website address and description of the situation are enough to start. We then establish domain, hosting, code and email access. We do not switch providers until we know what runs on the existing account and how to verify it afterwards.
The steps before a handoverThe website and access remain yours
Domain and hosting in your name, full access and code you can move. Care after launch is a choice, with its scope agreed before work begins.
See how continuing care worksHosting mess / ZmieńWWW
Is the mess the hosting itself?
Site with one provider, email with another, the domain with a third and an expired certificate — that is a specific job, and I run a separate service for it. Describe what you have and you will get an answer on whether moving it is even worth doing.
Describe your case at ZmieńWWWZmieńWWW is my second project. No obligation.
Questions before we start
Will you look after a site you did not build?
Yes, after a review. I check what it is built on and what condition it is in, and say plainly whether maintaining or rebuilding makes more sense.
What happens when the site goes down?
Monitoring reports downtime, so I usually know before you call. Backups mean restoring to a working state rather than rebuilding.
Am I locked into a contract?
No. Domain and hosting access are yours to take. Care should hold up on quality, not on being hard to leave.
Read next
Hosting, domains and who owns them.
What hosting for a small site should cost, and how to check who really owns your domain.
Moving a site from a previous developer.
How to recover domain, hosting and code — and not lose your Google positions in the move.
You cannot change your own site.
A stale offer, calls about old prices, and a site you cannot change yourself.
Next step
Let's discuss care for your website
The conversation and quote are free. I usually reply within one business day.