FluentCMS is an open-source, MIT-licensed content management system built on ASP.NET Core and Blazor, intended for .NET developers and content teams that want a self-hosted CMS which can also act as a headless content backend.

What it is

FluentCMS is a content management system written in C# and built on ASP.NET Core and Blazor, distributed under the MIT licence. It lives in the ASP.NET Core and Blazor ecosystem, and the repository topics place it squarely among Blazor application, Blazor server, Blazor client-side and CMS framework projects. It is positioned to work both as a traditional content-based CMS, where writers manage content through a dashboard, and as a headless CMS, where content is exposed through an API-first design to decoupled front ends.

The concrete problem it addresses is the absence of a ready-made content back office inside a .NET application. Rather than building content types, page layouts, media handling, user and role management, multi-site administration and application settings from scratch for each project, a .NET team can run FluentCMS as the content layer and either use its Blazor-based interface directly or consume it headlessly. It covers the ground conventionally occupied by a general-purpose CMS in a stack, while staying inside the ASP.NET Core toolchain and the .NET SDK a C# team already uses.

Key capabilities

• A custom, independent Blazor-based component library styled with the Flowbite design system, documented in /src/Frontend/FluentCMS.Web.UI.Components/.
• Headless, API-first operation for decoupled applications alongside the built-in content dashboard.
• Database selection through the Database key in appsettings.json, with LiteDB and MongoDB currently supported and SQLite, SQLServer, MySQL and PostgreSQL listed as coming soon; connection strings are supplied under ConnectionStrings as DefaultConnection.
• Content type definition with custom fields, plus creation, editing and management of content and pages with custom layouts.
• Multiple site support, with several sites managed from a single dashboard, and multi-language content management.
• Media management covering upload, organisation and handling of media files.
• Role-based access control with granular permissions, user management, role management and application settings configuration.
• Extensibility through custom plugins and themes, with a dedicated plugin management area, plus built-in SEO tools.

Who uses it and how

• ASP.NET Core teams that need content administration inside an existing .NET application and prefer to stay in the same runtime rather than adopt a separate technology stack.
• Content writers and editors working through the dashboard, supported by role-based access control that separates permissions between users and roles.
• Organisations running several sites or several languages, which can be administered from one dashboard instead of separate installations.
• Headless deployments, where front ends are decoupled from the CMS and consume its API-first output.
• Small deployments that avoid a database server entirely by using LiteDB, configured with a single file connection string such as Filename=./fluentcms.db.

Getting started

Clone the repository, navigate to FluentCMS/src/FluentCMS/, set the database type and connection string in appsettings.json, then run dotnet run and open http://localhost:5000. The prerequisite is the .NET SDK 9.0 or later; no Docker image or compose file is documented.

How it compares

The facts provided do not name any similar tool or any paid product that FluentCMS replaces, so no head-to-head comparison on licence, hosting or cost model is possible here. It stands alone in this registry.

When to use it — and when not to

A self-hoster must operate the .NET SDK 9.0 or later runtime and a database, choosing either a LiteDB file or a MongoDB instance, since neither Docker nor a documented hosted option is available in the repository. Teams that require SQLite, SQL Server, MySQL or PostgreSQL today should wait, because all four are listed as coming soon, leaving only LiteDB and MongoDB as working choices. The documentation is still being expanded, so expect to work from the source, the component library README and CONTRIBUTING.md rather than a complete manual.

</a>