📰
Publish often, read often.
CMS 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 — content on one side, templates on the other, a request in between.
Flatfile or database-driven
Where the content lives splits the field in two. Flatfile CMSes like Kirby and Statamic keep entries as text files in folders; database-driven ones like WordPress, Craft CMS and TYPO3 keep them in MySQL. Both are ordinary PHP applications here — the difference is which components an environment books.
A flatfile site runs on the PHP and storage components alone. The content folder is runtime data: editors change it on the server, so it belongs in persistent storage rather than the deploy package — the deploy sync only replaces what the package contains and leaves everything else in place. Teams that version content in git instead route edits through deploys; both setups work, but mixing them silently overwrites one side.
A database-driven site adds the MySQL component for entries and settings, while uploads still land in storage. The backup component snapshots both together, so a restore point always holds a matching database and media library.
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.
Trust
An honest account.
