You shouldn't have to pick a side.

$ docker run -p 3000:3000 \    -e TACHYON_DATABASE_URL=postgres://… \    -e TACHYON_PUBLIC_URL=http://localhost:3000 \    ghcr.io/tachyon-cms/tachyoncms:v0.1.0listening addr=0.0.0.0:3000setup needed: create the first Admin with  POST /api/setup

POST /api/setup{ "email": "[email protected]", "name": "You",  "password": "a long passphrase you will remember" } { "email": "[email protected]", "id": "01a18406-4df1-…",  "name": "You", "role": "admin", … } POST /api/setup (again)409 Setup has already been done. Sign in instead.

The choice you’re usually handed

Some CMSs are built for developers: typed, API-first, a pleasure to code against, and baffling to whoever has to publish the Tuesday newsletter. WordPress is built for the editor, and you pay for that ease in plugins, patches and page speed.

I don’t think you should have to choose. TachyonCMS aims at three things at once.

Fast, and you can see why

It’s Rust on Axum and Tokio, one binary with Postgres beside it, and published content is read from a single row. That’s an argument from how it’s built, not a number. Reproducible benchmarks against the popular CMSs come first, method and all, and only then will I quote one.

Safe, by default rather than by checklist

There’s no unsafe code; the compiler is told to refuse it. Fixed queries are checked at compile time, filters and sorts are built from a validated tree, and every value a request sends travels as a bound parameter. Access rules go into the SQL itself, so a hidden document never leaves the database. Security has the rest, including how to check a release before you run it.

Easy for editors, which is where it’s headed

The admin isn’t built yet. The bar it has to clear is that someone who has only used WordPress picks it up without training. For editors tells that story from the editor’s chair: what’s planned, and what’s already underneath.

What you can run today

• An API that appears the moment you define a content type, with twenty field types.
• Filters, sorting, cursors and populated links, trimmed to what the page needs.
• Access rules down to a single field, compiled into the query.
• Sessions, scoped API keys and passwords checked against known breaches.
• A schema file you can diff in a pull request, where renames keep their data.

Linux and macOS binaries and a Docker image come with every release, signed.

Early, and open about it

TachyonCMS is pre-alpha and MIT licensed. The content API, sign-in and access rules work; the admin, media, drafts and GraphQL don’t exist yet, so keep it off public networks for now. If that’s the stage you like to join a project at, the door’s open.