A developer opens a laptop on their first day and installs the container tool every tutorial recommends.
The download is free. The setup takes minutes. The whale icon appears in the menu bar and everything works.
What the install screen never mentions is the clause buried inside the license agreement that resets the price the moment their employer crosses a threshold most mid-size companies cleared years ago. So the question is not whether the tool works. It is whether the company is legally allowed to keep using it.
How a free download turns into a recurring bill the moment the company grows
Docker Desktop and Docker Engine are two different products, and that split is where the cost lives. The licensing restriction applies to Docker Desktop specifically : the graphical interface, the helper virtual machine, the Compose binary it ships, and the settings panel that most developers interact with every single day.
Meanwhile, the underlying open-source projects, including Docker Engine and the Moby project, remain under the Apache 2.0 license with no restrictions at all. Docker Engine runtime, upstream open-source Docker, and Moby projects have not been changed. A developer running Docker Engine inside a Linux environment owes nothing, no matter who signs their paycheck.
But Docker Desktop, the version that runs natively on Windows, Mac, and Linux with a point-and-click interface, carries a commercial use clause that most people never read. Any company with fewer than 250 employees and less than $10 million in annual revenue can use it without a paid subscription, but cross either of those lines and a paid plan becomes legally required. The tool works the same either way. The bill arrives later.
What the actual numbers look like for a team that already installed it
The pricing tiers are straightforward once you know to look for them. Docker’s paid plans billed annually run roughly $9 per user per month for Pro, $15 for Team, and $24 per seat for Business. Those figures feel modest in isolation.
Multiply them across a department and the picture changes fast. A ten-person Mac team on the Business plan runs roughly $2,880 per year. A fifty-developer team on that same tier crosses $14,400 annually for software most of them assumed was free the day they downloaded it. A hundred-seat engineering org is looking at nearly $29,000 before the first renewal conversation.
The number that matters is not the monthly rate but the fact that it applies per seat, every month, indefinitely. Nothing in the user experience signals the change. The container daemon keeps spinning, Compose files keep running, and the only real signal is a compliance review or an invoice from Docker’s sales team arriving out of nowhere.
Where the license boundary comes from and who enforces it
Docker Desktop moved to a paid per-user subscription model in 2022 for companies with 250 or more employees or $10 million or more in annual revenue. Docker’s pricing FAQ spells out the exact threshold: use without a paid subscription is restricted to non-commercial open-source projects or commercial undertakings with fewer than 250 employees and less than $10 million in annual revenue.
Both conditions operate independently, and that detail catches companies off guard. A business with 300 employees and $8 million in revenue still falls inside the paid zone because the employee count alone is enough to trigger the requirement. Crossing either threshold is sufficient. You do not need to cross both.
Enforcement is largely self-directed, meaning Docker relies on companies to audit their own installations. That ecosystem lock is part of why so many teams keep using the tool without addressing the license question. The broader developer-tool industry has moved firmly in this direction: open core is now a dominant monetization model, the core functionality is released open source, and companies are charged for the convenience layer on top. The free code is real. The free product is not always what it appears.
Where the catch does not apply and what teams are doing instead
Individual developers, students, and genuinely small companies owe nothing. Docker Desktop is free for small businesses with fewer than 250 employees and less than $10 million in annual revenue, as well as for personal use, education, and non-commercial open source projects. Both size conditions must be true simultaneously to qualify for that exemption. A fast-growing startup that crossed the revenue line last quarter but still has 40 employees is no longer in the clear, and many founders do not realize that until a compliance review flags it.
Some teams have responded by routing around the GUI entirely. Docker’s open-source software such as Docker Engine is accessible for all and supported by the Moby project maintainers and community members. On Windows machines, that means running the engine inside a WSL2 environment rather than through the Desktop application. The workaround requires more setup than clicking a download button, which is exactly why many developers never make the switch.
Free tiers and open-source labels increasingly describe a starting point, not a destination. For teams building on tools like these, a security review of the supply chain, including how OAuth tokens can expose an entire organization, is at least as urgent as sorting out the licensing invoice.
What changes when a team actually audits its tool stack
The honest consequence of ignoring the license is a retroactive compliance conversation that companies rarely win cheaply. For organizations that meet the threshold, compliance and cost control depend on accurate inventory, subscription management, and annual reconciliation against Docker’s audit requirements. Docker’s terms do not include a grace period for organizations that grew into the paid zone without noticing, and back-billing for unlicensed seats is a real outcome of those conversations.
For most engineering teams, the practical path is clear: audit installed copies of Docker Desktop against the employee and revenue thresholds, then either purchase the appropriate tier or migrate workflows to Docker Engine running natively inside Linux. Teams on entirely open-source components can keep their licensing cost at zero. The migration is not painless, but it is documented and well-worn.
The wider lesson sits beneath every free-to-download tool. Developers shopping for the next layer of their stack, whether that is a chip ecosystem worth nearly $88 billion by decade’s end or a container runtime they assumed was free, would do well to read the terms before the invoice arrives. The open-source label describes the engine. It has never described the whole product.
