Built into the binary
Every piece you would otherwise wire together.
Coming
Plugins, sandboxed or native.
Run untrusted plugins safe in a WASM sandbox. Compile trusted ones into the binary at native speed. Pick the tradeoff per plugin.
Coming
Branch your content. Merge with one click.
Edit on staging, review the diff, merge to production. Content finally gets the workflow code has had for fifteen years.
Coming
Static by default. Dynamic where it counts.
Pre-render the whole site. Drop in dynamic islands where you need them. .publr templates borrow Astro syntax, compiled by Zig — same template runs server-side and at build time.
Coming
Publish a field. Or a release. Or schedule it.
Field-level publishing, named releases, scheduled rollouts, approval flows — designed into the schema, not bolted on.
Shipped
One binary. Database inside.
Drop the file on a server and run it. SQLite embedded, static assets baked in, no runtime to install, no language required.
Shipped
Compiled native. Audit it in a day.
Pure Zig with a curated set of C dependencies, vendored by hand. No npm, no cargo, no transitive package graph to rot under you.
End to end
Publr is the content platform — framework, CMS, and build step combined.
Which is why Publr can do things other CMSes can only dream of.
Coming
Publish one page. Rebuild one page.
Publr tracks exactly which output depends on which content. Hit publish, and only the affected pages regenerate — in milliseconds. No framework can do this from outside the CMS.
Coming
Tailwind-style JIT, built in.
Publr ships its own JIT compiler that builds CSS from the content authored in the CMS. API-compatible with Tailwind v4 — no PostCSS, no node_modules, no external build step.
Coming
Knows what is above the fold.
Publr sees the whole render tree. It can split bundles, defer non-critical CSS, and prioritize above-the-fold delivery — automatically, without a config file.
Coming
Every page knows its schema.
Publr reads schema directly. Every page knows which fields it uses, every section knows what it renders. Content tooling, validation, and migrations all see the same truth.
Coming
Static export, no build chain.
Generate a CDN-ready static site straight from the binary. No npm install, no Node runtime, no separate build pipeline — just Publr and your data.
Get involved
Open source. Free forever.
Star the repo, file issues, follow the roadmap. No private backlog, no closed-source admin.