NUR CMS brings modular headless content management to Rust backends

NUR CMS landed on the Rust Programming Language Forum as a headless CMS built to slot into Rust backends, not sit outside them. The project had already been in personal use for months, and its core pitch is modularity: it can be embedded as a library, keeps its own migration table name, and leans on SQLx 0.9 for database work.

That design choice gives the project a very specific shape. NUR CMS can run as a ready-made CMS with an admin panel and API endpoints, but it can also disappear into a larger Rust application as one backend component among many. It can even be used in a backend-rendered setup, where the admin panel is only one piece of the stack. The API can emit content as Markdown, HTML, or AST JSON, which makes the system easier to fit into different rendering pipelines without forcing one output format on every consumer.

The implementation details make the pitch more concrete. The GitHub repository describes NUR CMS as built with Rust and Vue.js, pairing an Axum backend with a Vue 3 admin panel and PostgreSQL storage. The README also lists Server-Sent Events, Markdown editing, automatic image resizing, and image output in AVIF, WebP, JPG, and PNG. Desktop users can preview Markdown directly in the admin interface, and configuration can be handled through environment variables or command-line arguments. That is the kind of boring machinery a CMS has to get right before anyone cares about the content model.

The caveat is that NUR CMS is not trying to be a public commons. The repository says it is open source but not a community project, with no support and no feature requests welcome, and the author echoed that stance by saying documentation is poor and support channels are closed off. Even so, the repository had 326 commits, which suggests active, sustained work rather than a weekend demo. For a side project or a self-managed content backend, that is a meaningful signal: the project is opinionated, usable, and already wired into real workflows, but it expects the person deploying it to own the experience end to end.

That is what makes NUR CMS interesting right now. It is not selling Rust as a trendy CMS language; it is showing how a Rust backend can already take on migrations, content formats, image processing, and admin workflows without surrendering modularity.