I run Portainer on three boxes. Two of them host about a dozen containers each, and the third is a staging box I rebuild whenever I am trying out a new image. Portainer was the easy button. I clicked, I added a stack, I moved on. That is exactly why the upcoming 3.0 release makes me nervous, because Portainer has decided to retire the Community Edition and the replacement is not as generous as the marketing copy sounds.
Here is the deal in plain English. Portainer is collapsing CE into the mainline product, and the mainline product is the one that has historically been sold to businesses. Instead of two tracks, there will be one. To soften the blow, Portainer is offering three free nodes of the mainline version to anyone who fills out a form. On paper, three free nodes is a fair shake. In practice, “free” with a sign-up form tends to be the first step toward “free if you call sales.”
What the announcement actually says
Portainer’s blog post is careful with its language, and that is part of the problem. The words “Community Edition” go away. The free version that ships with the new packaging is described as “free for up to three nodes” rather than “Community Edition, just renamed.” If you read the announcement on a phone screen while distracted, you would walk away thinking the Community Edition is still there. It is not. What is there is the same product that paying customers use, gated by node count rather than by feature.
Three nodes is enough for a lot of homelabs. If you have one box and you split your containers across two stacks, you are fine. If you have a Pi cluster and a couple of NUCs (a small, fanless mini PC the size of a paperback book) for redundancy, you are also fine. Where it stops being fine is anywhere you already had four or more Portainer endpoints, which is exactly the case for any homelab that grew like mine did.
- Three nodes cover most single-server homelabs and the casual cluster.
- Four or more endpoints, the kind that show up after a year of tinkering, will need a paid plan.
- The “free” tier is gated by a sign-up form, which is a sales funnel by another name.
Why the timing matters
Portainer 3.0 is not out yet. The Community Edition is the only thing available right now, and it works fine. That is the part people are missing. If you wait for 3.0 to land before you test a replacement, you will be panic-shopping during a release window, when documentation is thin and forum posts are mostly people saying “it broke for me.” Test your fallback now, while CE still installs cleanly, and 3.0 becomes a Tuesday upgrade instead of a Saturday project.
This is the same lesson I learned the hard way when Nextcloud dropped their old sync client without warning. The day you find out a tool you depend on is changing is not the day to find a replacement. It is also not the day to read the new pricing page and assume the worst. Read both, then act.
- 3.0 is the deadline, but it is also the moment you should plan around, not the moment you react to.
- Test your replacement while the old version still installs and works as advertised.
- Read the actual pricing page, not the headline, before you decide to pay or leave.
What I tested as a replacement
I tried four alternatives over the course of a week. Yacht was the prettiest and the easiest to install, but its auth model assumes you trust every account on your network, which is not a safe default for a homelab with shared services. Dockge is the opposite: it looks like a developer wrote it for themselves, and the YAML editor is the best of the four, but the visual layer is utilitarian in a way that will annoy anyone who is used to Portainer’s polish.
The third option, the one I am actually using as my primary, is the Docker CLI plus a self-hosted tool called Dozzle. Dozzle is a real-time log viewer for Docker containers, and it covers about half of what I used to open Portainer for. The other half (start, stop, restart, environment variables, stack management) I now do at the terminal with docker compose. It is not for everyone, but if you are comfortable in a shell, the CLI plus Dozzle is a tighter toolchain than any GUI.
The fourth option is to do nothing and pay for Portainer. If the team you have today already knows Portainer and you are not interested in retraining, the paid plan is probably cheaper than the lost hours. I am not paying yet, but I have not ruled it out.
- Yacht is the friendliest for first-time GUI users, and the weakest on access control.
- Dockge is the strongest for YAML-first homelabbers, and the ugliest on the screen.
- Docker CLI plus Dozzle is the leanest setup, and the one that teaches you something.
- Portainer paid is the path of least resistance, and a fair one if your time is worth more than the bill.
The trade I did not expect
I thought the biggest cost of switching would be the operational one: rebuilding my stacks, re-importing my environment files, getting used to a new interface. That cost was real but small, maybe an afternoon. The cost I did not expect was the social one. When Portainer was on the box, my partner could restart the Home Assistant stack without paging me. With Dockge, she can do the same thing. With the CLI, she pages me. That is a regression I did not plan for, and one I am now solving with a small wrapper script and a sticky note on the desk.
This is the part the announcement does not warn you about. Free tiers change, and when they do, the cost is rarely the new bill. It is the small things you built on top of the tool that quietly stop working.
Trade-offs
Portainer is not wrong to consolidate. Running two parallel products with overlapping feature sets is expensive, and the free tier was eating engineering time the company could have spent elsewhere. If you are a solo homelabber with one box, the new free tier is probably fine, and the announcement is a non-event. For larger setups, the math is different, and you have months to make the call.
Docker CLI is free forever, but it assumes you are comfortable at the terminal. Dozzle is also free, and the developer is responsive on GitHub, but it covers logs, not lifecycle. Yacht and Dockge are both community projects, which means they could go quiet the same way Portainer CE did. There is no version of this choice that locks you in for five years.
Migration took about half a day, mostly because I was being careful with environment variables. If you already have your stacks as docker-compose.yml files, your migration is mostly a UI exercise.
If you run Portainer on a single box and you do not mind a sign-up form, stay on the new free tier. If you run a multi-node setup, test your fallback now, not in November. If you just want the leanest possible setup that teaches you something, the CLI plus Dozzle is the answer.
Bottom line
Portainer 3.0 is the kind of change that is fine if you see it coming and a scramble if you do not. The Community Edition is going away. The replacement is free up to three nodes and gated by a form. If that matches your homelab, you are done with this article. If it does not, install Yacht, Dockge, or the Docker CLI on a test box this week and confirm the workflow before the deadline hits. That is the entire job.