Alpha Release

Static-First, File-Native
Content Management

Publish durable HTML artifacts, not runtime APIs. Built for developers who value performance, reliability, and long-term maintainability.

Get Started View on GitHub

Publishes as files

Zero runtime dependency

Deterministic output

Key Characteristics

Designed for longevity, debuggability, and operational clarity.

Static-First Publishing

User-facing pages are generated as final HTML at publish time. No runtime rendering, no request-time content APIs.

File-Native Architecture

Published content lives as files in object storage. HTML, metadata, and sitemap are first-class artifacts.

Deterministic Output

Published pages are deterministic results of content + templates + build logic. The same input always produces the same output.

Zero Runtime Dependency

User-facing delivery requires no backend application, no rendering engine, and no runtime content APIs.

Clear System Separation

Admin is an application. User pages are documents. Clean boundaries, minimal attack surface.

Edge-Native Deployment

Pages for delivery, R2 for content storage, Workers for interaction. Designed for edge infrastructure.

Architecture Overview

A clear separation between the admin application, published artifacts, and the delivery layer.

Application

Admin Dashboard

Content editing, publishing, operational workflows

publish

Publish Targets

Static Artifacts

R2, GitHub, S3

Delivery Layer

Connected Delivery

Cloudflare Workers, GitHub Pages, Cloudflare Pages, CloudFront

✓ JavaScript is for progressive enhancement, not core rendering

✓ Published artifacts can be served independently from the admin backend

✓ Connects to R2, GitHub, S3, and multiple delivery layers

Why ZeroPress?

An alternative to WordPress and API-centric Headless CMSs.

vs WordPress

Content storage

Database

Files (HTML + JSON)

Rendering

Request-time PHP

Publish-time static HTML

Failure mode

White screen / DB errors

HTML still available

Plugins

Required for basics

Architecture-level features

Security

Continuous patching

Minimal attack surface

SEO

Runtime dependent

Deterministic

Mental model

Application

Documents

vs Headless CMS

Content delivery

JSON API

Static HTML files

Frontend

Required

Not required

SEO

SSR/SSG dependent

Native

Runtime dependency

High

None

Content survivability

Tied to API

File-based

What ZeroPress Is Not

Headless CMS

SPA-based

Request-time SSR

Framework-coupled

ZeroPress does not render pages via APIs.
ZeroPress publishes pages as files .

Vision

"Published content should outlive frameworks, APIs, and runtimes."

Instead of optimizing for developer convenience alone, ZeroPress optimizes for longevity, debuggability, operational clarity, and content survivability.

Longevity

Debuggability

Clarity

Survivability

Recoverable by Design

If you can rebuild it, you don't need to restore it.

Single Source of Truth

D1 stores canonical content and publishing intent. Everything else is derived.

Deterministic Publishing

Published pages are deterministic outputs of content + templates + build logic.

Failure Model

Critical

Restore from backup

Templates

Critical

Restore from Git

Non-critical

Re-publish (rebuild)

Infrastructure failures degrade into rebuild operations , not outages.

Currently in Alpha

Ready to publish durable content ?

Join early contributors who value clear architecture, explicit decisions, and minimal magic.

Read the Docs Contribute

Static-First, File-Native Content Management