{
  "id": 10387474,
  "title": "Portainer 3.0 Drops the Community Edition: What Self-Hosters Should Run Instead",
  "url": "https://urgent.news/2026/09/28/portainer-3-0-drops-the-community-edition-what-self-hosters-should",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-28T06:54:19.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/selfhostpilot/portainer-30-drops-the-community-edition-what-self-hosters-should-run-instead-22h8"
  },
  "original_language": "en",
  "account": "On 11 September 2026, Portainer CEO Neil Cresswell announced that Portainer 3.0 will drop the Community Edition. The 2.x line will be the last release for the Community Edition, and Portainer 3.0 will be a Kubernetes-first release with no separate Community Edition build. CE will continue to receive security patches and back-ports for now, but there is no fixed end-of-life date. Portainer argues that Docker and Swarm do not have the same capabilities as Kubernetes, such as network policies, pod security standards, and admission controllers. This will mean that Docker support is second-class in the UI and will not receive new capabilities. While Docker will still be supported, it will not get new features in the policy engine, GitOps engine, or observability layer.\n\nIf you are running Docker at home, you have a few options. You can stay on Portainer 2.45 CE and receive security patches and back-ports while the LTS line is supported. Alternatively, you can move to the free tier of Portainer 3.x, which uses a Kubernetes-first policy engine, GitOps, and observability. However, Docker support will be second-class in the UI and will not receive new capabilities.\n\nFor those looking for Docker-only alternatives, there are several options available. Dockge, Komodo, Arcane, Coolify, and Dokploy are all Docker-first tools that handle multi-server Docker deployments and can be used as alternatives to Portainer 3.0.\n\nIt is worth noting that RustFS 1.0 has been released, which is an Apache-2.0 licensed, Rust-based, S3-compatible object storage system. It is a drop-in replacement for MinIO and Amazon S3, and it claims to be 2.3x faster than MinIO for 4KB objects. However, it is recommended to test a full restore before trusting it with any data you cannot afford to lose.\n\nNavidrome 0.64 was also released on 12 September 2026, which adds an experimental Jellyfin Music API and a new artwork pipeline with blurred placeholders and a diagnostic CLI. However, before upgrading, it is important to back up your database first, as the migration touches every table and may cause issues for clients that cache item IDs.",
  "summary": "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…",
  "key_points": [
    "Portainer 3.0 will drop Community Edition, focusing on Kubernetes",
    "Docker support in Portainer 3.0 will be second-class with no new features",
    "Alternatives to Portainer 3.0 include Dockge, Komodo, Arcane, Coolify, and Dokploy"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}