How to Choose an IoT eSIM Orchestration Platform: A 2026 Buyer's Guide
eSIM orchestration explained for enterprise IoT: how SGP.32 works, why orchestration beats a single-carrier SIM, and 8 questions to ask any provider.
Choosing an IoT SIM used to be about coverage maps and price per MB. In 2026, it's an eSIM orchestration decision: who controls which network your devices use, and how easily you can change it.
The GSMA's SGP.32 standard made eSIM profiles practical to manage at fleet scale. Plenty of providers now sell an "eSIM." Far fewer give you orchestration you can use today: the ability to add carriers, set network policies and manage profiles across your whole fleet from one place.
This guide explains what eSIM orchestration is, why it matters for enterprise IoT, and the questions to ask before you sign a connectivity contract.
What eSIM orchestration actually is
An eSIM is hardware that can hold more than one carrier profile. Orchestration is the software layer that decides which profiles go on which devices, and which network a device uses, under rules you set.
Three GSMA standards shape how this works:
Standard | Built for | How profiles are managed |
|---|---|---|
SGP.02 (M2M) | Earlier IoT deployments | Relies on SMS and tight operator integration |
SGP.22 (consumer) | Phones, wearables, infotainment | A user approves changes through a screen |
SGP.32 (IoT) | Headless, constrained device fleets | The fleet owner pushes changes remotely through an eIM |
Under SGP.32, an eIM (eSIM IoT Manager) manages the profile lifecycle across your fleet. An IPA (IoT Profile Assistant) on the device or eUICC carries out the changes. Removing the SMS dependency widens support for NB-IoT and LTE-M devices, including those in power-saving modes (Kigen).
An SGP.32 eSIM on its own is not orchestration. You also need a platform that onboards carriers, applies network policies and gives you one view of every device, profile and network.
Want to tell a truly programmable eSIM from relabeled static profiles? Download our free eSIM Buyer's Guide for Enterprise.
Why orchestration matters for enterprise fleets
Orchestration turns connectivity from a fixed contract into something you can tune over the life of a device. For fleets expected to run 5 to 10 years in the field, that flexibility compounds.
No lock-in. Add or change carriers over the air, without new SKUs, separate supply chains or truck rolls to swap SIMs.
Keep the deals you already have. Bring your existing carrier contracts, pricing and SLAs, and add networks only where you need them.
Fill coverage gaps. Add a second network where one operator is weak, or bring in technologies like LTE-M, NB-IoT or satellite in specific markets.
Configurable network switching and failover. Set policies for when and how devices move between networks, so your team decides how the fleet behaves when conditions change.
Negotiating leverage. When switching carriers is a configuration change, you have real options at renewal.
One view of everything. Manage every network, profile and device from a single dashboard and API, instead of one portal per carrier.
Buyer's checklist: 8 questions to ask any provider
Use these questions to separate a real orchestration platform from an eSIM with a roadmap slide.
Is your orchestration generally available today? Ask for a live demo on production devices, not a beta or early-access sign-up.
Do you support SGP.32 now? Confirm both the eSIM hardware and the eIM are in production.
Can I bring my own carrier? Check whether you can onboard existing carrier contracts yourself, or only buy the provider's own plans.
How many networks are natively integrated? Native integrations usually mean better performance than roaming-only access.
Can I configure network switching and failover policies? You should control the rules, not depend on a black box.
Is the eIM open, or locked to one provider? SGP.32 supports changing eIMs. Make sure your contract and platform do too.
Is there one API and one dashboard for every carrier? Count how many portals your ops team would actually log into.
Which form factors are supported? Look for removable (2FF/3FF/4FF) and embedded (MFF2) options so one strategy covers your whole hardware line.
Available today vs. "coming soon"
Many IoT connectivity providers now talk about orchestration, but some still list it as alpha, beta or early access. If you're deploying devices this year, ask what you can use on day one.
What to check | Orchestration platform in production | eSIM with orchestration on the roadmap |
|---|---|---|
Carrier onboarding | Self-serve, including your own carrier contracts | Provider's own plans; others "planned" |
Network policies | Configurable switching and failover rules today | Fixed behavior, or rules in early access |
eIM | SGP.32 eIM in production, open to other eSIMs | Tied to the provider's own SIMs |
API coverage | Full API for profiles, networks and devices | Partial API, "full support coming" |
Risk to your roadmap | Low: what you test is what you deploy | Higher: features may change before GA |
How TEAL delivers eSIM orchestration today
TEAL has been building carrier-neutral eSIM orchestration since 2018, and it's in production now. We're not an MNO or an MVNO. We're the neutral orchestration layer between your devices and any network.
TEAL product | What it does |
|---|---|
Network Orchestration Service (NOS) | Orchestrates connectivity across thousands of network paths in 196+ countries through one carrier-neutral platform |
Aurora | A single dashboard and API to manage every network, eSIM profile and device, with configurable switching and failover policies |
Chameleon eSIM | SGP.32 eSIM in removable (2FF/3FF/4FF) and embedded (MFF2) form factors |
OpenEIM | A free, open SGP.32 eIM for allocating, downloading and managing eSIM profiles |
Bring Your Own Carrier (BYOC) | Upload your existing carrier plans to Aurora as Network Apps and keep the pricing and SLAs you've already negotiated |
Customers in robotics, energy, drones, transportation and public safety use TEAL to keep enterprise fleets connected on any network.
As Safe Fleet's IoT Product Manager put it:
TEAL allows our cellular solutions to be carrier agnostic. With the TEAL eSIM we can effortlessly support the carrier LTE bands our various modems are designed for.
See orchestration running on real devices
Don't settle for a roadmap. Book a live demo of Aurora and see how TEAL lets you add carriers, set network policies and manage every eSIM in your fleet from one place.
Want the full checklist to share with your team? Download eSIM: A Buyer's Guide for Enterprise
Frequently asked questions
What is eSIM orchestration?
It's software that manages which carrier profiles live on your devices' eSIMs, and which network each device uses, under policies you set. It turns an eSIM's multi-profile hardware into fleet-wide control.
Is an SGP.32 eSIM the same as orchestration?
No. SGP.32 is the standard that makes remote profile management practical for IoT. Orchestration is the platform that onboards carriers, applies network policies and gives you one view of your fleet.
Can I keep my current carrier contracts?
With TEAL's Bring Your Own Carrier, yes. You upload your existing plans to Aurora and keep the pricing and SLAs you've negotiated.
Does network switching happen automatically?
Network switching and failover are configurable capabilities in TEAL. Your team sets the policies that decide when and how devices move between networks.
How many countries does TEAL cover?
TEAL orchestrates connectivity in 196+ countries, across any network.
