Inside the eSIM Stack: Who Builds It vs Who Resells It
There’s a question every serious eSIM buyer — and every investor looking at this space — should be asking right now: when you buy a data plan from one of the dozens of eSIM providers out there, whose infrastructure are you actually riding?
The honest answer is: usually not theirs.
The eSIM industry has a visibility problem. On the surface, it looks like a competitive market with dozens of providers offering plans across 150, 180, 200+ countries. Dig one layer down, and you find a surprisingly concentrated infrastructure ecosystem, with a handful of players doing the actual heavy lifting while most of the “providers” operate as branded storefronts layered on top.
Understanding the stack matters — not just for technically-minded buyers, but for anyone trying to assess whether a provider’s value proposition will hold up long-term.
The Three Layers Most People Never See
At its most basic, the eSIM stack has three distinct layers: infrastructure, aggregation, and distribution.
Infrastructure
Aggregation
Distribution
Infrastructure is where the actual connectivity lives — the SM-DP+ servers that handle profile delivery, the carrier agreements, the network access arrangements that determine whether your device actually connects when you land in Nairobi or São Paulo. This is the expensive, technically demanding, relationship-heavy layer. Companies like BICS, Giesecke+Devrient, Kigen (ARM), and Thales operate core RSP infrastructure. On the carrier access side, you’re talking about MVNOs and infrastructure operators — some of whom have built their own eUICC platforms — companies like Transatel (NTT), Cubic Telecom, and 1GLOBAL, the latter now quietly embedded inside fintechs like Revolut and N26.
Aggregation sits in the middle. Aggregators hold contracts with multiple carriers and package that access into a usable API. This is where companies like Airhub, eSIM Go, etc operate. They don’t own the networks, but they’ve done the hard work of negotiating terms, building technical integrations, and creating a normalized data layer that downstream partners can build on top of. The quality of an aggregator’s carrier relationships and the depth of their coverage map is what separates a reliable product from one that fails at the edges.
Distribution is where the consumer-facing brand lives — pricing, UX, support, marketing. Most of what you see in the eSIM app stores, comparison sites, and travel content is distribution. Airalo, Holafly, Nomad, Yesim, Ubigi, and Fairplay — all operate at this layer to varying degrees, though several have made significant investments in moving further down the stack.
Who’s Actually Building
The distinction between “we have our own infrastructure” and “we’ve built a great product on top of someone else’s infrastructure” is meaningful — but often deliberately obscured.
Ubigi is a clear example of a provider with genuine infrastructure depth. Operated by Transatel, which NTT acquired in 2019, Ubigi has direct carrier-grade relationships and builds product features — like SmartIP, which preserves your home-country IP while roaming — that only make sense if you have real control over the routing layer. That’s not something you bolt on top of an aggregator API.
Airalo pioneered the aggregator model as a consumer product and has arguably done more than any single company to normalize the eSIM purchasing experience. But Airalo’s infrastructure advantage is commercial — supplier breadth and scale — rather than technical. They source from multiple aggregators and carriers and redistribute through a marketplace model. It works, and works at scale, but the ceiling on technical differentiation is real.
Yesim has been building in a slightly different direction — their OneBalance model and Partner API suggest ambitions toward B2B2C distribution, trying to become more of a platform than a retailer. Whether that strategy gains traction depends less on tech than on sales cycle and enterprise relationships.
Fairplay is the most structurally unusual player in the current market. A subscription-based model with tiered pricing and a deliberate “Stop” feature — not a pause, an active user decision to halt usage — it’s designed around a different user psychology than the flat-rate plans that dominate the space. The pricing architecture is genuinely distinct: a monthly base with a defined data ceiling and a hard cost cap above it, which demands precise disclosure rather than the kind of vague “unlimited-ish” positioning that’s rampant in the category.
The API Economy Underneath
One of the more underappreciated shifts in the last two years is how many eSIM providers have moved to expose their own APIs — not just consume them.
This matters because it signals a strategic repositioning. A provider that only consumes aggregator APIs is, functionally, a retailer. A provider that exposes APIs to downstream partners is becoming infrastructure. The business model, margin structure, and defensibility of those two positions are completely different.
Airhub has been explicit about this shift, marketing itself as an API-first eSIM platform for developers and OTAs. eSIM Go has followed a similar path. The downstream customers for these APIs are travel apps, fintechs, airlines, and hotel chains — the distribution layer that the industry’s most bullish analysts have been pointing to for years as the real growth vector.
The satellite connectivity layer is worth watching here, too. Starlink’s roaming product and AST SpaceMobile’s direct-to-device ambitions create a new infrastructure category that doesn’t fit neatly into the existing MNO-MVNO-aggregator chain. Whether traditional eSIM providers integrate with satellite as a fallback layer — or get disintermediated by it — is genuinely open.
Who’s Differentiating and How
Real differentiation in the eSIM market is rare. Most of it happens at the distribution layer: pricing logic, UX, plan structure, customer support quality, and how well a provider handles edge cases (profile delivery failures, network fallback, customer comms when coverage fails).
The providers gaining ground are the ones treating the product layer seriously. Ubigi’s SmartIP is a genuine feature — it solves a real problem for remote workers and security-conscious travelers, and it couldn’t exist without infrastructure control. Fairplay’s subscription architecture is a genuine pricing innovation, though its success depends on user education and honest positioning, not just clever structuring. Yesim’s enterprise pivot is plausible but unproven at scale.
What to Watch
The next 18 months in the eSIM stack will likely be defined by three dynamics: consolidation at the aggregator layer (the middle of the stack is inefficient and overcrowded), API-led B2B2C distribution accelerating faster than direct-to-consumer growth, and an increasing pressure on pure resellers to either differentiate on product or compete purely on price — a race they’ll eventually lose to whoever controls the infrastructure below them.
GSMA’s SGP.32 standard for IoT eSIM is already adding pressure on the device side. The IHE (IoT Hub Entity) model it introduces changes to profile management in ways that will eventually ripple up to the consumer eSIM layer. Providers ignoring this are missing a structural shift that’s already in motion.
The most reliable third-party visibility into how this stack is evolving comes from GSMA Intelligence, Berg Insight’s eSIM market reports, and Kaleido Intelligence’s annual eSIM forecast. All three have been consistently more accurate about adoption curves than the eSIM providers’ own marketing would suggest, which is a useful calibration in an industry where hype consistently runs ahead of reality.
The providers who will matter in five years are the ones who understand which layer they actually occupy — and are building accordingly.
FAQ Block (Schema-Ready)
| Q1: What is the eSIM infrastructure stack
The eSIM stack has three main layers: infrastructure (SM-DP+ servers, carrier agreements, eUICC platforms), aggregation (API-based middlemen who package carrier access), and distribution (the consumer-facing brands you buy plans from). Most eSIM retail brands operate at the distribution layer and depend on aggregators for their actual connectivity. |
| Q2: What is an SM-DP+ server and who operates them?
An SM-DP+ (Subscription Manager Data Preparation+) server is responsible for creating and delivering eSIM profiles to devices. It’s a core component of the GSMA RSP (Remote SIM Provisioning) architecture. Operators like Giesecke+Devrient, Thales, and Kigen manage these servers for network operators and eSIM providers globally. |
| Q3: What is the difference between an eSIM provider and an eSIM reseller?
An eSIM provider owns or controls part of the connectivity stack — typically carrier agreements, aggregator relationships, or RSP infrastructure. A reseller sources plans from an aggregator or provider and redistributes them under their own brand with no underlying infrastructure. The distinction matters for long-term pricing stability and feature development capability. |
| Q4: What is an eSIM aggregator?
An eSIM aggregator holds contracts with multiple mobile carriers and packages that are accessed through a normalized API. Downstream partners — apps, travel platforms, eSIM brands — use this API to offer multi-country data plans without negotiating carrier deals directly. Companies like Airhub and eSIM Go operate in this layer. |
| Q5: Which eSIM providers have their own infrastructure?
Ubigi (operated by Transatel/NTT) has genuine carrier-grade infrastructure and builds features like SmartIP that require routing-level control. 1GLOBAL operates as a licensed telco. Most consumer-facing eSIM brands — including large ones — source connectivity from aggregators rather than owning infrastructure themselves. |
| Q6: What is GSMA SGP.32 and why does it matter?
SGP.32 is the GSMA standard for IoT eSIM management. It introduces the IHE (IoT Hub Entity) model, changing how profiles are managed on constrained devices. While primarily relevant to IoT, it signals a broader architectural evolution in the eSIM ecosystem that will eventually affect how consumer eSIM platforms are built and certified. |
