KORE Teams with Kigen on SGP.32 eSIM to Simplify Global IoT Provisioning

Why It Matters

Enterprises can future‑proof IoT deployments, reducing costly field interventions and enabling dynamic network selection as regulations and coverage evolve. The move signals a broader industry shift toward programmable, carrier‑grade connectivity as a core service layer.

Key Takeaways

• KORE will launch SGP.32 eSIM portfolio with Kigen in late 2026
• Solution enables remote profile switching, roaming, and local failover
• Reduces truck‑roll costs by moving connectivity changes to software
• OEMs can avoid region‑specific hardware SKUs with programmable eSIM
• Success hinges on carrier‑grade integration and enterprise provisioning workflows

Pulse Analysis

The IoT market has outgrown the early‑generation eSIM model, where a single profile is baked into a device at manufacture. GSMA’s SGP.32 standard introduces a multi‑profile architecture, allowing operators and enterprises to swap carriers, adjust roaming policies, and comply with regional regulations without physical access. This evolution addresses a long‑standing pain point: the expense and delay of field‑level SIM changes, especially for assets deployed across continents. By standardizing profile management, SGP.32 lays the groundwork for a more agile, software‑centric connectivity layer.

KORE’s collaboration with Kigen translates the SGP.32 promise into a market‑ready service. Kigen supplies a GSMA‑certified eSIM and eIM platform, while KORE builds an enterprise‑focused portfolio that bundles connectivity behaviors—such as automated roaming, localized failover, and resilience templates—into selectable profiles. For IoT operators, this means the ability to re‑provision fleets from a cloud console, align network contracts with real‑time coverage needs, and defer hardware redesigns when markets shift. The approach also opens a new revenue stream: subscription‑based connectivity management that can be billed per profile change or per active device.

The broader impact reaches OEMs, system integrators, and carriers alike. Manufacturers can consolidate SKUs, embedding a single SGP.32‑ready eSIM and relying on software to adapt to regional networks, thereby cutting bill‑of‑materials and inventory complexity. Integrators must now focus on stitching provisioning APIs into existing device‑management platforms, turning remote activation into an automated workflow. Carriers, meanwhile, are compelled to expose carrier‑grade APIs and support multi‑network orchestration to stay competitive. As more enterprises demand lifecycle‑driven connectivity, SGP.32 could become the de‑facto baseline, accelerating the shift from hardware‑bound SIMs to programmable, cloud‑native network services.