TL;DR:

  • eSIM (embedded SIM) is a reprogrammable SIM soldered onto a circuit board; iSIM integrates the SIM function directly into the main SoC, eliminating a separate chip entirely
  • Both enable remote SIM provisioning (RSP): you can switch carriers, activate new connections, and manage subscriptions without physical access to the device
  • The GSMA SGP.02 spec (M2M) applies to most IoT deployments; consumer eSIM (SGP.22) is for smartphones and tablets — they’re different and not interchangeable

Deploying a fleet of cellular IoT devices with physical SIM cards involves a predictable set of problems: sourcing SIMs from the right carrier before knowing final deployment locations, physically inserting SIMs during manufacturing, redeploying field technicians when a carrier relationship changes, and dealing with SIM trays that corrode or loosen in outdoor enclosures. eSIM and iSIM address all of these by making the SIM a software configuration rather than a physical component.

What eSIM and iSIM Actually Are

eSIM (embedded SIM, or eUICC — embedded Universal Integrated Circuit Card) is a SIM that’s soldered directly to a circuit board rather than inserted in a tray. The chip is identical in function to a regular SIM — it stores credentials, authenticates to the network, and runs the same security protocols — but it’s surface-mounted during board manufacturing and cannot be physically removed or swapped. Its reprogrammability comes from the eUICC standard, which defines how operator profiles (the credentials for a specific network) are downloaded to the SIM over the air.

iSIM (integrated SIM) goes one step further: the SIM function is integrated directly into the cellular modem or application processor SoC. There’s no separate SIM chip at all. Nordic Semiconductor’s nRF9161, Qualcomm’s MDM9205, and several modules from Murata and u-blox include iSIM functionality. The board footprint shrinks further, there’s one fewer component to source and solder, and one fewer point of failure.

For practical IoT purposes, both work the same way from a connectivity management perspective — the differences are in hardware design and component count. The management infrastructure (SM-DP+ servers, RSP platforms) is the same.

The Remote SIM Provisioning Architecture

GSMA defines two RSP architectures:

SGP.02 (M2M RSP) — designed for IoT and industrial devices. Uses a centralised SM-SR (Subscription Manager — Secure Routing) server that controls which SM-DP+ (Subscription Manager — Data Preparation) can load profiles onto an eUICC. The network operator manages the SM-SR relationship. This is the architecture most enterprise IoT deployments use.

SGP.22 (Consumer RSP) — designed for smartphones. The user controls profile management directly from the device, without the SM-SR intermediary. This is what’s in your iPhone or Android phone’s eSIM. It’s not suitable for unattended IoT devices where you don’t want end-users managing connectivity credentials.

A typical M2M eSIM provisioning flow:

  1. The device boots with a “bootstrap” profile — minimal credentials that give it just enough connectivity to reach the SM-SR/SM-DP+ servers
  2. Your IoT connectivity platform pushes an operational profile over the air — the full credentials for the target operator and plan
  3. The device switches to the operational profile and connects to the network
  4. If needed, you push a new operational profile to switch carriers — the bootstrap remains as fallback

When eSIM/iSIM Makes Sense for IoT

Large-scale deployments across multiple geographies. If you’re deploying 10,000 smart meters across three countries, locking in SIMs from a single operator before deployment is risky — local regulatory requirements, coverage gaps, or better commercial terms elsewhere may require switching. eSIM lets you make that call post-deployment.

Remote or inaccessible installations. A SIM card failure or carrier issue in a device mounted on a wind turbine nacelle or embedded in a road surface costs significantly more to fix if it requires physical access. With eSIM, the fix is a remote profile push.

Long device lifetimes. A utility meter or industrial sensor expected to operate for 10-15 years will outlast carrier relationships, regulatory frameworks, and network technologies. eSIM decouples the device lifetime from a specific carrier relationship.

Harsh environments. Physical SIM trays are a point of failure in outdoor, vibration-heavy, or moisture-exposed installations. Surface-mounted eSIM chips are sealed within the PCB — they’re as robust as any other soldered component.

Where eSIM may not help: low-volume deployments where manual SIM insertion is trivial, ultra-low-cost designs where even the eSIM chip cost is significant, or devices where the connection is WiFi or LPWAN (LoRaWAN, Sigfox) rather than cellular.

Management Platforms

Eseye. Strong enterprise focus with support for SGP.02 M2M deployments. Their AnyNet Secure SIM combines eSIM with multi-IMSI capability — the device can connect to multiple operators’ networks from a single profile, improving resilience and coverage in regions where no single operator has comprehensive coverage.

Hologram. Developer-friendly platform with good API coverage. Supports physical SIM, eSIM module form factors, and their own multi-network eUICCs. Pricing is usage-based and they provide a global bootstrap profile with coverage in 200+ countries. Good starting point for prototyping and small-to-medium deployments.

1NCE. Known for their flat-rate IoT SIM offering — a one-time fee for 10 years / 500MB of global connectivity. They’ve extended this to eSIM form factors. Appropriate for low-bandwidth monitoring applications where predictable lifetime cost matters.

Twilio Super SIM. Twilio’s multi-operator SIM (physical and eSIM form factors) with programmatic management via their REST API. If you’re already in the Twilio ecosystem, the API integration is convenient. Coverage in 180+ countries via partnerships with 30+ network operators.

KORE Wireless. Enterprise-grade with strong presence in healthcare, utilities, and industrial IoT. Offers full SGP.02 RSP infrastructure including private MVNO services for enterprises that want their own branded connectivity.

Practical Considerations for Hardware Design

Form factors. eSIM chips come in MFF2 (5mm × 6mm, the standard industrial form factor) and smaller variants. Your module or SoC may include an integrated eSIM, in which case you just need to connect it to your RSP platform rather than sourcing a separate chip.

EAL rating. The GSMA requires eUICC chips to be certified to EAL4+ or EAL5 under Common Criteria. Verify the certification level of any eSIM chip you’re considering — uncertified chips may not be accepted by carriers on their networks.

Bootstrap connectivity. The bootstrap profile needs to work where your device will first boot. If a device boots in a warehouse, ships internationally, and is activated in the field, the bootstrap must have coverage in all those locations, or the initial over-the-air profile push cannot happen. Platforms like Eseye and Hologram specifically design their bootstrap profiles for this — global roaming with high reliability rather than optimised cost.

Antenna design. iSIM and eSIM don’t change antenna requirements. Cellular antenna design, placement, and certification remain the usual considerations.

Profile switching latency. Switching operator profiles is not instantaneous — it involves a handshake between your RSP platform, the SM-SR, and the device. Plan for 30-90 seconds of connectivity interruption during profile switches. Don’t switch profiles on devices that can’t tolerate a 2-minute connectivity gap.

Getting Started

The practical path for a new project: evaluate whether any cellular module or SoC in your BOM already includes eUICC functionality (many do in 2026, including the Nordic nRF91 series and several Quectel and SIMCom modules). If yes, you’re doing eSIM by default. Choose an RSP platform based on coverage requirements and volume — Hologram or Twilio for prototyping, Eseye or KORE for production scale. Request test eUICCs or bootstrap profiles from your chosen platform, integrate the remote provisioning flow into your device initialisation sequence, and test activation in the regions you’ll deploy to before committing to the hardware design.

The per-unit cost of eSIM capability has dropped substantially as the technology has matured — for most industrial IoT applications in 2026, the question isn’t whether to use eSIM, it’s which platform to use.