Portainer Frozen Community Edition Development
The company halted open-source development at version 2.x to focus exclusively on a new Kubernetes-based platform.
Updated on Sept. 21, 2026 in Software
Live Poll
Do you trust companies to keep open-source software free for users over the long term?
Portainer has ceased new development for its open-source Community Edition, capping the project at version 2.x. The platform will remain anchored to the 2.45 LTS release while the company shifts its primary focus to a closed-source architecture centered on Kubernetes.
Why it matters
The company transitioned away from the open-source model to reduce maintenance complexity caused by managing separate features for Docker, Swarm, Podman, and Kubernetes. Leadership determined the enterprise-oriented 3.0 architecture was fundamentally incompatible with the existing community framework.
The new 3.0 platform architecture replaces the previous interface with five distinct consoles designed for specific job functions. Future updates for the open-source edition will be strictly limited to security fixes, bug fixes, and Docker API-compatible backports.
The players
Portainer
Portainer is a software company that provides management platforms for containerized applications.
The details
The shift prioritizes Kubernetes-specific primitives over native Docker setups, with new observability, GitOps, and policy tooling slated to debut exclusively on Kubernetes. While the open-source development has stalled, Portainer continues to offer a free node-capped license for its closed-source Business Edition.
Timeline
Development of the open-source model spanned from 2016 through 2026.
The freeze of Community Edition development was announced on September 21, 2026.
The Tech Race
This pivot reflects a broader industry trend where software vendors abandon multi-platform support to prioritize Kubernetes-native infrastructure. By narrowing its focus, the company aims to move past the technical debt of maintaining legacy compatibility layers across fragmented container runtimes.
Users relying on the open-source Community Edition will no longer receive new feature updates and must rely on the 2.45 LTS version indefinitely. Those requiring advanced features like GitOps and policy tooling for Kubernetes must now transition to the closed-source platform or seek alternative tools.
The takeaway
Developers should evaluate whether their existing Docker-based workflows can remain sustainable on the legacy 2.45 LTS version. Planning a migration to a platform aligned with long-term support roadmaps is now essential for those requiring ongoing feature innovation.
Further reading
Learn more about the latest industry shifts in the Software section.
Source note: This article includes information reported by It's FOSS.
Live Poll
Do you trust companies to keep open-source software free for users over the long term?
