Hosting
Hosting, monitoring, backups, updates and the steady stream of small changes a live property needs. Billed to your account, not resold through ours.
What you get
Why this way
The most common failure on a live site is not an outage. It is something that returns a perfectly healthy response code while being completely broken: a stylesheet that stopped loading, a form that submits into nothing, a page that renders but no longer contains the thing it is supposed to sell.
Every one of those returns 200. Uptime monitoring reports all clear. The business finds out when someone mentions it in passing weeks later.
So checks here look at the body of the response, not the status code. Does the form actually deliver. Did the CSS actually load. Is the page still the page. That is a more annoying way to monitor a site and it is the only kind that catches the failures that cost money.
Practice
This site is deployed with the full response verified after every release, not just the status code. The deployment process, including a mistake that shipped inert security headers and how it was caught, is documented in the repository rather than quietly fixed.
Questions
No. Hosting is billed directly to your account by the provider. For a static site that is often free or close to it. You pay us for work, not for reselling infrastructure.
Nothing switches off. The hosting account is yours, the domain is yours, the code is yours. You remove our access and the site keeps serving.
Small changes are usually same or next day. Larger work is scheduled. What we will not do is let a broken thing sit because it was not on the plan.
The other departments
Taking new work
Send what you have and what is not working. You will get a straight answer about whether this house is the right fit, including when it is not.