Separate the platform from the care around it.
A hosting provider supplies the environment that stores and serves the website. A maintenance plan covers work such as dependency updates, compatibility checks, monitoring, backups, recovery, small fixes and the process for handling incidents or requested changes.
Managed hosting can combine parts of both. The word managed is not a standard scope, so the proposal must still name the tasks, response routes and exclusions. Without that detail, two similarly priced plans may leave very different responsibilities with the client.
Do I need website maintenance if I already pay for hosting?
Usually, yes. Hosting may keep the server or platform running without checking whether your forms, integrations, dependencies and content workflows still work as intended. Some managed plans include maintenance tasks, but you should confirm the exact coverage. The important distinction is who notices, investigates and resolves a problem in the website rather than only the infrastructure beneath it.
Know what hosting is responsible for.
Hosting quality affects availability, speed and recoverability, but a hosting account does not automatically create an operating process for the whole website.
Infrastructure and delivery
The service stores site files and data, processes requests and delivers responses to visitors. Confirm the platform, region where relevant, resource limits and how capacity changes if the site grows or receives a traffic spike.
Domain and DNS boundaries
The domain registrar, DNS provider and host may be separate. Record who controls each account, where access is stored and who is authorised to make changes so a routine update does not become an ownership problem.
Backups and restoration
A backup only becomes useful when its coverage, frequency, retention and restoration process are understood. Ask whether files, databases and configuration are included and how a restore is requested and tested.
Platform-level monitoring
A provider may monitor server availability or platform health without knowing whether an important customer journey is broken. Understand which signals are watched and where the hand-off to website support begins.
Define the maintenance work around the website.
Maintenance turns a deployed site into an owned service. It needs priorities, checks and a person responsible for acting on what those checks reveal.
Software and dependency updates
Content systems, frameworks, plugins and packages change. The plan should explain how updates are reviewed, tested and released, and what happens when an update conflicts with custom functionality.
Journey and integration checks
Forms, payments, email delivery, bookings and external APIs can fail even when the homepage loads. Identify the journeys that matter commercially and how problems will be detected rather than waiting for a customer report.
Security response
State who reviews relevant alerts, applies urgent updates, investigates suspicious behaviour and communicates an incident. Avoid broad promises that do not name a response process or service window.
Content and improvement requests
Routine maintenance is different from adding pages, redesigning a section or building a feature. A good plan explains which small changes are included and how larger requests are estimated and scheduled.
Compare plans through scenarios, not feature labels.
Ask what happens when something goes wrong, when someone needs a change and when the current setup no longer fits. The answers reveal the operating model.
A contact form stops sending
Will monitoring detect it, who investigates the website and email provider, what response time applies and is the fix included? This scenario crosses hosting, application and third-party boundaries.
An urgent security update appears
Ask who judges relevance, how quickly critical work is handled, where it is tested and how you are told about risk or disruption. An update feed alone is not a response service.
A campaign needs a new landing page
Confirm whether content entry, design adaptation, development, analytics and quality assurance are included. Maintenance retainers and improvement budgets solve different kinds of work.
You decide to change provider
The domain, code, database, content and relevant accounts should have an understood handover route. Ask about notice, exports, credentials and migration help before that information is needed under pressure.
Hosting, maintenance and improvement at a glance.
Providers package these responsibilities differently. Use the categories to expose overlap and gaps in the actual proposal.
Hosting
Infrastructure, storage, traffic delivery, platform availability and resource limits.
Managed hosting
Hosting plus a defined layer of monitoring, backups, configuration or support. Exact coverage varies.
Maintenance
Routine technical care, updates, compatibility checks, recovery readiness and agreed journey checks.
Incident support
A route for reporting, triaging, communicating and resolving an unexpected problem.
Content support
Help changing existing words, images, entries or pages within the current system.
Continuous improvement
Planned design, content, performance or feature work based on business priorities and evidence.
Give every live responsibility an owner.
Subtle Standard provides managed hosting and ongoing support with the boundaries discussed around the website, its integrations and the changes your team expects to make.
Hosting and support questions.
What is managed website hosting?
Managed website hosting combines infrastructure with a defined level of operational care. That may include deployment, monitoring, backups, configuration, updates or support, but the term has no single universal scope. Ask the provider to list the exact systems they manage, the checks they perform, their response route and which website problems remain outside the plan.
Is website maintenance the same as making content changes?
Not necessarily. Maintenance often covers technical health, updates, monitoring and fixes, while content support covers edits to pages, images or structured entries. Some plans include an allowance for both. Confirm whether unused time carries over, what counts as a small request and when a change becomes a separate design or development project.
What should a website maintenance agreement include?
It should name the covered website and services, routine tasks, monitoring, backups, update process, support hours, priority levels, response expectations, exclusions, client responsibilities, access arrangements, third-party costs and exit process. It should also distinguish incident work from requested improvements so neither side has to interpret the agreement during an urgent problem.
Can I host a website with one company and maintain it with another?
Yes, provided the boundaries and access are clear. The maintenance provider needs suitable control of deployments, logs, backups and configuration, while the host must expose enough information to investigate platform issues. Record who opens support tickets, who approves changes and how the two providers coordinate when the source of a fault is uncertain.