Self-Hosting

You can self-host Tovu today — this isn't only a roadmap page. It ships as one Docker container: content, uploads, and themes live in a single mounted volume, nothing else required.

Run it yourself

Set TOVU_ADMIN_PASSWORD in .env, then docker compose build && docker compose up -d. One container serves the public site and the admin together.

• tovu deploy config --target fly|render|railway generates that platform's own config from the same Dockerfile, so all three stay in sync with each other.

• tovu export renders the public site to plain static files — no server, no database — for anyone who'd rather host the output than run the app.

• Every site's data — content.db, uploads, themes — lives in one folder. Copy it, back it up, move it. Nothing else to migrate.

What's on the roadmap

A managed path — one-click deploy of your folder to infrastructure Tovu operates, no server of your own to run — is planned, not shipped. Until then, self-hosting means running the container yourself.

What won't change

The important part: it stays your site. Managed hosting will be a convenience layer over the same portable folder — export to a standalone binary and walk away at any time. No lock-in is the point, not a feature we can quietly remove.

Related admin screens

Deployments configures where your site deploys and triggers a static export. Recovery captures restore points and rolls your site back to one if a change needs to be undone.