No, DNN is not dead. The open-source platform is still being released, the major module vendors are still in business, and a great many companies run on it every day. It is also true that DNN is no longer the fashionable choice it once was. If you own a DNN site, here is an honest account of where things stand and what to do about it.
Why people ask
Three things make owners nervous. The developer who built the site has moved on and a replacement is hard to find. Web agencies pitching for work say DNN is old and offer to rebuild everything in whatever they happen to sell. And the site itself has been neglected for so long that it feels fragile.
Look closely and only one of those is about DNN. The other two are about who is looking after your site.
What is true about DNN today
The good. The platform is mature, which in software means the embarrassing mistakes were made and fixed long ago. It is free. Its handling of users, roles and permissions is still better than what most content management systems offer. The module vendors we rely on have supported their products for many years. And it sits on Microsoft ASP.NET and SQL Server, which are not going anywhere.
The honest weak points.
- The community is smaller than it was. There are fewer new modules and fewer forum answers than at DNN’s peak.
- Developers are scarce. DNN is a specialty, and most young developers have never used it.
- It runs on Microsoft’s older framework. DNN uses the .NET Framework, which runs only on Windows. Microsoft still supports it, but new Microsoft development has moved to the newer ASP.NET Core.
- Neglect is punished. A DNN site left without updates for years becomes hard to upgrade and easy to attack. That is true of every CMS.
Stay, upgrade or move? A quick test
| If this describes you | Then |
|---|---|
| The site works, staff like it, it is just out of date | Upgrade and stay |
| The site is fine but nobody is looking after it | Get a team behind it and stay |
| You are paying for Evoq and using little of it | Stay on DNN, move to the free platform |
| The custom modules are now the whole business system | Plan a move to a custom application |
| The site is only pages and a blog | WordPress is a reasonable move |
Most owners land in the first two rows. For them, replacing DNN is like replacing a car because it needs a service and the mechanic retired.
The alternatives to DNN
- WordPress. The right answer for content-only sites. A poor fit once logins, permissions and business data are involved. See DotNetNuke vs. WordPress.
- A custom ASP.NET Core application. The right answer when the site is really a business system. It costs more to build than staying put, and you get exactly what you need on Microsoft’s current platform.
- Another .NET content management system. There are several. Moving to one means rebuilding every custom module, so the case for it has to be strong.
What each move involves is set out on our DNN migration services page.
A word about Evoq
Some of the worry about DNN is really worry about Evoq, the paid edition, and its annual license. The free DNN Platform is a separate thing, and it is what we build on. The two differ in only a few features. When a client needs one of them, we add it. For Trailmark Bank, which wanted content approval, we wrote it as a custom module, and they did not have to license Evoq to get it.
Our advice
We work in DNN, WordPress and custom ASP.NET Core, so we are not tied to one answer. For most businesses with a working DNN site, the sensible course is to keep it, bring it up to date and make sure more than one person knows how it works. Rebuild only when the site has outgrown the platform.
If you would like a second opinion on your own site, book a 20-minute call. Keene Systems has built custom business software since 1987 and worked in DNN since 2004. See our DotNetNuke development services.
Frequently asked questions
Is DNN still supported?
Yes. The open-source DNN Platform continues to receive new releases and security fixes.
Should we move off DNN?
Only if the site is content-only, or has grown into a business system that the CMS now gets in the way of. An out-of-date site or a departed developer are reasons to upgrade and get support, not to rebuild.
What is the best alternative to DNN?
WordPress for content sites, and a custom ASP.NET Core application for business systems.
Can you still find DNN developers?
They are scarce, which is why a team is safer than one person. See how to hire DNN developers.

