top of page
Business & Enterprise
Telecommunications Technology
Cloud Infrastructure
Mirantis
Built an enterprise cloud position by making open-source infrastructure operable at scale, despite VMware, Red Hat and hyperscalers’ stronger distribution and ecosystem control.
1
MODEL
BUSINESS MODEL
Product–Service Hybrid
Enterprises and service providers pay multi-year subscriptions and services fees for software, support and managed operations across OpenStack, Kubernetes and AI infrastructure; the unit of value is a reliably operated hybrid cloud. [422][423][424]
1. Identify a complex infrastructure workflow where enterprises lack internal expertise. 2. Build the smallest system that deploys and operates one platform reliably. 3. Make automation, support and transferability foundational. 4. Add adjacent platforms only after the core delivery model is trusted. 5. Price for outcomes and operations, not licences alone. The common mis-build is selling software before the services model can guarantee reliability.
DISTRIBUTION MODEL
Mirantis, founded in 2005, first built OpenStack deployment and operations expertise, then expanded into Kubernetes, Docker Enterprise and AI infrastructure; this sequence made the build-operate-transfer delivery model the foundation for enterprise trust. [425][426][427]
HOW THEY BUILT IT
HOW TO ARCHITECT IT
Direct Sales, Enterprise Sales, Partnerships, Channel Partners
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
Mirantis reaches large enterprises and telcos through direct and enterprise sales, strategic partnerships with Intel, Ericsson and SAP, and channel partners; its customers include PayPal, Comcast, NASA and Societe Generale. [425][428][429][423]
Build enterprise sales around a high-stakes infrastructure problem, then use strategic partnerships and lighthouse customers to establish credibility. Add managed services and acquisitions only after the core delivery model is repeatable. The trap is copying enterprise sales before implementation and support can handle multi-cloud complexity.
| PATTERNS OF THIS MODEL
PATTERNS IN ENTERPRISE INFRASTRUCTURE SAAS: 1. Open-source credibility creates differentiation. Vendor-agnostic positioning appeals to enterprises avoiding lock-in. 2. Build-operate-transfer reduces adoption risk. Enterprises buy outcomes, not software. 3. Strategic partnerships amplify reach. Intel, Ericsson and SAP lend credibility and distribution. THE WEAKNESS: Services-heavy models can limit scalability and margin; software must eventually carry the economics.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — AI INFRASTRUCTURE OPERATIONS. The underbuilt opportunity is managing GPU clusters, Kubernetes and AI workloads as a unified platform. GOLDMINE 2 — HYBRID CLOUD CONTROL PLANE. Enterprises need consistent operations across on-prem, edge and public cloud; this remains fragmented. GOLDMINE 3 — OPEN-SOURCE COMMERCIALIZATION. Packaging open-source complexity into enterprise-grade support is a durable wedge. THE PIT — OPEN-SOURCE COMMODITIZATION. Free alternatives reduce pricing power if the platform does not add operational value. THE SECOND PIT — SERVICES MARGIN TRAP. Heavy consulting can limit scalability. MOVE WITH CAUTION — Do not chase AI infrastructure before Kubernetes and cloud operations are dependable; enterprises will not accept experimental platforms in production.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
Mirantis entered enterprise IT, where legacy infrastructure and vendor lock-in created resistance to cloud adoption; it sold operational outcomes rather than digitization itself. [425][430][427]
MARKET TYPE
Mature Market
ENTRY STRATEGY
Brownfield Entry
WHY THEY WON
Enterprise cloud infrastructure is mature, with entrenched incumbents. Mirantis’s opening was to serve enterprises that wanted open, hybrid alternatives without losing operational reliability. [425][422][427]
EXECUTION
Mirantis replaced VMware-centric or proprietary infrastructure with open-source-based hybrid cloud platforms. [425][426][427]
FOOTHOLD STRATEGY
Lighthouse Customer Strategy
Mirantis used recognizable customers such as NASA, PayPal, Comcast and Ericsson as lighthouse references, reducing perceived risk for other enterprises. [425][431][432]
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: The commercial implication is that recognizable references convert an infrastructure tool into a strategic platform decision. KEY LEARNING: The strongest campaign premise is not “adopt open source” but “reduce lock-in without losing reliability.” HOW TO USE: Test a lighthouse-reference strategy only when early customers will permit named use and their deployments demonstrate repeatable outcomes.
KEY LEARNING
In a mature market, the winning position is usually a workflow the incumbent treats as secondary. Mirantis’s structural opening was that proprietary vendors focused on lock-in, while enterprises wanted flexibility and control. By making open-source operability central, it changed the purchase from software to strategic infrastructure. The transferable lesson is to enter where the incumbent’s core strength—ecosystem or integration—does not solve the customer’s flexibility problem.
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN STRATEGIC-PARTNERSHIP DISTRIBUTION: 1. Vendor alliances create trusted access. Intel, Ericsson and SAP partnerships lend credibility and distribution. 2. Open-source community creates technical advocacy. Developers and architects influence enterprise decisions. 3. Lighthouse references support expansion. Named customers create a natural path from pilot to broader deployment. 4. THE WEAKNESS: Partnership-led sales can become dependent on partner priorities and margin-sharing.
| MARKET ENTRY PLAYBOOK
Use Brownfield Entry when the buyer already operates legacy infrastructure and needs modernization. Prove that your product can migrate and operate the highest-friction workflow first, then expand into adjacent platforms. Build support, automation and transfer capability before scaling. Reject this approach if the buyer’s incumbent system is adequate and there is no lock-in or cost trigger.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
Choose a Lighthouse Customer Strategy when credibility and implementation proof matter more than initial volume. Target a recognizable customer whose successful deployment creates reference value for similar enterprises. Validate the foothold through named references, repeatable implementation and expansion into adjacent teams. Expand only after the first deployment pattern is reliable; otherwise enterprise sales become custom-services projects. A failure pattern is chasing logos without repeatable onboarding, which inflates cost and slows growth.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
Mirantis uses multi-year subscription and services contracts, with enterprise deployments often exceeding $50M–$100M over their lifetime; pricing is quote-based. [423][433][424]
REVENUE MODEL
Subscription, Service Fee, Licensing Fees
PRICING MODEL
Custom Enterprise Pricing, Value-Based Pricing, Subscription Discount Pricing
WHY THEY WON
Customers pay recurring subscriptions for software and support, with professional services and managed operations adding services revenue. [423][424][427]
Mirantis does not publish pricing; contracts are quote-based, multi-year, and scale with infrastructure scope, users and support needs. [423][433][424]
TARGET AUDIENCE
Large enterprises (quote; want hybrid cloud and open-source flexibility); telecom and service providers (quote; want NFV and edge infrastructure); AI-driven companies (quote; want GPU and Kubernetes operations); government and regulated industries (quote; want compliance and sovereignty).
CUSTOMER BUYING BEHAVIOUR
A CIO or infrastructure leader identifies vendor lock-in or cloud complexity, evaluates Mirantis against VMware, Red Hat or hyperscalers, requests a demo and reference calls, then adopts through a build-operate-transfer engagement. [425][422][427]
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Buyers are not buying software; they are buying operational control, reduced lock-in and infrastructure reliability. The comparison budget includes VMware licences, managed-service providers and the cost of infrastructure downtime. The meter should reflect clusters, nodes and support scope because these track operational complexity. The vendor’s hidden cost is services delivery and open-source maintenance. RULE 1 — SELL OPERATIONAL OUTCOMES. Frame the purchase around reliability and flexibility. RULE 2 — PRICE INFRASTRUCTURE SCALE. Clusters and nodes map to real value. RULE 3 — MAKE TRANSFER A TRUST BUILDER. Build-operate-transfer reduces adoption risk. RULE 4 — CONTROL SERVICES MARGIN. Heavy consulting can limit scalability. The buyer is ultimately buying infrastructure control, evidenced by the IT operations or cloud budget.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
The largest threat is commoditization from Red Hat, VMware and hyperscalers. Open-source alternatives reduce pricing power if the platform does not add operational value. Services-heavy delivery can limit scalability and margin. Platform dependency arises from Kubernetes and OpenStack communities. Concentration risk arises if growth depends heavily on a few large enterprise contracts. Mirantis raised over $200M total, including $100M Series B in 2014; current ARR is not publicly verified. [425][428][423][434]
Where the model can break
4
MOTION
motion ge cs
Mirantis’s multi-cloud, reliability-sensitive, services-heavy product and expansion into enterprise and telco accounts require a structured enterprise-sales motion; its quote-based pricing and lighthouse customers support this. [425][422][423]
GROWTH EXPANSION MODEL
Acquisition-Led Growth, Product Line Expansion
HOW THEY EXPAND
Mirantis expanded from OpenStack services into Kubernetes, Docker Enterprise and AI infrastructure through organic development and the 2019 Docker Enterprise acquisition. [422][426][435][423]
COMPETITIVE STRATEGY
Differentiation
HOW THEY COMPETE
Mirantis differentiates through open-source flexibility and build-operate-transfer delivery, rather than competing solely on proprietary ecosystems or hyperscale cloud. [425][422][427]
GROWTH ENGINE
GTM
Content Flywheel
An infrastructure leader’s lock-in or complexity problem creates a sales opportunity; onboarding deploys and operates the platform; successful use expands into Kubernetes, AI and managed services. The loop depends on fast activation, reliable operations and measurable flexibility improvement. It breaks if onboarding is slow, support fails or the platform becomes too complex for enterprise teams. A founder can reproduce this by making the first workflow produce a visible outcome quickly and aligning expansion with customer maturity.
Mirantis uses an enterprise, sales-led GTM: direct and enterprise sales target CIOs and infrastructure leaders; strategic partnerships and lighthouse references create credibility; implementation activates the platform; product expansion deepens accounts. The primary motion is enterprise sales, supported by ecosystem partnerships and category education. The transferable components are a clearly owned infrastructure problem, implementation repeatability and expansion paths tied to cloud maturity; this system is unlikely to work for low-ACV self-serve buyers or where services capacity cannot scale.
SUSTAINING MOATS
High Customer Lock-In
moat
The moat is high customer lock-in created by deployed infrastructure, operational knowledge and multi-year support contracts. It strengthens as enterprises expand into Kubernetes and AI; it weakens if open-source alternatives improve or if a competitor delivers a materially simpler migration path.
| MOAT INTELLIGENCE
THE STANDARD: A moat lasts when the cost of leaving exceeds the perceived benefit of switching. RULE 1 — INFRASTRUCTURE DEPTH. Deployed clusters and operational knowledge create migration friction. RULE 2 — SUPPORT DEPENDENCE. Managed services and SLAs increase reliance. RULE 3 — ECOSYSTEM EMBEDDING. Partnerships and open-source integrations raise re-integration cost. THE SIGNAL: Enterprise customers like PayPal, NASA and Societe Generale, plus multi-year contracts, indicate adoption; the moat does not protect against superior managed-cloud providers or a major open-source shift. [425][422][423][427]
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — PROVE THE OPENSTACK-SERVICES WEDGE: The early move was to build deployment and operations expertise for enterprise OpenStack. [425][430] WATCH: whether services alone create retention. $1–5M ARR — SYSTEMATIZE ENTERPRISE SALES: The move was to build direct sales and lighthouse references to convert early adopters; by 2014 Mirantis had 130+ OpenStack customers. [425][431] WATCH: services scalability. $5–10M ARR — ADD KUBERNETES AND CONTAINERS: The move was to expand into container platforms, increasing account value. [422][426][435] WATCH: platform complexity. $10–50M ARR — SCALE THROUGH SERIES B: The 2014 $100M Series B funded global expansion and enterprise sales; large contracts could reach $50M–$100M lifetime value. [425][433][434] WATCH: services margin and delivery capacity. $50–100M ARR — ACQUISITION-LED EXPANSION: The 2019 Docker Enterprise acquisition added 750 customers and container-platform depth. [426][435][436] WATCH: integration complexity and brand differentiation. $100M+ ARR — AI-INFRASTRUCTURE EXPANSION: The strategic move is to position AI infrastructure and Kubernetes as the next growth layer across hybrid cloud. [422][423] Rule: In enterprise infrastructure SaaS, expand from services into software and AI only after delivery repeatability is proven.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Own the enterprise’s infrastructure-operations workflow, then expand into software and AI only after the delivery model becomes the system of record. SEQUENCE: 1. Build a dependable deployment-and-operations workflow that solves a high-stakes infrastructure problem. 2. Win a recognizable lighthouse customer and make implementation repeatable before scaling enterprise sales. 3. Add Kubernetes, AI or managed-service modules only when the core workflow creates trust and expansion economics. WORKED: Mirantis’s progression from OpenStack services into Kubernetes and AI follows the logic of expanding where operational control creates permission. CAUTION: Do not copy the enterprise-sales motion before services delivery is repeatable; do not sell AI infrastructure without reliable Kubernetes operations. Public ARR is undisclosed, so replication should prioritize contract quality, implementation repeatability and retention over customer logos. [425][422][426][423]
bottom of page