Static files and structured content in one system. Every update versioned. Preview before going live. Promote when ready. Self-hosted or cloud.
# Deploy your site in one command wren deploy ./dist --tree mysite --public Found 47 files in ./dist Creating binary collection: mysite-assets Uploaded 47 files... Created public read permission for tree:mysite Deployed to tree "mysite": 47 uploaded, 0 unchanged, 47 new paths Preview: https://wren.example.com/orgs/acme/tree/mysite/index.html
Why WREN
No CI/CD pipeline. No separate CMS. No build step. Just upload and serve.
wren deploy ./dist --tree mysite uploads your files, creates the tree, and gives you a URL. Done.
Every upload creates a new version. Diff any two, roll back to any point. Full history for HTML, CSS, images — everything.
Deploy with --label preview. Test at ?label=preview. Promote to published when ready. One label controls what’s live.
Your static files and your JSON data live in the same system. One tree, one permission model, one label makes everything live atomically.
Collections are queryable, filterable, faceted. Your site’s data is also a REST API. Schemas, labels, natural keys — built in.
One Docker image. Bring your own Postgres. No vendor lock-in. Your data, your servers, your rules.
How it works
Three steps from local build to live site. No CI pipeline, no build service, no waiting.
Point wren deploy at your dist/ folder. It scans every file, uploads only what changed (size-based diffing), assigns each to a tree path, and prints your live URL. First deploy auto-creates the binary collection and public permission.
Deploy with --label preview. New versions are created but the public site is unchanged — visitors still see the published label. Add ?label=preview to any URL to see the new version yourself.
One command moves the published label to every document’s current version. Static files and JSON data go live atomically. No race condition between “the site deployed but the data hasn’t synced.”
Compare
WREN replaces both the hosting layer and the content backend.
Pricing
Every plan includes deploy, versioning, labels, trees, and the full REST API.
For personal projects and experiments.
For side projects and small teams.
For production workloads and compliance.