Timberline
Active developmentA secure publishing platform that turns a private CMS into immutable public releases.
Timberline separates writing from serving. Editors work in a private CMS; the public site is built as an immutable release artifact and promoted by moving an atomic pointer, so serving never depends on the CMS, the database, or Git being online.
The problem
Most content platforms couple the public site to the editing system, so an admin outage or compromise becomes a public outage or defacement. Teams leaving WordPress need the editing comfort without carrying that coupling forward.
What it does
- Builds the public site as an immutable release tree; promotion and rollback move an atomic pointer to the same artifact without rebuilding.
- Keeps the public surface free of CMS credentials through a narrowly scoped public API sidecar.
- Imports WordPress content through SSRF-guarded migration tooling with staged review.
- Requires TOTP step-up for promote and rollback operations, and signs outbound webhooks.
Security notes
- Strict package boundaries keep admin, worker, and public surfaces separated.
- Preview links are authenticated, scoped, and marked noindex.
Honest limitations
- In active development with no public release or decided licence.
- WordPress import does not yet map every Gutenberg block type or SEO plugin field.
- Continuous integration currently runs manually rather than on every push.
Where to find it
Timberline is in development and not yet public. Private for now; licensing is not yet decided. The developer portal records its current state honestly.
Related work
- Fairview: A local-first control plane for AdGuard Home fleets.