Licensing and Governance
By the end of this lesson you will know exactly which Docker components are free, which have paid tiers, and who is responsible for each part of the ecosystem.
Who Owns Docker?
"Docker" refers to both a company and a collection of technologies. This distinction matters because different parts of the ecosystem have different owners, licenses, and support models.
| Entity | Type | What It Controls |
|---|---|---|
| Docker, Inc. | For-profit company | Docker Desktop, Docker Hub, Docker Scout |
| Moby Project | Open-source project | The upstream source code that Docker Engine is built from |
| CNCF | Non-profit foundation | containerd (the low-level container runtime), plus Kubernetes and Helm |
| OCI | Standards body | The Image Spec and Runtime Spec that all container tools follow |
Think of it like Fedora vs Red Hat Enterprise Linux: Moby is the community-driven upstream project, and Docker Desktop/Engine is the assembled, tested, branded product you actually install.
Docker, Inc. builds the tools (Desktop, CLI, Hub). The standards (image format, runtime behavior) are governed by the open industry through OCI. This means you are never locked into Docker as your only option.
What Is Free and What Is Paid?
This is the most common question teams ask, and the answer depends on which component you are using.
Open Source (Always Free)
These components are open source under permissive licenses. You can use them in any context — personal, commercial, enterprise — with no restrictions:
| Component | What It Does | License |
|---|---|---|
| Docker Engine | The daemon that runs containers on Linux | Apache 2.0 |
| Docker CLI | The command-line tool you use to interact with Docker | Apache 2.0 |
| Docker Compose | Multi-container application definitions via YAML | Apache 2.0 |
| containerd | Low-level container runtime (CNCF project) | Apache 2.0 |
| runc | OCI-compliant process-level container runtime | Apache 2.0 |
If you run Docker on a Linux server using apt install docker-ce or the official install script, everything is free regardless of your company size.
Docker Desktop (Conditional)
Docker Desktop is a GUI application for macOS and Windows that bundles the Engine, CLI, and a Linux VM into a convenient package.
| Usage Context | Cost |
|---|---|
| Personal learning and hobby projects | Free |
| Education and academic use | Free |
| Open source projects | Free |
| Small businesses (fewer than 250 employees and less than $10M revenue) | Free |
| Larger organizations | Requires a paid subscription |
[!IMPORTANT] If your company has 250+ employees or $10M+ annual revenue, using Docker Desktop without a subscription is a licensing violation. On Linux servers, this is irrelevant — you use Docker Engine directly, which is always free.
Docker Hub (Freemium)
Docker Hub is the default cloud registry for storing and sharing container images.
| Plan | Pull Rate Limit | Private Repos | Key Constraint |
|---|---|---|---|
| Anonymous | 100 pulls / 6 hours | 0 | Very limited for CI |
| Free account | 200 pulls / 6 hours | 1 | Sufficient for small personal use |
| Pro | Unlimited | Multiple | Individual professional use |
| Team / Business | Unlimited | Unlimited | Organization-level features |
For CI pipelines that pull images frequently, the free tier's rate limit can cause build failures. Authenticated pulls or a private registry (like GitHub Container Registry or self-hosted Harbor) avoid this issue.
The Practical Decision Tree
When someone asks "Is Docker free?", walk through these questions:
- Are you using Docker Engine on Linux? — Free. Always. No subscription needed.
- Are you using Docker Desktop on Mac/Windows? — Check your company size against the Desktop licensing terms.
- Are you pulling images from Docker Hub in CI? — Check your pull rate against the free tier limits. Consider authenticated pulls or a mirror.
Governance: Who Manages What on Your Team?
Licensing clarity is only useful if someone on your team actually tracks it. Here is a minimal ownership model:
| Responsibility | Recommended Owner |
|---|---|
| Engine version policy (when to upgrade) | Platform / SRE team |
| Desktop compliance (license eligibility) | IT / Engineering manager |
| Registry strategy (Hub limits, private registries) | Platform + Security |
| Compose plugin version | Platform team |
| Monitoring licensing term changes | Named policy owner |
If no one on your team owns these responsibilities, you will eventually face a surprise — a rate-limited CI build, an unexpected invoice, or a compliance audit question you cannot answer.
Common Mistakes
Assuming "free for me" means "free for the company"
Docker Desktop is free for personal use. That does not mean it is free when employees use it at a large organization. Always verify against the current terms.
No registry strategy for CI
If your CI pipeline pulls base images from Docker Hub without authentication, you will hit rate limits during busy build periods. Use authenticated pulls, image caching, or a private registry.
Ignoring version drift
When Engine versions differ between development, CI, and production, you get subtle behavior differences that are hard to debug. Pin versions and test upgrades in staging first.
Treating licensing as someone else's problem
Licensing affects architecture, cost, and reliability. Engineers benefit from understanding it, not just legal and procurement teams.
Key Takeaways
- Docker Engine, CLI, and Compose are open source and free for all use cases.
- Docker Desktop requires a paid subscription for organizations above a certain size.
- Docker Hub has pull rate limits on free tiers that can disrupt CI pipelines.
- Docker is governed by multiple entities (Docker Inc., Moby, CNCF, OCI) — not a single company.
- Assign clear ownership for version policy, Desktop compliance, and registry strategy on your team.
What's Next
- Continue to Docker Popularity and Industry Adoption to understand where Docker fits in the modern technology landscape.