Where it runs
Cloud hosting and deployment
Hosting should be boring. Certificates renew themselves, deployments roll back cleanly, and backups exist before you need them.
We have offered domains and hosting since the early years of the studio. What changed is the shape of it. A modern site sits behind a CDN with content cached close to the visitor, and the server only does the work that genuinely has to be dynamic.
We set this up in your own account wherever possible. Your domain, your hosting bill, your access. Agencies that hold the keys create a hostage situation nobody planned for, and it always surfaces at the worst moment.
One detail worth stating plainly: an expired SSL certificate takes a site offline for most visitors, and browsers show a full page warning rather than a small notice. Automatic renewal is not optional.
What the work covers
Included in every hosting & devops project.
Domain and DNS
Registration or transfer, records configured, and email routing kept working through the move. DNS mistakes cause more launch day outages than code does.
SSL that renews itself
Automatic certificates with monitoring, so nobody has to remember a date twelve months from now.
CDN and caching
Static files served from an edge close to the visitor, with cache rules set per file type rather than one blanket setting.
Preview deployments
Every change gets its own URL to review before it reaches the live site. Approving a link is easier than approving a description of a change.
Backups and rollback
Database backups on a schedule, tested by actually restoring one, and a one click return to the previous deployment.
Uptime and error monitoring
An alert when the site goes down or starts throwing errors, sent to a person rather than to a dashboard nobody opens.
No themes, no page builders, no plugin stacks
Every site written from scratch, starting from almost nothing and adding only what the pages need. The whole speed recipe is published, not kept secret.
Read the recipe →AI, used properlyWe use AI to go faster, not to decide
It writes the mechanical parts. It never chooses the architecture, the performance budget, or a single fact about your business. Everything is reviewed by the person who will maintain it.
Where we draw the line →Questions
Asked often enough to answer here.
If yours is not here, the general questions page covers how we work, or you can just ask.
Can you host it for us instead?
Yes, if you would rather not deal with it. We bill it through transparently and you keep the right to move at any time. Our preference is your own account, because that is the arrangement that protects you.
What happens if the site goes down at midnight?
Monitoring alerts us. If you are on a care plan we respond within the agreed window. If you are not, we still answer where we can, but we will not promise a time we have not committed to.
Will moving hosts affect my email?
It can, and this is the most common way a migration goes wrong. Email records are separate from website records. We note the existing mail configuration before touching anything and confirm mail still flows after the switch.
Related work we do
All 16 servicesCustom web development
Websites written from scratch for one business, rather than a theme bent into shape until it almost fits.
Next.js development
The framework we reach for first, and the one we know well enough to know when it is the wrong answer.
Bun and Node.js backends
The part nobody sees, which is exactly why it has to be right.
Want this for your business?
Tell us what you have now and what is not working. We will tell you what we would do and what it would cost.