Dora NodaA 30-developer team that just crossed 250 employees, or closed a fiscal year over $10 million in revenue, owes somewhere between $5,400 and $8,640 a year for a tool that cost nothing the day before. That's Docker Desktop's Team tier ($15/user/month) at the low end and Business tier ($24/user/month) at the high end, billed to every developer who runs it — not because Docker shipped a new feature, but because the company itself grew past a line drawn back in 2021 and enforced since January 2022. It's still the rule in 2026, and it still catches teams that never rechecked it after the year they crossed.
The Rule, Precisely
Docker Desktop is free for individual developers, education, and noncommercial open-source work, regardless of who's behind it. It is also free for any company below both of two thresholds: fewer than 250 employees and less than $10 million in annual revenue. The moment a company crosses either threshold — headcount or revenue, whichever it hits first — commercial use of Docker Desktop requires a paid subscription: Pro ($9/user/month annual, $11 monthly), Team ($15/user/month annual, $16 monthly), or Business ($24/user/month).
Two details trip up teams doing the math for the first time:
- Eligibility is company-wide; billing is per user. A 3,000-employee company with two developers who happen to open Docker Desktop owes two seats, not 3,000. The size test decides whether you owe anything; the invoice itself only counts people actually running the tool.
- It's an OR, not a sequence. A bootstrapped 40-person startup with $12M in ARR crosses on revenue alone, headcount irrelevant. A 300-person company pre-revenue crosses on headcount alone. "Whichever comes first" means literally whichever metric your company happens to cross first — there's no requirement to hit both.
What It Actually Costs a Mid-Sized Team
Take a company that just tipped past 250 employees, with 30 developers actively using Docker Desktop day to day. Team tier — the minimum that supports centralized settings management, which most companies this size want — runs:
30 users × $15/month × 12 = $5,400/year
Business tier, which adds SSO, SCIM provisioning, and enforced Desktop security policies (the tier a compliance-conscious org this size typically ends up needing anyway), runs:
30 users × $24/month × 12 = $8,640/year
Pro tier is the theoretical floor at 30 × $9 × 12 = $3,240/year, but Pro caps out at individual accounts with no centralized admin — most 250-employee companies land on Team or Business once IT needs visibility into who's running what. That puts the realistic range for a 30-developer team at $5,400–$8,640 a year, and the cost scales linearly with every developer added:
| Developers using Docker Desktop | Pro ($9/mo) | Team ($15/mo) | Business ($24/mo) |
|---|---|---|---|
| 10 | $1,080/yr | $1,800/yr | $2,880/yr |
| 30 | $3,240/yr | $5,400/yr | $8,640/yr |
| 100 | $10,800/yr | $18,000/yr | $28,800/yr |
| 300 | $32,400/yr | $54,000/yr | $86,400/yr |
Note what doesn't shrink this bill: none of these tiers price by how often a developer opens Docker Desktop. A seat costs the same whether that engineer runs a container fifty times a day or once a month — the meter is per named user, not per usage, which is exactly the opposite of how the metered cloud-compute bills this same team is probably also fighting are structured.
Why This Keeps Catching Teams By Surprise
The threshold itself isn't new — Docker announced the licensing change on August 31, 2021, with enforcement starting January 31, 2022. Nearly five years later, in 2026, it's still the rule, unchanged in its structure even as Docker's tier pricing and feature bundling (Docker Scout, Build Cloud minutes, Testcontainers Cloud) have shifted around it. What makes it a recurring surprise rather than a one-time event is that crossing 250 employees or $10M in revenue is a business milestone, not an engineering one — it shows up in an HR headcount report or a finance close, not in anything that pings whoever owns the company's Docker Hub organization. A team can cross the line, keep working normally for a year or more with nothing visibly broken, and only discover the obligation when procurement audits software spend or Docker's own compliance team reaches out.
The Audit Risk Nobody Budgets For
The dollar figure above assumes a company notices the crossing and signs up promptly. Docker's subscription agreement gives it contractual audit rights: it or its representative may inspect records with ten days' notice to confirm compliance, and customers must retain licensing-relevant records for at least three years. If an audit finds a company crossed the threshold eighteen months ago and kept running Docker Desktop unlicensed the whole time, the exposure isn't next month's invoice — it's back-billing for every month since the crossing, on every seat, across however many developers were running it unnoticed.
That's the part a one-time $5,400 line item doesn't capture: the actual risk is a company that grows quietly — a headcount milestone HR tracks, a revenue milestone finance tracks, neither of which routes to whoever owns the Docker Desktop bill — and finds out at audit time rather than at growth time.
The Free Path: Tools That Never Ask the Question
None of this is a Docker Desktop problem specifically — it's a licensed-GUI problem, and the fix is not running one:
- Podman Desktop is the closest drop-in replacement: fully open source, cross-platform, and daemonless by design (no privileged background process holding the socket), with Docker-CLI-compatible commands. It's free at any company size because there's no commercial license to trigger in the first place.
- Rancher Desktop, maintained by SUSE, bundles containerd and k3s, ships under Apache 2.0, and is explicitly free for all commercial use regardless of company size or revenue.
- Colima is a lighter, CLI-only option for macOS and Linux developers who don't need a GUI at all — smaller footprint, no license question to ask.
For local development, any of the three closes the gap Docker Desktop leaves once a company crosses the line. But the more durable fix is upstream of the developer's laptop entirely.
The migration itself is smaller than the pricing page makes it sound: Podman Desktop consumes the same Dockerfile syntax and (with podman-docker installed) even accepts docker as a shell alias, so most existing docker build / docker compose workflows run unmodified. The real work is auditing anything that assumed a privileged root daemon was always listening on /var/run/docker.sock — Podman's daemonless, rootless-by-default model occasionally exposes places where a script or CI job depended on that assumption rather than on Docker's documented interface.
Why a Build Pipeline Shouldn't Depend on a Licensed GUI at All
Docker Desktop is a local development convenience — a GUI wrapped around a Linux VM on macOS and Windows. It was never meant to run on a CI node or a production build server, and most CI systems already build images with docker buildx, Cloud Native Buildpacks, kaniko, or rootless podman/buildah — none of which touch Docker Desktop or its license terms.
That distinction matters more for a self-hosted PaaS than for almost any other kind of team, because the build layer is the product surface: every git push a tenant makes runs through it. A Cluster API-managed fleet's CI nodes should never have a Docker Desktop dependency to audit in the first place — they build with daemonless tooling on Linux nodes that were never going to run a desktop app, licensed or not. The 250-employee threshold is a non-event for infrastructure built this way, not a line item that shows up the year the company grows.
That's the same posture worth applying to the rest of a build pipeline's toolchain: before totaling up cloud compute costs, check whether any tool in the chain — not just Docker Desktop — has a license clock quietly ticking against a headcount or revenue number nobody's watching.
The Two-Question Check
Any team can run this in under a minute, regardless of whether they think it applies to them:
- What's our current headcount — company-wide, not just engineering?
- What was trailing-twelve-month revenue?
If either number is at or approaching 250 employees or $10 million, the Docker Desktop bill is either due now or due soon — and the cheaper fix, at any company size, is switching the CI and build layer to tooling that was never going to ask the question.
Bex.co is the open-source, AI-native Render alternative — push a git repo, get a running HTTPS service on machines you own, built on a Cluster API fleet whose build pipeline was never wired to a licensed desktop client. Star the repo on GitHub or deploy your first app today.
