What managed hosting means here
Your website runs on enterprise Drupal infrastructure that we operate for you. Monitoring, backups, SSL, DDoS protection, security patching and support are part of the plan, handled by the same engineers who know your codebase.
That last part is the whole point. When a page slows down, the question "is it the code or the infrastructure?" is answered by one team looking at both, rather than becoming a conversation between 2 suppliers.
What is included
2 tiers. The allowances and the operations are identical on both; the uptime commitment is what differs.
| Per site | Basic | Pro |
|---|---|---|
| Uptime commitment, per month | 99.9% | 99.95% |
| Planned maintenance | May fall outside the commitment | Counted against the commitment |
| Production environment, live around the clock | Yes | Yes |
| Non-production environments for build, test and review | 2 | 2 |
| Storage across all of the site's environments | 20 GB | 20 GB |
| Production hits per month | 200,000 | 200,000 |
| Monitoring, backups, SSL, DDoS protection, security patching, support | Yes | Yes |
| Preview environments, deploy on push, nightly backups | Yes | Yes |
| Additional storage, traffic or environments | Published rate | Published rate |
The allowance is generous on purpose. Most sites sit inside it and pay the flat fee, month after month, with nothing to reconcile.
The platform underneath
We run your site on Lagoon(Opens in a new tab/window), the open-source application delivery platform for Kubernetes, hosted on amazee.io Cloud. It is the same platform we use for our own work, and it is what turns hosting from somewhere your site sits into part of how your team ships.
Preview environments for every change
Open a pull request and Lagoon builds it a working environment of its own. It merges your branch on top of the target branch first, so what you review is the merged result, including everything that landed in the target since you branched. If the merge conflicts, the build stops and tells you, before anyone has spent time reviewing the wrong thing.
That changes the review conversation. A stakeholder gets a URL and clicks through the actual change on real content, instead of reading a description of it or waiting for a staging slot to free up.
Branch-based environments work the same way, if your team prefers those to pull requests. Lagoon does not impose a workflow; you tell it which branches and pull requests deserve an environment.
The same thing everywhere
Local, test and production run the same Docker images, the same service configuration and the same code. When something behaves differently in production, that difference is a real bug worth chasing, because the environments themselves are not the variable.
Deployment and recovery
- Push to a configured branch and the deployment runs itself: build, deploy, and a notification to Slack or email when it lands.
- Backups run nightly on every database and every persistent volume. Daily backups are kept for a week and weekly backups for 6 weeks, and any of them can be retrieved on request.
- Services your Drupal site actually uses are first-class on the platform: MariaDB, Redis, Solr, Varnish and OpenSearch among them.
One thing to plan for: each live environment consumes one of the non-production environments in your allowance. Teams running many preview environments at once either prune them as pull requests close, or add environments to the plan. We will tell you which pattern fits your team before you are surprised by it.
Choosing a tier
Basic suits sites where a short outage is an inconvenience. Pro suits sites where it is a business event: transacting sites, campaign landing pages, anything with a support cost attached to being unreachable.
Pro buys back roughly half the allowed downtime and brings planned maintenance inside the commitment, so scheduled work counts against the same number you are measuring us on.
Storage and extra environments cost the same on either tier, so a site with heavy content but ordinary traffic gains nothing by moving up. Pick the tier for the uptime you need, and stay where you are otherwise.
How the billing works
A flat base fee per site per month while the site sits inside its allowance. If a site goes over on one axis - storage, traffic, or an extra environment - you pay for the excess on that axis alone, at a published rate. Everything else stays flat.
A site stays on one tier for a whole billing month, and a change takes effect from the start of the next one. Invoices are itemised per site, so a portfolio of sites reads as a list you can check line by line.
Moving a site in
Migrating an existing site onto managed hosting is quoted once, up front, as a one-off alongside the recurring plan. It is never folded into the monthly fee, so the ongoing cost stays the ongoing cost.
The cutover is staged behind a rollback plan. The new environment goes live and is verified before DNS moves, which is what lets us move a site without downtime.
It starts with a technical assessment of what you are running now, at no cost, so you can see the shape of the move before committing to it.
Who this is for
- Teams who would rather hold one supplier accountable for the website and the infrastructure together.
- Organisations coming off a hosting arrangement where nobody quite owns the platform layer.
- Anyone already working with us on delivery or support who wants the hosting to sit in the same place.
Where the line sits
We host the websites we build and support. That is what makes the accountability real: the team operating the infrastructure is the team that knows what runs on it.
Hosting for a site we have never worked on starts the same way any engagement does, with a look at what is there. Sometimes the answer is that your current arrangement is fine and you should keep it.
Talk to us about your platform
Managed hosting usually sits alongside ongoing support, and it is where sites land after a migration or an upgrade.
If your site is on hosting nobody wants to touch, or your renewal is coming up and you want to know what the alternative looks like, tell us what you are running and we will assess it.