Portainer Severs Open-Source Community Edition From Kubernetes-First Version 3.0

A decade of open-source development for Portainer's Community Edition is coming to an end. The company has announced that its forthcoming Portainer 3.0—a complete architectural overhaul centered on Kubernetes—will not extend to the Community Edition. Instead, CE will remain anchored to Portainer 2.45 LTS, the final release in the 2.x series, according to CEO Neil Cresswell.

The Community Edition will receive ongoing security patches, bug fixes, and selective backports of 3.x features, but only those that correspond to Docker API equivalents. Full feature parity between the editions is not planned, since some 3.x capabilities rely on Kubernetes primitives that Docker lacks.

The reasoning behind the split

Cresswell frames this as a maintenance challenge rather than a business strategy shift. The development team previously had to build each new policy or API capability three times over—once for Kubernetes, once for Swarm, and once for Docker and Podman environments. This triplication created significant overhead.

Portainer 3.0 discards this unified approach in favor of five separate consoles, each purpose-built for a specific operational context rather than a single interface attempting to handle all scenarios.

Cresswell explains that the Community Edition simply cannot fit within this new structure. He states that "releasing that as CE would misrepresent what it is and who it is for," noting that Portainer 3.x's policy framework, operations API, and enterprise-oriented consoles are designed with enterprise users as the primary audience from the outset.

What changes for existing users

For those currently operating Docker environments, the immediate impact is minimal. Version 2.x continues to function as before and will receive security updates; remaining on the current version is a fully supported path forward.

Users who migrate to 3.x will find that Docker, Swarm, and Podman environments continue to work as native connection types. For those preferring Docker-style tooling while running Kubernetes underneath, Portainer-D2K serves as a compatibility bridge, enabling Docker Compose and related tools to deploy and manage applications on Kubernetes clusters.

Future development in observability, GitOps, and policy tooling will prioritize Kubernetes environments, leaving native Docker setups with a lower position in the interface hierarchy and no access to these emerging capabilities.

For users seeking new functionality without transitioning to Kubernetes, options are limited. The only free path to 3.x runs through 3 Nodes Free, Portainer's existing node-limited license tier for the closed-source Business Edition—not an open-source Community build.

Alternatives to consider

For those unwilling to remain indefinitely on version 2.x, other projects are actively being developed that warrant evaluation. Neither represents a complete substitute for every Portainer use case, particularly for deployments that depend on Portainer's extensive Kubernetes feature set. However, for homelab environments or modest Docker and Swarm setups where the primary need is a capable self-hosted interface without premium features, both merit investigation.