Managed hosting
Hosting setup and coordination, SSL, domain connection, deployments, uptime checks, and technical communication with the provider.
THE PRACTICAL SIDE OF THE PICTURE
Choose the responsibilities your website needs. Agree what gets checked, who owns the work, and what happens next.
Every connected part deserves a clear owner.
01 / WHAT ONGOING CARE CAN COVER
Hosting setup and coordination, SSL, domain connection, deployments, uptime checks, and technical communication with the provider.
Software and dependency updates, compatibility review, broken-link checks, form testing, and small technical fixes.
Plan-defined backup frequency, retention, restore procedures, and clear responsibilities when recovery is needed.
Periodic tests of forms, booking links, notifications, spam controls, and the agreed integrations behind an inquiry.
Documented DNS help that protects MX, SPF, DKIM, DMARC, and verification records while web changes are made.
Practical monitoring, recommendations, update hygiene, login protection, and incident coordination—with honest limits.
02 / CHOOSE THE LEVEL OF RESPONSIBILITY
Compare the kinds of responsibility your website needs. We agree the work, frequency, response arrangements, and price in a written scope.
EXAMPLE SCOPES · Final allowances and response arrangements are agreed for your website. Hosting, AI usage, paid services, emergency work, and migrations may be separate.
03 / RESPONSIBILITY, DEFINED
A dependable care plan says what will be checked, how often, who owns each account, how support is requested, and what happens when a problem falls outside the agreement.
Read the practical details ↓Domains and core business accounts should remain under the client’s control whenever practical. Access is documented and limited to the work being performed.
Monitoring, updates, backups, and good configuration reduce risk. They do not guarantee that a website can never be compromised or interrupted.
A response target means acknowledging and beginning review. Resolution can depend on the cause, provider, access, and availability of a safe fix.
Each plan defines included edit time and whether unused time carries forward. New features and redesign work receive a separate scope.
THE PRACTICAL DETAILS
No. Managed care can be discussed for an appropriate external setup. Hosting, ownership, access, responsibilities, and provider costs are agreed before work begins.
No. Each plan defines an included allowance. Larger additions, redesigns, new integrations, and unused-time rules are addressed in the service agreement.
No backup system removes every risk. The plan should define frequency, retention, included data, storage, restore testing, and the process and cost of recovery work.
No. Availability depends on providers, software, networks, integrations, and events outside one party’s control. Care plans define monitoring, escalation, and response—not impossible guarantees.
No. TheWebPage.ai scopes and implements automation. Connected Care covers only the monitoring and maintenance responsibilities specifically listed in the care agreement.