Spots 
Three clients messaged me this week asking some version of "did Portainer just kill Community Edition?" Not exactly, but if you run Portainer CE on a homelab box or a client's Docker host, your upgrade path just changed.
Here's what happened with Portainer, why RustFS hitting 1.0 matters if you self-host S3 storage, and the Navidrome update you should back up before touching. Portainer 3.0 drops the Community Edition
On 11 September 2026, Portainer CEO Neil Cresswell published a post on the official Portainer blog titled "Portainer 3.0 is coming, and here's what it means for you." I read it twice, since I run Portainer for half my Docker clients, and the framing was blunt.
Portainer 2.45 LTS is the last release in the 2.x line, and Portainer 3.0 ships as a Kubernetes-first STS release with no separate Community Edition build. CE stays on 2.x and does not get 3.x features. Free access continues through the existing 3 Nodes Free program, not as a community-built release.
A maintenance build, 2.45.1 LTS, shipped on 17 September 2026 with security fixes and no new features. Portainer 3.0.0 arrives as an STS (short-term support) release, with a new 3.x LTS line later. Docker, Swarm and Podman still work in 3.x, but Portainer calls them "secondarily ordered" in the UI, and they won't get new capabilities in the policy engine, GitOps engine or observability layer. Every new product in the family, including Portainer-Run, Portainer-IDP, the Portainer-Command MCP gateway, Portainer-Operations and Portainer-AiGrid, is Kubernetes-only. See Linuxiac's writeup and heise online's coverage for outside takes. Why Portainer made the call
Cresswell's reasoning: keeping one codebase fully featured across Docker/Podman, Swarm and Kubernetes stopped being realistic. Policy management, the operations API and the internal auth model each had to be built three times, once per substrate. There's an AI-agent angle too. Portainer argues Docker and Swarm have no equivalent of Kubernetes network policies, pod security standards or admission controllers, the primitives you'd want to sandbox autonomous agents. That's why the new lineup only targets Kubernetes.
After the backlash, Cresswell clarified: "We are not abandoning Docker," and "nothing that works today gets ripped out of 2.x or the Docker environments in 3.x." He said that if Docker support ever reaches end of life, users will hear about it well in advance with a migration path. Worth stating plainly: the free tier going forward is a Portainer Business licence tied to an account, not a community-maintained build. The Portainer lifecycle docs track the support timeline. What this means if you run Docker at home
announced Move to Portainer 3.x free tier| Kubernetes-first policy engine, GitOps and observability, free via 3 Nodes Free| Docker becomes second-class in the UI and stops getting new capabilities Docker-first alternatives| Docker-only tools: Dockge, Komodo, Arcane, Coolify, Dokploy| You give up Portainer's Kubernetes option if you ever need it What I would actually run
For a single box, I run Dockge, the lightweight Compose stack manager from the Uptime Kuma author, holding a couple of stacks on a VM I built with my own Proxmox guide. It's MIT licensed, it edits compose files directly, and it starts in seconds on a Raspberry Pi. Mine sits behind my own reverse proxy, never exposed.
When I manage several client boxes and want GitOps, I reach for Komodo instead. It's GPL-3.0, it handles multi-server Docker deployments, and Dockge compose files port to it unchanged. Once you're juggling stacks across hosts, networking is what bites, which is why I still hand clients my Docker networking guide before they scale up. Arcane suits anyone wanting a modern Go-based UI, and Coolify or Dokploy cover git-push-to-deploy with automatic SSL. None of this is urgent: if your homelab runs Portainer 2.45 CE today, nothing breaks tomorrow. RustFS 1.0 is out, and MinIO left a gap
Three clients messaged me this week asking some version of "did Portainer just kill Community Edition?" Not exactly, but if you run Portainer CE on a homelab box or a client's Docker host, your upgrade path just changed.