KORE and Kigen Are Rewriting IoT Connectivity With SGP.32
KORE Group Holdings has introduced a new portfolio of SGP.32-compliant connectivity solutions, built with Kigen. Commercial rollout is expected in 2026. SGP.32 IoT connectivity
At first glance, it looks like another standards announcement. In reality, it’s part of a much bigger shift in how global connectivity is being structured, especially for IoT.
And this time, it’s less about the technology itself and more about how it actually gets used.
What SGP.32 really fixes
The eSIM industry has had standards for years. M2M (SGP.02) handled early IoT. Consumer eSIM (SGP.22) brought flexibility to smartphones.
But neither fully solved the core enterprise problem.
How do you manage thousands or millions of devices across countries, networks, and regulations without constant manual intervention?
That’s where SGP.32 comes in.
It’s designed specifically for IoT, with a more flexible architecture that allows enterprises to remotely manage connectivity across entire fleets. Not just at deployment, but continuously over time.
And that’s the key difference.
Connectivity stops being a one-time decision and becomes something you can adapt.
The end of “truck rolls”
One of the highest hidden costs in IoT is physical intervention.
A network agreement changes. A device needs a new profile. Coverage needs to be optimized.
And suddenly, someone has to go on-site.
That’s a “truck roll.”
It sounds simple, but at scale, it’s a nightmare.
What KORE is building with SGP.32 is a model where that disappears.
Instead, enterprises can:
Remote provisioning as standard
Switch and activate profiles over the air across global deployments.
Built-in redundancy
Use multiple networks with failover and recovery logic.
Local compliance, global control
Adapt to local telecom rules without losing central oversight.
Long lifecycle management
Update connectivity strategies years after deployment.
This is not just convenience. It’s operational survival at scale.
Why this partnership matters
The combination of KORE Group Holdings and Kigen is very intentional.
KORE operates on the connectivity and orchestration layer. They manage carrier relationships and global deployments.
Kigen brings the secure eSIM and eIM technology that actually enables remote provisioning under GSMA standards.
Put together, this becomes something more complete.
Because SGP.32 is not just a spec you plug in. It requires coordination across infrastructure, provisioning, and lifecycle management.
This is where most implementations fail.
Not in theory, but in execution.
The bigger shift: connectivity becomes programmable
What’s really happening here is a shift toward programmable connectivity.
Instead of static plans and fixed network relationships, connectivity becomes something that can be:
- Adjusted dynamically
- Controlled through policies
- Optimized in real time
- Managed centrally
If this sounds like cloud computing, that’s not a coincidence.
The telecom industry is slowly moving in the same direction.
You don’t “buy connectivity” anymore. You orchestrate it.
And SGP.32 is one of the standards enabling that transition.
Where this fits in the ecosystem
The eSIM and IoT connectivity market is no longer a single layer.
You now have:
- Connectivity orchestrators like KORE
- eSIM security and OS providers like Kigen
- API-driven telecom platforms like 1GLOBAL
- Enterprise control layers like Suresim
Each solves a different part of the same problem.
What’s interesting about this announcement is that it sits right in the middle of these layers.
It’s not just connectivity. It’s not just provisioning.
It’s the integration of both.
And that’s where the market is clearly heading.
Regulation is driving more than people think
There’s another factor quietly shaping all of this: regulation.
Countries are tightening rules around:
- Data localization
- Permanent roaming
- Local network usage
For global IoT deployments, this creates constant friction.
SGP.32 offers a way around it.
You can localize connectivity when needed, switch profiles dynamically, and still maintain centralized control.
That’s not just a technical improvement.
It’s a way to stay compliant without breaking your deployment model.
Why timing matters
KORE plans to bring these solutions to market in 2026.
That timeline makes sense.
IoT deployments move slowly. Large-scale rollouts take years, not months. Standards like SGP.32 don’t win overnight. They gain traction through ecosystem adoption and real-world implementation.
The important signal here is not the launch date.
It’s the fact that companies are already building commercial solutions around it.
That means the industry is moving beyond theory.
Why this matters beyond IoT
Even if you focus on travel eSIMs, this still matters.
Because infrastructure decisions in IoT tend to shape the consumer market later.
We’ve already seen that pattern:
- Remote provisioning moved from the enterprise to smartphones
- Multi-profile eSIM became standard
- Global connectivity models evolved from IoT frameworks
SGP.32 will likely follow the same path.
It starts in the enterprise, but it doesn’t stay there.
Conclusion: the industry is aligning, finally
For years, eSIM has been fragmented.
Different standards, disconnected layers, and too much operational complexity.
SGP.32 is one of the first serious attempts to align those pieces into something that actually works at scale.
What KORE Group Holdings and Kigen are doing is not revolutionary on its own.
But it reflects a clear direction.
Compare this with players like 1GLOBAL, pushing API-driven telecom, or Suresim, focusing on enterprise orchestration.
Everyone is converging toward the same idea.
Connectivity is becoming abstracted.
Less visible. More flexible. Fully controlled through software.
According to the GSMA, IoT connections are expected to exceed 38 billion by 2030. That scale cannot be managed with legacy models.
SGP.32 is not the final step.
But it’s one of the first that actually connects the dots.
And this announcement shows the industry is finally starting to build around it.
