Hosting & Maintenance
Someone to call
after launch.
Managed infrastructure and ongoing care for the products we build, so performance and security do not quietly degrade over time.
Why it matters
Software decays
when nobody owns it
Nothing stays working on its own. Dependencies get security patches, third-party APIs change, certificates expire, and disk fills up — usually on the day it is least convenient.
Security is not one-time
Vulnerabilities are found in things that were fine last month. Patching is a routine, not a project.
Integrations move
Payment providers, shipping APIs, and platforms change without asking. Something has to notice before a customer does.
Performance drifts
More data, more content, more traffic. A site that was fast at launch is not automatically fast a year later.
Backups are only real if tested
An untested backup is a belief, not a recovery plan. Restores need to be practised.
How we work
Boring infrastructure, on purpose
Infrastructure you own
Deployed to accounts in your name. If you leave, you keep the servers, the domains, and the data.
Monitored, not watched
Uptime, errors, and certificates alert us automatically. Nobody should learn about downtime from a customer.
Backups with restores tested
Automated, off-site, and periodically restored to confirm they actually work.
Updates on a schedule
Security patches applied routinely and staged before production, so upgrades stay small and boring.
Reproducible deployments
Containerised and scripted, so recovering an environment is a known procedure rather than an archaeology exercise.
A person, not a ticket queue
You talk to someone who knows your system, because we probably built it.
Honest fit
You may not
need us for this
Managed hosting is worth paying for when the system matters commercially and nobody internally can own it. If you have a capable technical team, they should probably run it themselves.
Managed hosting makes sense when
- The product is commercially important and downtime costs you
- There is no in-house team to own servers and updates
- The stack is self-hosted rather than fully managed by a platform
- You need someone accountable when something breaks
- The system will keep changing and needs ongoing work
You can probably skip it when
- You have a technical team already running infrastructure
- The site is fully managed by a platform like Shopify
- It is a static site with no backend to maintain
- The project is short-lived or a one-off campaign
- You would rather own the risk to keep the cost down
Infrastructure
What we actually
run and watch
A typical setup. The specifics depend on the product, but the separation between the runtime, the data, and the things watching both stays the same.
What is included
The work that
keeps it running
FAQ
Questions
we get asked
Do you only host what you built?
Mostly. Taking over someone else's system means taking on its history, so we audit it first and are honest about what we found — including when the sensible answer is that it needs work before anyone can support it properly.
What are the response times?
That depends on the arrangement, and we would rather agree it in writing with you than publish a number here that may not apply to your project.
Where is it hosted?
On infrastructure in your name, in a region that suits your customers and your obligations. You keep the accounts and the data whatever happens between us.
What if we want to move away?
You take it with you. Deployments are containerised and documented, and the accounts are already yours — we hand over rather than hold anything hostage.
Does this include new features?
Maintenance covers keeping the system healthy — updates, monitoring, fixes, and performance. New work is scoped separately so you are not paying an open-ended retainer for something undefined.
Related
What we usually maintain
Work with us
Have something
you want built?
Small enough to care about the details. Experienced enough to build the difficult parts. Tell us about the problem and we'll come back with a technical direction, scope, and timeline.
You work directly with the people building your product.