Architecture 2026-11-15·Ievgenii Svyryd

Why Rustango-CMS: an honest comparison

Where Rustango-CMS beats WordPress, Wagtail, Strapi and Payload, where it does not yet, and the benchmark numbers behind both.

Why Rustango-CMS: an honest comparison

Rustango-CMS is a page-tree content management system written in Rust. I built it after years of shipping Wagtail and Django sites, and I wanted the same editing model without the server bill, the plugin hunt and the runtime surprises. This post makes the case for it, and it is just as clear about where it is not the right choice yet.

The short version

  • Choose Rustango-CMS when you want one fast, small, self-hosted program that gives editors a real admin and gives developers typed content, a headless API and an AI-agent interface, all in one box.
  • Choose something else when you need a large plugin or theme marketplace, a big hiring pool, a hosted SaaS, or years of production history behind every feature.

What you get in the box

FeatureRustango-CMS
Page tree with typed page typesYes: defined in Rust, or built in the admin without code
Block editor with live previewYes, with an outline of the page and validation as you type
Headless JSON APIYes, with a draft preview mode for your own frontend
Content translationYes, per locale; the admin itself speaks six languages
FormsVisual form builder, submissions stored and emailed
Members areaSign-up, email confirmation, password reset, Google sign-in, page gating by permission
Revisions, scheduling, workflowYes
Media libraryImages with automatic renditions, documents
SEOPer-page metadata, sitemap, redirects, robots.txt
Multi-tenant hostingMany sites from one process, each with its own database and theme
AI agentsA built-in MCP server; each key acts with its owner's permissions
DatabasesSQLite, PostgreSQL and MySQL from the same code
DeploymentOne binary plus templates and a database

How it compares

The table compares architecture, not quality. Each of these projects is mature and well loved, and each makes different trade-offs.

Rustango-CMSWordPressWagtailStrapiPayload
LanguageRustPHPPython (Django)JavaScript / TypeScript (Node.js)TypeScript (Next.js)
RenderingYour templates, or headlessThemes, or headlessYour templates, or headlessHeadless onlyNext.js, or headless
Page treeYesPages nest; posts are a flat listYesNo, collectionsNo, collections
Content types defined inRust code or the adminPlugins and custom post typesPython codeThe admin or codeTypeScript code
Type checking of content modelsAt compile timeNoNoPartly (TypeScript)Yes (TypeScript)
DatabasesSQLite, PostgreSQL, MySQLMySQL / MariaDBPostgreSQL, MySQL, SQLitePostgreSQL, MySQL, SQLitePostgreSQL, MongoDB, SQLite
Runtime to installNone: one binaryPHP + web serverPython + WSGI serverNode.jsNode.js
EcosystemSmall and newHugeLargeLargeGrowing
Maturity0.x, public since October 202620+ years10+ years10 yearsSeveral years

What this means in practice:

  • Against WordPress, the win is speed, memory and safety: no PHP, no plugin chain to keep patched, and content types that the compiler checks. The loss is the ecosystem: WordPress has a theme or plugin for everything, Rustango-CMS has a small set of built-in features.
  • Against Wagtail, the editing model is close (page tree, typed pages, blocks), and that is deliberate. The win is a fraction of the memory, no Python runtime, and a few things Wagtail leaves to packages or to you: public member sign-up, an MCP server for AI agents, and a separate database per site. The loss is the Django ecosystem and a decade of production use.
  • Against Strapi and Payload, the difference is shape. They are collection-based and API-first; Rustango-CMS is page-tree-first and renders HTML itself, with the API as a second door. If your site is pages, Rustango-CMS fits more naturally. If your product is an app with a content backend, they are a better match.

Performance

Two sets of numbers, and it matters which is which.

The engine. Rustango-CMS runs on the Rustango framework. In the fair benchmark, every app served the same blog with the same data and the same HTML, on the same machine, in the same run:

Same run, same blogUncached index, req/sCached index, req/sMemory under load
Rustango (framework, actix)6 341200 167~7 MiB
WordPress59921 285142 MiB
Laravel · Octane1 0985 884241 MiB
Python · gunicorn69711 012224 MiB

That is about 10× WordPress on uncached pages, about 9× on cached ones, and a twentieth of the memory. These are framework numbers on a test blog, not the CMS itself, and round 2 has since made the framework faster still.

The CMS itself. The Rustango-CMS documentation site, measured on a laptop with SQLite and 64 concurrent connections:

Rustango-CMS, docs sitereq/s
Blog index, from the page cache73 837
Documentation page, from the page cache63 191
JSON API, rendered from the database1 380
Documentation page, rendered from the database795

The median response from the page cache is under 1 ms, a page rendered from the database takes 2–4 ms for one visitor, and the whole site with its admin uses about 36 MB of memory at rest. There is no head-to-head CMS benchmark against WordPress yet, so do not read the two tables as one.

The honest caveats

  • It is young. Version 0.x, public since October 2026. Expect some changes between minor versions, and read the changelog when you upgrade.
  • The community is small. You will not find thousands of answers online, and most features have been used in production by a handful of sites, not thousands.
  • No marketplace. There are starter themes and a set of built-in features, not a plugin store. Anything missing, you build in Rust or in templates.
  • Developers need Rust for page types defined in code, custom routes and admin screens. Editors and site managers do not: they can build page types in the admin.
  • Compile times. A first build takes minutes; a changed template does not need one.
  • Hosting is DIY. You run the binary on a server or in a container. There is no hosted service.

Who should use it

  • Teams building content sites who want them fast, cheap to run and easy to keep secure.
  • Rust shops that want a CMS in the same language as the rest of their stack.
  • Agencies running many small sites, where multi-tenant hosting turns ten servers into one.
  • Anyone who wants an AI assistant to draft content inside the rules of the site.

Try it

cargo install rcms-scaffold
rcms new mysite --template blog
cd mysite && cargo run -- makemigrations
cargo run -- quickstart

The getting-started guide takes about twenty minutes, and the source is on GitHub.

Зв'язатися →