SGP.32 eIM

Remote eSIM management for IoT, built on an open SGP.32 core.

SymbIoT eIM is the enterprise edition of openiotrsp, our open source SGP.32 implementation. Download, enable and switch operator profiles across your fleet without touching the hardware, on a protocol layer you can read for yourself.

Talk to us View the open core Apache 2.0
Protocol path from SymbIoT eIM over ESipa to IPAd or IPAe and the eUICC, with any SM-DP+ outside the boundary. Enterprise operations sit on the openiotrsp protocol core.

What an eIM does

Profiles, managed remotely.

Change which operator a deployed device uses, over the air, at any point in its life.

Built for devices with no screen.

SGP.32 was written for headless, power-constrained IoT hardware, not phones.

One hardware SKU, many markets.

Ship the same device everywhere and decide the network later.

New to SGP.32? Start with our ecosystem tracker.

How it fits together

Same architecture: ESipa path through IPA to the eUICC, any SM-DP+ on a separate axis, open core under the enterprise layer.

openiotrsp is an open source implementation of the GSMA SGP.32 protocol, published under Apache 2.0. It handles the specification: ESipa, signed eUICC packages, profile operations, the device-facing protocol surface. Anyone can read it, run it, and verify what it does.

SymbIoT eIM is the enterprise edition built on that core. Same protocol implementation, unchanged, plus everything an organisation needs to run it in production: multi-tenancy, managed key handling, audit logging, access control, operational tooling, deployment and support.

Protocol completeness stays in the open core. The enterprise edition does not add, change or withhold protocol behaviour. Everything SGP.32 defines is in the open source implementation. What we sell is the operational layer around it.

What you get

The protocol surface is in the open core. The enterprise edition adds the operations layer.

In the open core (Apache 2.0)

  • Signed eUICC package operations: download, enable, disable, delete, list profiles
  • ESipa over HTTPS and CoAP/DTLS
  • IPAd and IPAe device paths
  • Indirect profile download
  • Full SGP.32 protocol surface

In the enterprise edition

  • Multi-tenant isolation
  • Managed signing key handling
  • Audit logging
  • Role-based access control
  • Web console and REST API
  • Bulk operations across device groups
  • Hosted in any region, or self-hosted, with support

openiotrsp

The open core

The SGP.32 protocol implementation behind SymbIoT eIM is openiotrsp, published under Apache 2.0. Read the ESipa handling, the signature verification and the profile operations. Run it locally. Test it against your own hardware before you talk to us about anything commercial.

The enterprise edition imports the same core unchanged. Protocol completeness stays open source, permanently. That means an independent reviewer can verify our implementation without an NDA, and it means the protocol layer you depend on is already yours.

Repository Apache 2.0 v0.2.18 
git clone https://github.com/openiotrsp/openiotrsp.git
cd openiotrsp
docker compose up

That starts the eIM, Postgres, and a mock IPA. The first request is a direct-download trigger against the public sysmocom test SM-DP+. See the repository README for the exact sequence.

Deployment

Run the core yourself.

Clone openiotrsp and run it on your own infrastructure. No commercial relationship required.

Hosted in your region.

The enterprise edition can be hosted in any region you require, including the EU. Data stays in the region you choose.

Self-hosted enterprise.

Deploy the enterprise edition on your own infrastructure, with support. No dependency on us being in the path.

Regulatory posture.

GDPR, EU Data Act export and erasure, Cyber Resilience Act vulnerability handling, NIS2 alignment where applicable.

Who it is for

Device makers and OEMs

Bring your own hardware to the open core and test it yourself before you talk to us about a commercial deployment.

See the open core

Connectivity providers and MVNOs

Offer eSIM management to your customers on an implementation you can read. The protocol layer is not owned by an operator, SIM manufacturer or connectivity reseller.

Talk to us about a provider deployment

Enterprise fleet owners

Download, enable, disable and delete profiles across devices without a truck roll. If you leave, the protocol implementation is already public and you can run it yourself.

See how you can run it

Resources

Ungated. No email required.

Contact

Five fields. Or book a conversation if you already know what you need to ask.

Email to book a time

Independent and European. Not owned by or tied to an operator, SIM manufacturer or connectivity reseller. Hosted in the region you require, or on your infrastructure.