Hardened Linux servers at DigitalOcean, Frankfurt
The same infrastructure every system we operate runs on, not a shared budget host chosen to hit a price point.
MANAGED HOSTING
The infrastructure behind everything we build
A fast build sitting on slow, unmanaged hosting is a fast build that does not perform like one. Managed hosting is the same infrastructure every system we operate runs on, not a shared budget host chosen to hit a price point.
WHAT'S INCLUDED
Four things, held in production, not just promised at launch
Each one is how we run our own systems, extended to what we host for clients.
Atomic releases, one-command rollback
A deploy completes fully or not at all. A broken one reverts in one command, not a manual cleanup.
Backups tested by restoring them
An untested backup is a hope, not a control. Restores are rehearsed on a schedule, not assumed to work.
Caching set correctly, not left at defaults
Static assets cached for a year, HTML revalidated on every request, HTTP/3 enabled. The speed the build was designed for, held in production.
HOW IT'S PRICED
Part of care, not a separate line item
Included in a standard website's quarterly figure, or scoped with the wider care agreement for a platform.
Managed hosting is included in what a standard care plan covers, billed as part of the same quarterly amount. Platforms and marketplaces are priced by agreement, the same way the rest of care is.
What a care plan costs
Around
STRAIGHT ANSWERS
Questions about managed hosting
The ones that come up once a project is close to launch.
The same four measures behind every system we build: security headers configured correctly, encryption in transit and at rest, no third-party script on the render path, and every dependency justified and audited monthly. Hosting is not a separate security posture from the build, it is the same one extended to the infrastructure.
Releases are atomic, so a deploy either completes fully or does not apply at all, and a broken one rolls back with a single command rather than a manual scramble to undo half-applied changes. The site is never left in a state that is half the old version and half the new one.
We restore them. An untested backup is a hope, not a control, so restores are rehearsed on a schedule rather than assumed to work because a backup job reported success. The first time a restore is tested should never be during an actual incident.
It is included in what a standard care plan covers for a website, billed as part of the same quarterly figure. For a platform or marketplace, hosting is scoped as part of the wider care agreement rather than priced on its own.
Building something new? Hosting is included in the build.
Every project we build ships on this same infrastructure from day one. Care and managed hosting are scoped at handover, once you know what you actually built.
Managed hosting sits alongside care plans and monitoring as the three parts of what keeps a site running after launch.