IoT Connectivity Marketplace Background

IoT Connectivity Marketplace

Find the perfect connectivity solution for your IoT devices

IoT Connectivity Marketplace

Compare IoT Connectivity Providers

Find the perfect IoT connectivity solution. Compare providers by coverage, protocols, and features. Get instant RFQ matches for your IoT devices. Browse global coverage maps and learn about NB-IoT, LTE-M, LoRaWAN, and 5G connectivity options.

Public Beta: Live platform with active updates.

THE INDUSTRY TRACKER

IoT Remote SIM Provisioning · SGP.32

The SGP.32 Ecosystem Tracker. Independently maintained, continuously updated.

9
Production-ready providers
5
Certified eUICC modules
6
Certified eIM components
v1.2
Latest spec
Released 697 days ago
Updated
What the industry is talking about
Last refreshed

SGP.32 Available Solutions

Public record of vendor and provider announcements against the GSMA SGP.32 certification schemes. Each entry links to its primary source.

List last updated

SGP.32 eSIM (eUICC + IPAe)
VendorProduct nameGSMA CertificationSource
Kigen
IoT eSIM
GSMA Certified?
PR
Thales
Thales Adaptive Connect (TAC)
GSMA Certified?
PR
STMicroelectronics
ST4SIM-300
GSMA Certified?
PR
G+D
IoT eSIM
GSMA Certified?
PR
IDEMIA
DAKOTA eSIM IoT1
GSMA Certified?
PR

5 vendor rows tracked

SGP.32 eIM (eSIM IoT Manager, Server)
VendorProduct nameGSMA CertificationSource
Thales
Thales Adaptive Connect (TAC)
GSMA Certified?
PR
IDEMIA
Smart Connect IoT
GSMA Certified?
PR
Eastcompeace
Eastcompeace eIM
GSMA Certified?
PR
Redtea Mobile
Redtea eIM
GSMA Certified?
PR
Kigen
Kigen eIM
GSMA Certified?
PR
1oT
1oT IoT eSIM platform
GSMA Certified?
PR
G+D
AirOn360® eIM
Trasna
Workz eSIM IoT remote manager
emnify
emnify eSIM IoT Manager
BICS
BICS eSIM Hub
Eseye
Infinity IoT connectivity platform
Soracom
Connectivity Hypervisor
Transatel
Global IoT eSIM platform

13 vendor rows tracked

Is your product missing or wrong?

This tracker is compiled from public sources. If your company has a GSMA SGP.32 certification that should be here, or if we've got something wrong, email sgp32@symb-iot.com with a link to the announcement. We review within 48 hours.

IoT Connectivity Providers SGP.32 maturity

Connectivity providers from the marketplace directory, graded by SGP.32 support tier. Directory-based maturity, not GSMA product certification.

TierStatusProvidersTop providers
Commercial deployment and live infrastructure91Global, 1NCE, 1oT, AT&T, BICS, show all 9
Pilots, trials, and stack validation18Cubic Telecom, Deutsche Telekom, EMnify, iBASIS, Monogoto, show all 18
Planned, no confirmed deployment timeline47A1 Digital, Aeris, Airtel, Antel, Bell, show all 47

Browse all providers →

What moved this month

Short notes from on SGP.32 items we think are worth a second look.

Tele2 IoT, IDEMIA & Cisco Launch Global SGP.32 Solution

Tele2 IoT, IDEMIA & Cisco Launch Global SGP.32 Solution Tele2 IoT, IDEMIA Secure Transactions, and Cisco have launched one of the first commercially available end-to-end IoT solutions based on the GSMA SGP.32 eSIM standard, announced at MWC 2026 in Barcelona. The solution combines IDEMIA's GSMA-certified SGP.32 eSIM ecosystem for remote provisioning, Cisco's IoT Control Center with SGP.32 orchestration capabilities, and Tele2 IoT's global connectivity and network onboarding. It enables enterprises to provision, manage, and switch device profiles worldwide from a single platform and a single eSIM SKU, eliminating the need for region-specific SIMs, manual provisioning, and physical swaps. The partnership specifically targets industries with global connectivity requirements such as automotive, claiming to reduce deployment timelines from months to minutes.

analysis

