📰
Publish often, read often.
Content site hosting
Editors publish, visitors read. One application does both.
Built with
Built by
Features
Benefits
Solutions
A CMS that renders its own pages: editors publish, visitors read, and the HTML arrives finished. It's the most common thing on the web, and it's the workload PHP was built for — a database, or in Kirby's case a folder of text files, on one side, templates on the other, a request in between.
Reads and writes pull in opposite directions
A handful of editors write; everybody else reads. With a page cache doing its job, most requests are cache hits rather than full renders, so the PHP component is sized for the editors and the cache misses, not for the traffic graph. In practice the XS and S plans cover most normal websites, with 256 MB PHP memory as a workable starting point for WordPress and Kirby.
Uploads outgrow everything else
Text stays small for years; images and PDFs don't. Uploads live on the storage component, a persistent file system that survives deploys — each release replaces the code directory while runtime data stays in place. Storage is one of the autoscaling components: plans grow and shrink with measured usage, aggregated daily for billing.
Components are booked individually and billed pro-rated, post-paid, by the day, so a site that grows for a season and settles again isn't stuck with the plan it needed in October. The backup component snapshots the whole environment state, uploads and database included.
Trust
An honest account.
