Umono 0.9: my self-hosted CMS now has themes that can't touch your content
retained text
About eight months ago I posted Umono here, a self-hosted CMS built around one idea: keeping content, themes and plugins apart. It got a few thousand views and no comments, which was fair. It was mostly a story and a link. So this time, here is what it looks like and what it does today.
**What it is**
* An open-source (MIT) CMS. One Go binary and a SQLite file.
* Linux and macOS, x86\_64 and arm64. [umono.io](http://umono.io) runs on it, on an ARM64 VPS.
* A CLI that downloads a release, verifies its checksum, sets up a site and upgrades it later.
* Pages are written in Compono, Markdown with components. The admin panel previews the page as you type.
* A media library with local or S3-compatible storage. Images get resized variants.
**Built with AI, not vibe coded**
The flair says AI, so here is what that means. The code is written by AI agents, Claude Code and opencode. The design isn't. Umono is developed document-first:
* Every decision and spec is written before any code. That's where most of my time goes, and it's why the project moves slowly.
* An agent gets one small, concrete task from a spec: which file, which function, what behavior.
* Tests come first. A new test has to fail before the change and pass after it. There are about 700 golden tests for Compono, around 600 Go tests, and Playwright end-to-end tests for the admin panel.
* I review each change against the spec. Every change lands through a pull request on GitHub.
* Commits written with AI say so in their Co-Authored-By lines.
Vibe coding is prompting until something seems to work. Here the spec decides what "works" means, and the tests keep it that way. The specs are in my private notes, but the docs are written from them, and the code, tests and pull requests are public. Judge those.
**New in 0.9: themes**
A theme is only CSS, fonts and images. It styles a published page structure, called a contract, and it can't change what a page says or does. When you switch themes, every page changes its look and none of them changes its content.
There are two official themes: Octavo for simple sites and Folio for blogs (the screenshot above). You install a theme package with the CLI, and Umono checks it again before it activates it.
**Privacy defaults**
Public pages set no cookies and make no third-party requests. Fonts are served by the site itself, and the Content-Security-Policy allows nothing else. When you activate a theme, Umono verifies its contract with one request to umono.dev. It happens once per contract version, doesn't send your site's address, and umono.dev keeps no request logs.
**What it isn't yet**
It's stable enough to run [umono.io](http://umono.io), it has had regular releases since November 2024, and the CLI upgrades a site in place. But it's not feature-complete. Compono is still a language for technical users, there is no plugin system yet, and there are rough edges, like a menu you have to write on every page. I work on it full-time and keep releasing.
**Try it**
curl -fsSL https://umono.io/install.sh | sh
umono create my-website
cd my-website
umono up
Or download a release from GitHub. The docs walk you from an empty directory to a site with a theme: [https://docs.umono.dev/getting-started/your-first-site/](https://docs.umono.dev/getting-started/your-first-site/)
**What I'd like to know**
Nobody besides me runs Umono yet, so any real use helps:
* Where did you get stuck in the first ten minutes?
* Is writing pages in Compono a deal-breaker for you?
* What would you need before you'd run your own blog on it?
Feedback, questions and criticism are welcome here or in GitHub Discussions: [https://github.com/umono-cms/umono/discussions](https://github.com/umono-cms/umono/discussions)document fetched 2026-10-22 00:31 · canonical https://reddit.com/r/selfhosted/comments/1xbntnu/umono_09_my_selfhosted_cms_now_has_themes_that