A static site is HTML, CSS, images and nothing else. No database, no plugins, no admin login. It is the least fragile thing you can put on the internet, and most of the sites we are asked to rescue would have been fine as one.
On this page
The best part is what is missing
Every other page on this site describes keeping software current, because software is where sites break and where they get taken. A static site has none of it:
| No database | Nothing to inject, nothing to dump, nothing to corrupt. |
|---|---|
| No CMS | No core, plugin or extension updates. No version to fall behind. |
| No admin login | Nothing to brute force. The thousands of daily attempts against login pages across our platform simply have no target here. |
| No server side code | A request for a configuration file or a shell finds files that cannot execute. |
This is not an argument against a CMS. If people who are not developers need to publish without asking anyone, you want a CMS and we will host it. But if the site changes a few times a year and a person edits the files, static is faster, cheaper and quieter.
What you still get
Static does not mean unmanaged. The platform work is the same:
- Certificates issued and renewed automatically.
- Served from cache, so pages come back without touching the origin.
- Edge filtering, so the sweeps for configuration files and source control directories are refused before they reach your files.
- Offsite backups, nightly, to storage separate from the server. Yes, even for files you also have locally. The copy you have locally is the one that gets overwritten.
- Monitoring, checking that the site actually answered rather than that a cached copy was returned.
- A preview address that search engines are told to ignore, so you can see the site before the domain points at us.
Generated sites
If your site is built by a generator, we host the output. Upload the built files over SFTP and that is the deploy. There is no runtime for us to match, no build step on our side to keep in step with yours, and nothing that stops working when a language version moves on.
Forms and the one thing static cannot do
A static site cannot process a form submission on its own, so a contact form needs somewhere to send it. We can put a small handler alongside the site, or point the form at a service you already use. Worth settling before launch rather than after someone notices nobody received the enquiries.
Most of the sites we migrate arrive as a CMS installation with one page of content, built that way because the person building it only knew one tool. Converting those to static makes them faster and removes the maintenance entirely. We will tell you when that is the better answer, including when it means a smaller invoice.
Where this is the wrong choice
Static is not for you if the site needs user accounts, a shop, search over a large catalogue, or non-technical editors publishing daily. Those want an application, and the other pages here cover that.
Ask about hosting your static site
Send us the files or the URL. Static sites are quick to quote, because there is very little to find out.
Request information