A CMS written in Rust, shipped as one program
A CMS written in Rust, shipped as one program
Most content management systems are a stack: a language runtime, a database server, a web server and a pile of plugins that each need patching. Sophia Stack X is a CMS written in Rust that ships as one executable. That program is the admin, the web server, the site builder and the package tool. Its database is a SQLite file it makes for you.
This page explains what that means in practice, what Rust does and does not buy you here, and what you give up.
What is in the program
One file, sophia, does the work of several parts:
- The admin. A page builder with a live preview, a Design screen for colors and fonts, a Publish screen, an Import screen, accounts, backups and an audit log.
- The web server. It answers on its own port and picks a site by host name, so one install can serve several sites. On a server it sits behind nginx or Caddy, or the installer sets that up.
- The build system. Publishing renders every route into a numbered release of plain files and checks links first.
- The package tool. Extensions are built, checked and signed with the same file:
sophia new,sophia check,sophia pack. - An MCP server.
sophia mcpgives AI agents 55 tools to work on the site. See a CMS AI agents can run.
Everything else lives in one data folder: a SQLite database, uploaded files and published releases. Backup is sophia backup, and restore is sophia restore.
What Rust gets you
The honest list is shorter than the marketing for most Rust projects, so here it is.
One file to deploy. Rust compiles to a native executable. The Linux build is fully static, so it runs on any 64-bit Linux without installing libraries. There is no PHP or Node to install, version or patch on the server.
Small, steady memory. On our test machine an idle server used about 13.5 MiB and 24 MiB under 32 connections on a published page. Those are our own numbers from one computer, with the method written out on the benchmarks page.
Memory safety. Rust prevents whole classes of memory bugs in the program's own code. It does not remove other bugs, such as logic errors or a missing permission check. Security here also comes from design: the site visitors see is plain files, extensions are sandboxed, and updates must be signed. See Security and backups.
Fast start. The server answered its first request about half a second after launch in our test.
What Rust does not give you: a library of ready-made themes, or a community the size of PHP's. That is the trade, and it is why extensions are JavaScript.
Extensions in JavaScript, not Rust
You do not need to know Rust to extend Sophia Stack X. An extension is a folder with a manifest, templates and optional JavaScript that runs in a sandbox. The sandbox is a small JavaScript engine inside the program, with no Node, no npm and no build tool. The code can reach only the permissions its manifest declares, such as data or mail, and the site allows.
sophia new app tickets
sophia check extensions/tickets --json
The program checks the manifest, parses templates and compiles the script, then packs and signs it. The extensions guide has the manifest and the calls code can make.
SQLite, on purpose
One database file means one thing to back up and nothing to run alongside. SQLite handles a lot of reading, and most of a site's traffic never reaches it, because visitors get the published files by default. Sites that need many writers at once, such as a very large shop, should look at the limits before choosing it.
What you give up
- It is not open source. You can use it free for any site, including client work, and what you make is yours. You cannot read the source or fork the program. The license has the details.
- It is new. The first version is 0.1.0, and the changelog shows what shipped and when.
- The ecosystem is small. The marketplace lists packages reviewed by SOPHIA XT. There is no directory of thousands.
- Self-hosted. You run it. SOPHIA XT does not host it for you.
- The Windows program is not code-signed yet, so Windows may warn on first run. Verify a download shows how to check it.
Try it
You can run it in about two minutes. Download the program, open it, and fill in one setup page. Or try a private bakery site in the live demo for an hour, with nothing to install. If you are weighing it against something you know, read the comparison with WordPress, Joomla and Ghost. If you plan to run it on your own server, see a self-hosted CMS.