IN PARTNERSHIP WITH KIGEN
One SKU. Every network. SGP.32, delivered.
FLOLIVE® pairs its global network with Kigen’s SAS-certified eIM and eSIMs, so your devices ship once, connect on power-up anywhere, and switch to compliant local profiles on demand.
What is SGP.32?
SGP.32 is the GSMA standard for remote SIM provisioning in IoT. It lets devices download and switch operator profiles over the air, with no physical SIM swap and no user interaction, using an eSIM IoT Remote Manager (eIM) and certified eUICCs. FLOLIVE® delivers SGP.32 as a managed capability on a fully owned, cloud-native global network, so you get the flexibility of the standard with carrier-grade reliability behind it.
The challenges of scaling IoT connectivity globally
Shipping and connecting millions of devices across borders and regulatory regimes is hard. Here is where single-profile and older provisioning approaches hold teams back, and what SGP.32 on Flolive changes.
One device, dozens of markets
You can’t build a separate variant or pre-assign a different operator for every country. Without a way to assign and change connectivity after manufacturing, each new market adds SKUs, inventory, and lead time.
Regulations require in-country connectivity
Many markets restrict permanent roaming and require local data handling. Devices need local operator profiles and in-region routing, not one home profile roaming worldwide.
Older M2M eSIM provisioning is complex and operator-locked
The earlier M2M eSIM standard (SGP.02) relies on heavy infrastructure and binary-SMS activation and makes changing operators slow. It wasn’t built for large, interface-less IoT fleets that pull profiles on demand.
Profiles and networks still fail
Even with remote provisioning, one active profile is a single point of failure, and switching operators can drop you out of your management platform, so you lose visibility exactly when you scale.
Why leading IoT teams choose Flolive for SGP.32
Flolive owns the full stack, including core network, CMP, SIM technology, and policy engines, and delivers SGP.32 with Kigen’s certified eIM and eSIMs, so every layer works together from day one.
Factory-to-field, zero-touch onboarding
eUICCs are pre-provisioned at the factory (In-Factory Profile Provisioning) with a Flolive Multi-IMSI bootstrap profile. Devices connect on first power-up, then pull local profiles over SGP.32 as they scale.
Ship one SKU worldwide and bring fleets online with no field handling.
Remote profile switching for compliance
Push local profiles over the air to meet in-country regulation, without hardware changes or product recalls.
Stay compliant in every market from a single deployment.
Hybrid resilience: Multi-IMSI + SGP.32
Combine SGP.32 local profiles with a Flolive Multi-IMSI bootstrap layer for global fallback if a profile or network fails.
Proven Multi-IMSI reliability today, plus SGP.32 flexibility as you scale.
No visibility lost on switch
Run natively on the Flolive network or aggregate your existing providers. The CMP Aggregator keeps full visibility and control when profiles switch operators.
One operating layer across native and aggregated connectivity.
Our SGP.32 team has shipped this before
From factory provisioning and profile validation to compliance in regulated markets, our network engineers help you map the fastest path to activation, native or aggregated.
Not all SGP.32 approaches are built equal
There are three ways to get SGP.32 into your devices: the full stack from Flolive, an eSIM platform on its own, or a stack you piece together yourself. Here’s how they compare.
Built on real global deployments
From manufacturers shipping devices direct from the factory floor to teams operating across borders, companies choose Flolive when network architecture actually matters.
Frequently Asked Questions
No. With the aggregated path you keep your existing providers and standardize operations through SGP.32 and the CMP Aggregator, so you don’t lose visibility when a profile switches.
Consumer eSIM (SGP.22) is user-initiated and built for phones and wearables. SGP.32 is server-driven and built for large IoT fleets and devices with no user interface, so profiles are managed remotely at scale.
Yes. Provisioning runs on Kigen’s SAS-certified eIM and eSA-certified eSIMs, with cryptographic authentication and encrypted profile management.
The Flolive Multi-IMSI bootstrap layer provides fallback, so devices stay connected while the issue is resolved.
Pay-as-you-grow. You scale profiles and devices as your deployment grows, without heavy upfront cost.
Yes. Speak to our team to validate factory provisioning, profile download to a Kigen eUICC, and remote switching across your target markets before full deployment.
Activate SGP.32 for your devices
Adaptive, compliant, and built for the scale the AI era demands. Tell us about your deployment and we’ll map the fastest path to activation.
Learn more about SGP.32
Understanding SGP.32: The Latest eSIM IoT Standard
SGP.32: Risks & Opportunities for Enterprises
