Source numbers link to evidence. [Inference] marks analytical judgment, including motion classifications and causal explanations. Public evidence does not establish every internal decision or metric.
Conceptual illustration for Docker: a package, a terminal, and layered sheets evoke application packaging as an organized developer workbench, without representing verified technical architecture.
- Company
- Docker · Developer tools and communities · docker.com
- Conversion motions
- [Inference] This research classifies Docker as Product Led, Human Led and Partner Led.
- Docker target customer
- Individual developers, software teams and organizations governing development workflows. [3]
- Product complexity
- [Inference] A familiar container interface fronts a complex build and software-supply-chain system.
- Decision-making unit
- [Inference] Individual tool adoption can be quick; company-wide subscription, security and governance need managers.
- Market at entry
- Docker emerged from dotCloud’s container work and became an open-source project in 2013. [1][2]
- Market today
- Current products combine developer subscriptions, images, security and AI-related workflows. [3]
- Evidence
- Source-backed brief · 3 linked sources · research date · method and limitations
The ten-step Revenue Engine reading map
These links locate relevant evidence. A linked section does not imply every detail of the step is publicly established.
- Acquire Your First Customers: Founder Led Sales Read first customers
- Embrace GTM Experimentation Not established in this entry
- Understand Your GTM Motion Options Read GTM motion
- Pick Your GTM Motion Not established in this entry
- Generate a Lead Read GTM motion
- Turn Leads into Paying Customers Read GTM motion · Read people & process
- Retain and Grow Your Customers Read retain & expand
- Build Your GTM Team Read people & process
- Plan Your Tech Stack Read people & process
- Optimize and Scale Through Metrics Read pricing & economics
Docker origin and first customers: The reusable technology outgrew its original wrapper
Solomon Hykes’s farewell traces the company to dotCloud, founded with Kamel Founadi and Sebastien Pahl. He identifies Eric Bardin, Sam Alba, Jerome Petazzoni and Julien Barbier as the core group around the 2013 reinvention as Docker. The account establishes a technical-team pivot; it does not identify the first paying Docker customer. [1]
[Inference] The reusable container workflow could reach developers beyond one hosted platform. Open distribution exposed the technology to a wider ecosystem, but adoption of a standard and purchase of a vendor’s commercial product remained different events. The case should not be simplified into downloads automatically becoming enterprise revenue. [1][2]
[1] [2]Docker GTM motion: The company changed which customer job it monetized
In November 2019, Docker sold its enterprise business to Mirantis and focused the remaining company on developer workflows. Scott Johnston’s announcement explicitly framed the next chapter around developers. This separates the production-operations business from the later developer-tool business; they should not be treated as one unchanging sales motion. [2]
[Inference] The strategic fit improved when the paid offer addressed the same broad population that already knew the product. Enterprise governance could still be sold, but around a developer workflow already in use. That is a different route from convincing operations leaders to buy a complete production platform because developers liked containers. [2][3]
[2] [3]Docker people and process: Different phases needed different leadership work
Hykes describes moving from CEO to CTO as the company hired experienced leadership, and his 2018 account names Steve Singh as CEO at that time. Johnston authored the 2019 refocus. These dated roles are historical, not claims about present officeholders. The sources do not document the first sales rep’s playbook or the original account-management assignments. [1][2]
[Inference] The founding team’s strength was creating and communicating a useful technical abstraction. The restructuring required a separate skill: selecting a narrower commercial focus despite an expansive ecosystem. Keeping a platform widely adopted while defining a paid boundary requires consistent communication with both users and purchasing organizations. [1][2]
[1] [2]Docker retention and expansion: From one developer to a governed organization
The live site exposes onboarding, training, documentation, community resources and support. Its subscriptions distinguish Personal, Pro, Team and Business; Business emphasizes organizational security and control. November 2026 annual-billing equivalents show Pro at $9, Team at $15 and Business at $24 per user monthly, with differing monthly-billing rates for some plans. [3]
[Inference] Team expansion relies on shared tooling and controls, not simply forcing every container user into the same contract. Onboarding must explain entitlement, identity and administration alongside product features. Complementary images and integrations can extend value, but their existence is not evidence that every partner drives paid acquisition. [3]
[3]Docker pricing and economics: Distribution is an asset with a cost
[Inference] Free developer access can create preference and familiarity while consuming infrastructure and support resources. Paid team governance and professional capabilities supply monetization opportunities; the public rate card does not reveal conversion, CAC or customer-level profitability. The first commercial subscription and a complete historical pricing series remain gaps. [3]
[Inference] The central critique is that a huge ecosystem can obscure an unresolved buyer problem. The 2019 separation provides concrete evidence that scope was reconsidered. A better operating discipline would measure value and conversion for each buyer group separately before treating the popularity of the underlying technology as validation of every adjacent product. [1][2]
[1] [2] [3]Docker economics at a glance: Pricing is only half the story.
Free Personal and per-user Pro, Team and Business plans, plus product-specific commercial offers. [3]
See the dated pricing analysis.
[Inference] The relevant costs and conversion frictions are discussed in the analysis; no invented margin model is supplied.
Not verified in this brief.
No cohort retention figure verified in this brief.
The people in the Docker GTM story: People & capabilities.
Solomon Hykes
FounderTechnical founder of dotCloud; later Docker CTO.
Helped create and popularize the developer container workflow. [1]
[1]Scott Johnston
Executive leading the 2019 refocusDetailed earlier career not inspected here.
Articulated the shift toward developer workflows after the enterprise-business sale. [2]
[2]Docker GTM: critical reading and analysis: Why it worked.
Where it breaks.
What worked—and why
[Inference] Existing developer familiarity supported a focused paid workflow.
What did not work
The enterprise business was sold and the company refocused in 2019. [2]
What could have been better
[Inference] Separate ecosystem adoption from conversion by economic buyer.
What another founder can use
[Inference] Mass developer adoption did not settle the business model; a later refocus aligned the offer with the user.
Docker go-to-market FAQ: The questions that matter.
How did Docker find its GTM motion?
Mass developer adoption did not settle the business model; a later refocus aligned the offer with the user. See the sourced account and explicitly labeled analysis above.
Docker sources and open questions: Follow the sources.
- Au Revoir Docker · primary
Inspected for the facts attributed in this brief; current pages observed November 10, 2026.
- Docker’s Next Chapter Docker · primary · 2019-11-13
Inspected for the facts attributed in this brief; current pages observed November 10, 2026.
- Pricing Docker · primary
Inspected for the facts attributed in this brief; current pages observed November 10, 2026.
What remains unverified
First paid account and its original contract were not verified.
Named early sales and customer-success hires, training, compensation and individual account assignments remain incompletely documented.
No verified CAC, payback, funnel conversion or numerical retention series in this brief.
Historical website/pricing screenshots were not captured for this company; dated textual evidence is distinguished from current pages.
No verified visual capture is attached to this entry. A current screenshot is not a substitute for a historical capture.