The fast site you paid for, kept fast.
A site is only as quick as the machine serving it. We host what we build, on infrastructure picked for that build, and the load budget it launched with is the one it keeps.
“What am I actually paying for?”
Managed hosting, itemised before you agree to it
Most hosting invoices are a single line with no way to tell what sits behind it. Ours arrives with the list.
The server, sized for your build rather than sold by the tier. Nightly backups, kept for thirty days, with a restore we rehearse monthly. Certificates renewed before they lapse. Security patches applied by us, on our time. Uptime monitoring that alerts us rather than you. That is the plan, and there is nothing underneath it waiting to be billed separately.
It is one monthly figure, quoted against your site rather than a pricing table, because a brochure site and a store taking a thousand orders a week do not cost the same to run and should not pretend to.
Get the monthly figure for your site →“Will it stay up, and will it stay quick?”
99.9% uptime, checked every minute
Every site we host is polled from four locations, once a minute. When a check fails, the alert comes to us.
That order matters more than the number. Plenty of hosts will quote you an uptime figure; far fewer will tell you who finds out first when it slips. You should read about an outage in our note explaining what happened and what we changed, not in an email from a customer who could not check out.
Speed gets held the same way. We keep headroom on the server rather than running it at the edge of its capacity, so a good week of traffic is a good week rather than an incident. First byte lands in around two tenths of a second on the builds we host, and if a page starts drifting off its budget we see it in the monitoring before your visitors feel it.
“Does this tie me to you forever?”
Hosting you can leave, which is why people stay
You own the code. You own the domain. Nothing in the site is proprietary to us and nothing in it only runs on our infrastructure.
Notice is one month, and if you go we run the migration out ourselves and help your next host stand it up. That is not generosity, it is the only arrangement worth offering: hosting that holds a client through difficulty rather than through quality is a slow way to lose them anyway.
What most clients actually want is one team answerable for the whole thing. When the people who wrote the site are the people running the server, there is nobody to pass a problem to and nobody to blame. Read how the build works on our web development page.
Assess
We look at what the site needs to serve and how hard, then size the server to it. You get the monthly figure in writing, with the list of what it covers.
Move
We stand the site up on the new infrastructure and test it before anything switches. DNS moves last, once you have clicked through it yourself.
Watch
Monitoring goes on from day one, backups run nightly, and patches land on our schedule rather than waiting for something to break.
Report
You get a note when anything happened and a note when nothing did. No dashboard to log into, no metrics you have to interpret yourself.
“Why not just pay a fiver a month?”
What managed hosting buys you is the bad day
On a good day, cheap shared hosting and managed hosting look identical. Nobody buys either one for the good days.
The difference shows the morning the database corrupts, or a plugin update takes the checkout down, or a bot finds a hole that was patched everywhere except your server. On the cheap plan that is your problem, at your speed, with a support queue between you and anyone who can help. On ours it is our problem, and we have already rehearsed it.
We run a full restore on a live site every month and time it. Worst case, from total loss to a working site with the forms and the checkout tested, is under four hours. We know that because we have done it, not because a feature list says so.
Ask us what your bad day looks like →Website hosting questions, answered
What does website hosting cost?
One monthly figure, quoted against your build rather than a pricing table. It covers the server, nightly backups, certificate renewals, security patches, and uptime monitoring. Stores and sites with heavy traffic cost more to run, and you see that in the quote before you commit to it.
Do I have to host with you?
No. You own the code and the domain on every build we ship, and it runs anywhere. Most clients host with us because the site was written for the stack we put it on, and because one team answering for both means nobody gets to blame the other. If you would rather host elsewhere, we hand it over and help you set it up.
What uptime do you hold?
99.9% across the sites we host, checked every minute from four locations. The monitoring alerts us, not you, so the first you hear of a problem is our note saying what happened and what we did about it.
How often do you back the site up, and have you tested a restore?
Nightly, kept for 30 days, and yes. We rehearse a full restore every month on a real site, because a backup nobody has restored from is a guess rather than a safety net. Worst case from a total loss to a working site is under four hours.
Can you host a site another agency built?
Usually. We audit it first and tell you what we find, including anything we would not be willing to take responsibility for while it stays as it is. If the site needs work before it can be hosted safely, you get that in writing with the cost, and you decide.
What happens if I want to leave?
One month's notice, and we run the migration out ourselves. Nothing in your site is proprietary to us and nothing only runs on our infrastructure. A client who stays because leaving is difficult is not a client worth keeping.
Tell us what the site has to serve.
One monthly figure, the list of what it covers, and one month's notice if it stops suiting you.
And if the site has not returned what it cost inside its first year, the re-design and the rebuild are free.