Tele2 IoT (MNO connectivity), IDEMIA (SIM OS and eIM infrastructure), and Cisco (connectivity management platform) launching a commercial end-to-end SGP.32 solution is a strong signal. When three players of this scale commit production resources across all layers of the stack, it moves SGP.32 from specification to infrastructure. The question that follows is whether this kind of vertically integrated partnership delivers the multi-vendor interoperability SGP.32 was designed to enable, or a new form of bundled lock-in with a standards-compliant label. Either way, the ecosystem just got more serious.

Read original source →

KORE and Kigen announce joint SGP.32 connectivity portfolio

· Source: KORE Group press release

KORE Group Holdings announced a new portfolio of SGP.32-compliant connectivity solutions in partnership with Kigen, with commercial availability planned for later in 2026. The portfolio supports devices ranging from high-power gateways to battery-powered sensors, enabling remote provisioning, multi-network resilience, and lifecycle management.

analysis

This is a major MVNO + eUICC vendor commercial partnership under SGP.32 announced publicly. KORE provides MVNO scale; Kigen provides neutral-party eUICC and eIM infrastructure. The typical gap between announcement and commercial availability under SGP.32 is several months, reflecting certification and interoperability testing as the remaining bottleneck.

Read original source →

Rivian R2 integrates SGP.32 eSIM with G+D and AT&T

· Source: Giesecke+Devrient announcement

Rivian announced its R2 electric vehicle platform will integrate GSMA SGP.32 eSIM technology with 5G connectivity, in partnership with Giesecke+Devrient (automotive-grade eSIM and eIM infrastructure) and AT&T (US mobile network operator). This is one of the first major automotive production deployments of SGP.32.

analysis

Automotive is an ideal early vertical for SGP.32 - high per-unit value justifies certification investment, long device lifetimes (10+ years) benefit from remote profile management, and multi-region sales require a single hardware SKU. The Rivian deployment validates that G+D's automotive eSIM stack is production-ready. Expect other OEMs to follow with similar architectures over the next 12 months.

Read original source →

Telenor IoT launches standardised SGP.32 SIM cards

· Source: Telenor IoT announcement

Telenor IoT announced the commercial availability of fully standardised SGP.32 eSIM solutions. SIM deliveries begin April 17, 2026. Telenor positions the offering against non-standardised alternatives, emphasizing interoperability, simplified integration, and elimination of vendor lock-in risk.

analysis

Telenor is positioning SGP.32 compliance as a buyer risk-reduction argument - "avoid vendor lock-in" is the implicit message. This framing will become standard in enterprise IoT procurement over the next 12 months, and non-compliant vendors will face increasing pressure in RFPs.

Read original source →
Our method

What we track.

Public announcements by vendors or the GSMA naming a specific SGP.32 certification scheme: eSIM IoT Compliance (product functional), eUICC Security Assurance / eSA (eUICC product security), or SAS-SM for SGP.32 eIM operating sites (site-level, not a product cert). We also track connectivity providers as the bridge between certified components and live deployments.

What we don't track.

Generic "SGP.32 ready" or "compliant" marketing without a named scheme, partner launch announcements, IPAd module integrations without GCF or PTCRB certification, and SAS-UP factory certifications.

Sources.

Vendor press releases, GSMA announcements, and public GSMA documentation. Every entry links to its primary source. If a source disappears, we archive a copy and note it.

Known limits.

The GSMA does not publish a public registry of certified SGP.32 products, so this tracker has two structural limitations: it may be incomplete (we only see what is publicly announced), and it may contain inaccuracies (vendor announcements sometimes use loose language around scheme names, scope, or dates). Both are correctable on request.

Cadence.

Certifications and provider entries are reviewed weekly through 2026, monthly thereafter. The live signal feed refreshes every six hours. Spec versions update when the GSMA publishes.

Corrections and additions.

Email sgp32@symb-iot.com with a link to a primary source. We review within 48 hours and either add, correct, or reply explaining why we cannot include it. Corrections carry a note describing what changed.

Resources

Stay informed

Follow SymbIoT on LinkedIn for updates on SGP.32, the Maturity Framework, and the IoT connectivity marketplace.

Follow SymbIoT on LinkedIn

Know of an SGP.32 certification we should track? Email sgp32@symb-iot.com

Need Help?