Managed hosting and domains, run by the people who build the software
We operate the infrastructure our applications run on. It means that, when something breaks outside office hours, the person looking at it already knows what the application does.
What managed means here.
Hosting is sold as a commodity and then delivered as a support queue. This is what we mean by the word.
Infrastructure we operate
Servers we operate ourselves, configured for the applications running on them rather than for some notional average workload. That includes PHP versions per site, resource limits that match real load and the ability to change something today because we control the machine.
Backups that are actually restored
Daily backups with defined retention, kept off the machine they came from. More importantly, restores are tested — an untested backup is a belief, not a policy. The only way to know a site can be restored to yesterday afternoon is to have done it.
Domains and DNS
Registration, renewals, DNS records, mail routing and TLS certificates that renew themselves. Domains are registered with your company as the registrant wherever the registry allows it — a domain that expires because the renewal invoice went to a former employee is a preventable outage.
Boring infrastructure is the goal.
Good hosting is uneventful. The measure is not a feature list; it is how many times a year you have to think about it at all. We run infrastructure where sites stay up, stay patched and renew their certificates without anyone having to think about it.
What is included
- TLS certificates issued and renewed automatically — an expired certificate is one of the most common and most avoidable causes of outage
- Security updates applied to the operating system and runtimes, verified before anything touches a production site
- Uptime and resource monitoring with alerts to us, not just a dashboard you are expected to watch
- Daily off-machine backups with tested restores and defined retention
- Mail configuration — SPF, DKIM and DMARC — so your messages actually reach inboxes
Migrating in
Hosting clients usually arrive from somewhere else, and usually annoyed with the provider they are leaving. We migrate sites, databases, mailboxes and DNS with the old environment still running, cut over out of hours, and keep the previous setup available until everyone is satisfied. Downtime on a planned migration should be minutes, and it should be scheduled.
Who this is not for
If you need the cheapest possible shared hosting, a large provider will beat us on price and we will say so. What we sell is a named engineer who knows your stack and answers when it matters — that is worth paying for when the site is part of how the business earns, and it is not worth paying for when it is not.
Things clients ask before moving.
Do you only host what you build?
What happens if there is an outage?
Can we keep our domains registered elsewhere?
Is there a long contract?
Often bought alongside.
Tell us what needs to stay up.
Describe what you are running and where it lives now. We will tell you what moving would involve and what it would cost.