Bring Serene Bach assets forward
Template compatibility with Serene Bach v3 is a core goal, so existing design assets and publishing habits can keep working.
Self-hosted weblog engine
Serene Bach v4 is a Go weblog engine that runs as a single binary over CGI or HTTP. Write from the browser, keep SQLite on your server, and rebuild static HTML when your workflow calls for it.
For people who want browser-based publishing without carrying a large CMS stack.
It keeps the CGI-era ability to place your blog almost anywhere, with SQLite, static rebuilds, and AI integration added in.
Positioning
Serene Bach is for personal blogs and small sites that want browser-based editing without carrying a large CMS stack.
| Serene Bach | WordPress | Hugo | |
|---|---|---|---|
| Runtime | Go single binary / CGI / HTTP | PHP + database server | Static generator |
| Placement | Shared host, VPS, Raspberry Pi | PHP and MySQL hosting | Static hosting |
| Updates | Publish from the admin UI | Publish from the admin UI | Edit files and rebuild |
| Dependencies | No external DB server, SQLite | PHP, MySQL, plugins | Build tools and themes |
| Operations | Small surface area | Ongoing updates and hardening | Light, file-based workflow |
Quick start
go mod tidy
task seed
task dev Why Serene Bach
Template compatibility with Serene Bach v3 is a core goal, so existing design assets and publishing habits can keep working.
Pure Go SQLite is embedded, so there is no external database server to run. HTTP server mode and CGI support make it practical on a small VPS, a local box, or traditional shared hosting.
Rewrite, continue, summarize, suggest titles, tags, and keywords, and generate image alt text from the posting workflow.
Migration
Import from a Perl-era Serene Bach 3 SQLite database and keep the familiar template model. The goal is to preserve old design assets and publishing habits while moving the runtime to Go.
AI writing assist
AI assist is built into the entry editor rather than living in a separate app. You can choose OpenAI-compatible APIs, LM Studio, Ollama, or Claude, so cloud APIs and local LLMs are both viable.
API keys are encrypted on the server. AI settings are per-user, so the whole blog does not have to become AI-first just because one author wants assistance.
MCP / llms.txt
Deploy small
Run it on a small VPS, Raspberry Pi, CGI-capable shared host, or static host. Write from the admin UI, then rebuild static HTML when your publishing workflow calls for it.
Data ownership
Entries, settings, and analytics live in SQLite and local files
Images and templates remain server-side data you can back up
A self-hosted setup that is less dependent on external platform decisions
Get started
go mod tidy
task seed
task dev View on GitHub