Cofoundry is an open-source, MIT-licensed CMS and application framework for .NET Core, built around code-first development and aimed at .NET teams that want content management integrated directly into their own ASP.NET Core application instead of running beside it as a separate system.
What it is
Cofoundry is a content management system and application framework written in C# and published under the MIT licence. It lives in the .NET and ASP.NET Core ecosystem — its topics list asp-mvc, asp-net, asp-net-core, dotnet, dotnet-core, csharp and cms — and positions itself around four stated principles: code-first development, unobtrusive integration into your application, an extensible and flexible architecture, and simple, user friendly content management. The project is developed at github.com/cofoundry-cms/cofoundry, documented at cofoundry.org/docs, and has accumulated 902 stars and 168 forks, with 115 open issues at the time of writing. Its administrative surface ships as the Cofoundry.Web.Admin NuGet package, and the repository carries a GitHub Actions build workflow (build.yml) with a published status badge.
The concrete problem it addresses is the split that appears when a .NET application needs managed content but the CMS is a separate product with its own database, its own deployment and its own content model. Cofoundry folds that layer into the application itself: content definitions are expressed in code inside the codebase, and the CMS is added to an existing ASP.NET Core application rather than the application being built to fit around the CMS. The README describes this as unobtrusive integration, which is the specific thing being replaced — the external CMS installation that an application must be wired up against.
Key capabilities
- Code-first content modelling, so content definitions live in the application codebase alongside the rest of the source.
- Unobtrusive integration into an existing ASP.NET Core application, per the project's own stated focus.
- Extensible and flexible architecture, listed as a core design goal in the README.
- A user-facing content management interface distributed as the
Cofoundry.Web.Admin package on NuGet.
- Support for ASP.NET MVC and ASP.NET Core application stacks, reflected in the repository topics.
- Continuous integration through the GitHub Actions workflow at
.github/workflows/build.yml, with a build status badge.
- Public roadmap tracking via GitHub milestones, plus contributor guidelines in
CONTRIBUTING.md.
Who uses it and how
- .NET teams building or maintaining an ASP.NET Core application that needs editable content without adopting a separate CMS platform.
- Projects that want content structure reviewed, versioned and deployed through the same source control and release process as application code.
- Developers adding content management to an application that is already in production, where the integration must not disturb the existing structure.
- Teams on the .NET stack that need the admin UI installed as a package rather than provisioned as its own service.
- Contributors and integrators who follow the repository's
CONTRIBUTING.md guidelines and track upcoming work through GitHub milestones, the project blog and the listed support channels.
Getting started
Install the Cofoundry.Web.Admin NuGet package into an existing ASP.NET Core application and follow the setup instructions at cofoundry.org/docs, which the README names as the entry point for getting started.
How it compares
The facts provided do not name any comparable tools or any paid products that Cofoundry replaces, so on that basis it stands alone in this registry. Anyone evaluating it should compare it against whatever CMS options they are already considering, using the criteria the project itself documents rather than any comparison supplied here.
When to use it — and when not to
The README is deliberately brief and defers almost everything to the external documentation site, so the details needed to judge fit are not visible from the repository alone. Cofoundry is also still on 0.x releases, which the README states are considered early development: breaking changes can happen at any point, with patch releases treated as non-breaking and minor releases as potentially breaking, documented in release notes. Teams that need a stable 1.0 API guarantee, that work outside the .NET and ASP.NET Core stack, or that want a CMS they do not have to run and maintain as part of their own application should look elsewhere; teams already committed to .NET and comfortable tracking a pre-1.0 dependency are the intended audience.
