đŻ Short answer:
Choose the IPAe if you do not want to change your device firmware.
Choose the IPAd if you own the firmware and want more control.
IoT Profile Assistants come in two different forms. One of them "lives" inside the eUICC chip (on the SIM), while the other can be directly embedded within your device firmware.
Here is an overview and comparison:
IPAe = inside the chip
Built into the eUICC and fixed at manufacture.
The easiest path: no firmware work needed.
Needs a modem that supports it. Not every IoT module does this well, especially lower-cost ones.
We expect most customers to start here.
IPAd = in your device firmware
Runs in your firmware, so you control its behaviour.
You decide when to check in, for example whenever the device is already awake, which helps battery-powered devices.
You decide how to detect lost connectivity, which feeds into fallback.
Easier to debug, because the logic is in your own code.
Doesn't depend on the modem supporting an IPAe.
| IPAe | IPAd |
Where it runs | Inside the eUICC | In your device firmware |
Firmware work | None | Required |
Control over check-ins | Fixed interval | Fully customisable |
Modem dependency | Modem must support it | None |
Best for | Teams that want the simplest setup | Teams that own firmware and need control |
â ď¸ Important
An IPAd doesn't turn an older chip into an SGP.32 chip.
The eUICC itself stores and verifies the eIM's credentials, so you need SGP.32 hardware either way.
đĄ Learn more:
Which SIMs and devices work with the Onomondo eIM?