01 Hosted applications
Websites & documentation
Marketing sites, documentation portals and handbooks built as static HTML. They are fast and cheap to host, and the usual attacks on a web server have nothing to target.
- Available as
- SaaS or Custom
- Hosting
- EU / EEA only
- Licence
- Open source throughout
- Handover
- Your repository
A Jekyll site is a folder of HTML. That accounts for its security model, how it scales and most of the maintenance plan.
We use it where uptime matters more than novelty: product and marketing sites, documentation portals, public-sector handbooks, conference sites and statutory disclosure pages. These sites have to cope with a front-page traffic spike on a Tuesday and with nobody looking after them in August.
What you get
Content lives in Markdown in your Git repository and is reviewed in pull requests like everything else. Editors who do not use Git get a web interface that commits on their behalf. The build runs in your CI and produces a directory, which nginx or a CDN serves from Stockholm or Falkenstein.
There is no database to back up, no runtime to patch on a Sunday, no plugin marketplace to audit and no admin login to brute-force. When we hand it over, any developer who knows HTML can follow the whole system.
Where it is the wrong tool
If you need per-user state, a checkout flow, or content that changes minute by minute, we will recommend Rails instead and quote you for that. Static generation has clear limits, and stretching it past them would cost you more than it costs us.
The long-form case
Why we reach for these in particular: the comparison tables, the numbers, and the situations where we would tell you to pick something else.