SGP.22 vs SGP.32
TL;DR
SGP.22 targets devices with a screen and a human user (smartphones, tablets). SGP.32 is built for headless IoT: the device asks the server for a profile, no QR codes, no human input.
Comparison table
| Criterion | SGP.22 (Consumer) | SGP.32 (IoT) |
|---|---|---|
| Provisioning model | Pull with activation code | Autonomous Pull (eIM) |
| Screen required? | Yes (QR or code) | No, headless |
| New component | LPA | IPA + eIM |
| Published | 2016, refined in 2020 | May 2023 |
| Use cases | Phones, tablets, wearables with UI | Industrial IoT, sensors, vehicles, meters |
| Silicon availability | Mature, abundant | Certified modules since late 2024 |
When SGP.22 still works
Devices with a human UI (smartphones, tablets, wearables with screens) or IoT products where an installer scans a QR at activation.
- ·Phones and tablets
- ·Wearables with UI
- ·Home routers with companion apps
When SGP.32 is the right call
Genuinely headless IoT devices: meters, sensors, equipment in pits, asset trackers. SGP.32 removes the human dependency.
- ·Smart metering
- ·Industrial telemetry
- ·Asset tracking
- ·Connected vehicles
Verdict
For new IoT designs from 2025 onward, SGP.32. Only justify SGP.22 if the device has a real human UI. SGP.32 modules are the default expectation by 2026.
FAQ
What about my SGP.02 deployed fleet?+
Keeps working. SGP.02 (M2M) will be supported for years. For new deployments, SGP.32 is the path.
Do I need my own eIM?+
No; your IoT aggregator (like iot.cards) runs the eIM for you. Only if you operate as your own CSP would you self-host an eIM.
More comparisons
eSIM (eUICC) vs SIM tradicional
eSIM (eUICC) wins on flexibility and long-term cost, especially when the product ships across countries. Traditional SIM still wins on simplicity and upfront price when the carrier will not change and volumes are low.
MFF2 (soldada) vs 2FF removible
MFF2 removes vandalism, vibration, and dirty contacts; ideal for industrial and outdoor. 2FF removable offers field-swap flexibility and costs less. Today the norm is MFF2 in eUICC form to get the best of both.
LTE-M vs NB-IoT
LTE-M wins when the device moves or needs low latency (asset trackers, alarms, wearables). NB-IoT wins when the device is static and needs multi-year battery with deep indoor coverage (meters, parking, sensors). When in doubt, check real coverage at your deployment country before standard specs.