DNN

What DNN is

DNN is an open source content management system for the Microsoft stack. The community site, which calls itself the "Official DNN CMS community website", carries the headline "The #1 Open-Source CMS, Based on Microsoft Technology", a claim made by the site itself. It is "for and by the DNN community", and the pages describe an organization called the DNN Association, supported by the .NET Foundation, rather than a company selling a hosted product. The reader this fits is a Windows, IIS and SQL Server shop, usually with developers or an agency, building websites, intranets and portals with a CMS that editors can run day to day. The pages do not name a company headquarters.

What you build and how

DNN is a site and portal builder with a CMS at the core. The community's comparison page against Umbraco is the clearest description of how it works, and it is worth reading with the caveat that the DNN community wrote it.

Editing. The comparison says DNN "emphasizes on-page management with page/module permissions". Editors work on the page itself, and the proof-of-concept checklist on that page has you add two pages, place components or modules, and reorder them by drag and drop. Publishing includes publish and unpublish and a scheduled publish time. One recent forum thread mentions pushing JavaScript into the head tag of all pages through the Persona bar, DNN's admin interface.

Permissions. The page lists "granular RBAC down to the module/component level for editors and departments" as a reason to pick DNN. Roles are created, then page or module permissions are applied to them.

Multiple sites. DNN "supports multiple sites ('portals') in one install", and the page pairs that with "delegated governance". One installation can host several sites, which suits an agency, a university with departments, or a company with regional sites.

Extensions. DNN uses packaged "Modules/Themes/Containers, Providers, Scheduled Jobs, JS Libraries". Packages install and upgrade through a defined path, and a built-in scheduler runs background jobs. The homepage links a DNN Extensions listing for third-party extensions and a "Build DNN Extensions" section of the documentation. Recent forum posts mention extensions for forms and mega menus, plus the 2sxc and OpenContent modules. A thread on a form builder for DNN 10 shows a community member pointing to a third-party form product. If you want a blog, a form, a shop or a custom skin, you will install or build one of these.

APIs and headless. On the comparison page, DNN lists "Web APIs; services; varies by implementation". The same table says Umbraco has a built-in Content Delivery API, so a team that needs headless delivery from day one should read that row closely.

Platform and hosting. DNN is listed as "Open-Source .NET Framework", aligned with "Windows + IIS; SQL Server / Azure SQL". The page says "Releases/LTS: community releases", and advises validating the upgrade path against your customizations and packages. A community member's forum comment calls DNN "stable, strong but heavy on first load" and worries about the move from the .NET Framework to .NET Core. That is one user's opinion, not a statement from the project, but it shows the question people ask. A community project named the MVC Pipeline is in progress. A post thanks sponsors who gave money and time to it, and the project was a focus of DNN Connect 2026 in Louvain-la-Neuve, Belgium, a four-day event in May.

Community. The homepage links the installer on GitHub, community documentation, forums for "Community Support for all DNN Platform related questions", a Discord server with weekly events such as Open-Source Co-coding and Casual Coding Saturday, community blogs and a Show and Tell meetup on the first Tuesday of the month. A Technology Advisory Group meets every other week and publishes recaps. Navigation also lists Agencies and Consultants, MVPs and Contributors, Showcase, Roadmap, History and Security and Compliance pages. The site shows "DNN Community Forums 10.01.00" as a current release of its forum module, and forum threads mention DNN 10.

The evidence from the pages

• Price and license. The comparison table lists licensing for DNN as "Open source; community-governed". No price, no paid tier and no named license appear in the pages held. The same table says Umbraco is open source under MIT, a fact about Umbraco, not DNN.
• Hosting. DNN is not offered as a hosted product on these pages. The comparison lists Windows, IIS and SQL Server or Azure SQL as the primary stack. Umbraco, by contrast, is listed with cloud and hosted options.
• Governance. Copyright 2026 by DNN Association, supported by the .NET Foundation.
• Fit statements. DNN "can be a strong fit when" operations standardize on Windows, IIS and SQL Server or Azure SQL, when you need granular role-based permissions, when you prefer packaged extensions with a clear install and upgrade path and a built-in scheduler, and when you plan multi-site or portals from one installation.
• Compliance. A Security and Compliance link is in the navigation. The pages held name no certifications.
• Events. DNN Connect 2026 returned to Belgium, and a note says DNN Summit 2025 will return next year.
• Extension examples named on the pages. DnnGo, EasyDNNnews, PlantAnApp, 2sxc and Evotiva DnnBackup are demonstrated at Show and Tell sessions.

Who it suits and who it does not

DNN suits an organization that already runs Windows, IIS and SQL Server and has .NET developers, or an agency that wants one install hosting many client sites, with permissions that reach down to a single module. It suits an intranet team with several departments that need delegated control, and a team that values a community-run open source project with public releases and a roadmap.

It is a weaker fit for someone who wants to assemble a site with no developer at all, because extensions are packages that someone installs and configures. It is also a weaker fit for headless-first projects, since the comparison page itself says the API story varies by implementation. Teams that want cross-platform hosting on ASP.NET Core may prefer to compare the alternative the page describes, and the pages say community releases need planning around your customizations. Support comes from forums, Discord and consultants, not a vendor contract.