The unacceptable stagnation of NextDNS: Is this project abandoned?

This complaint is written out of profound frustration and severe disappointment regarding the current state of NextDNS. For users heavily relying on this service for network-wide protection and router-level DNS filtering, the absolute silence and lack of meaningful updates from the development team have become entirely unacceptable. It has been an incredibly long time since any real innovation or new features were added to the platform. While the core DNS resolution and blocklists still function, the platform itself feels completely abandoned.
Competitors are rapidly evolving, introducing advanced analytics, better interface options, deeper router integrations, and modern security protocols. Meanwhile, NextDNS remains stubbornly stuck in the past. Users are left with the exact same dashboard, the exact same feature set, and the exact same limitations that existed years ago. Where is the roadmap? Where is the communication from the developers? There is a growing consensus in the community that the project is on life support.

Entire network privacy and security architectures are entrusted to this service. Routers are configured, clients are deployed, and infrastructure is built around NextDNS, yet there is zero reassurance that the platform is actively maintained beyond merely keeping the servers online. The lack of transparency is absolutely alarming. Simple feature requests highly upvoted by the community have been ignored for years. Critical bug reports sit unresolved.
The IT and networking landscape changes rapidly, especially concerning encrypted DNS, malicious domain tracking, and zero-day threats. A security product cannot afford to remain stagnant. If it is not moving forward, it is actively falling behind. This stagnation is a serious technical failure that cannot be disputed. Relying on a static tool in a dynamic threat environment is a massive technical risk. The ecosystem needs active development, not just a service running on autopilot.

It is deeply disappointing to see a product with such incredible initial potential slowly fade into irrelevance simply because active development ceased. The community deserves a clear, honest answer about the future of this platform. If active development has concluded, transparency is required immediately so networks can be migrated to alternative solutions that actually prioritize progress, system updates, and user feedback. This lack of evolution is a technical reality that cannot be ignored or tolerated any longer.