Cloud Care Networks

SGP.32 eSIM · eSIM Manager

Pick the carrier
after the device ships.

Cloud Care SGP.32 eSIMs and the eSIM Manager load, switch and roll back operator profiles over the air. Use our plans, a partner's line or your own carrier contract, on one chip.

  • GSMA SGP.32 v1.2
  • Card, MFF2 and iSIM
  • Second eIM in the contract
  • One API with your plans and usage
Cloud Care SGP.32 eSIM cards in navy, graphite and blue finishes
Available todayMulti-carrier plans with AT&T & Verizon failover

Three ways in

Start where your devices are.

  1. Available today

    Run on our multi-carrier plans

    Routers, hotspots and gateways from our shop arrive activated. Unlimited Premium fails over to AT&T and Verizon on its own, with no contract.

    Plans from $45/mo

  2. Evaluation · by quote

    Retrofit the fleet you have

    An SGP.32 card in the SIM slot your routers and gateways already have. Load our profiles, a partner's or your carrier contract, and switch between them over the air.

    Lab check, then a 90-day evaluation

  3. Design-in · by quote

    Build it into your product

    MFF2 soldered at the factory or iSIM in the module. Sell your own connectivity and still let the channel load its carrier, on the same chip.

    Samples & reference design

How SGP.32 works

Ship one SKU. Choose the carrier in the field.

SGP.32 is the GSMA eSIM standard built for IoT. The SIM stops being a carrier's part and becomes a slot that whoever runs the eSIM Manager can fill remotely.

  1. 01

    A neutral chip

    The eUICC ships in the device with a bootstrap profile, so it can reach the eSIM Manager from first power-on.

  2. 02

    An eSIM Manager you control

    The eIM signs each operation: download, enable, disable, fallback. Every enable carries a rollback timer.

  3. 03

    Profiles from any source you contract

    Cloud Care plans, a partner's line, or your own carrier contract by activation code. Several can live on one chip.

The SGP.32 line

Three formats. One eSIM Manager.

GSMA SGP.32 v1.2 eUICCs, personalised with our eSIM Manager and a bootstrap profile, with an EID manifest for every shipment. Volume pricing by quote.

  • Cloud Care eSIM CC-ESIM-32-TC, triple-cut 2FF/3FF/4FF cardCC-ESIM-32-TCProduct render

    2FF · 3FF · 4FF

    Triple-cut card

    For devices already in the field. Fits the existing slot; no new modem firmware.

    • Profile assistant on the card (IPAe); modem needs BIP/STK
    • Bootstrap profile and eIM association at personalisation
    • Up to 10 operational profiles
    • Industrial temperature range
  • Cloud Care eSIM CC-ESIM-32-M2, MFF2 embedded chips on tape and reelCC-ESIM-32-M2Product render

    DFN-8 · 6 × 5 mm

    MFF2 embedded

    For new hardware. Soldered at manufacture: no slot, no tray, one SKU for every market.

    • Tape and reel; standard SMT reflow
    • Personalised before reel delivery, EID manifest per shipment
    • Up to 10 operational profiles
    • Reference footprint and bring-up support
  • Cloud Care iSIM CC-ESIM-32-IS inside a cellular moduleCC-ESIM-32-ISProduct render

    Inside the cellular module

    iSIM

    For next-generation designs. Zero board area and the lowest power for LTE-M and NB-IoT.

    • Runs in the module's secure enclave
    • Qualified per module and design
    • Same profiles, eSIM Manager and API

Cloud Care eSIM Manager

Every profile on every chip, from one screen.

The eIM is the SGP.32 server that signs operations and delivers them to the chip. Your team gets the console, your platform gets the API, with the same objects in both.

console.cloudcarenetworks.com/esim/euiccs
Fleet / eUICCsCC

eUICCs

Every Cloud Care eSIM in the programme, with the profile each one is running right now.

Import EIDsNew operation
  • Managed

    1,284

  • On a carrier

    1,197

  • Bootstrap only

    72

  • In flight

    12

  • Attention

    3

AllHouse planPartnerCustomerBootstrapAttention
Device · EIDEnabled profileStatePoll
Industrial router · 24W43-0117EID …5678 9447 1AT&THouse planEnabled2 min
Industrial router · 24W43-0118EID …5678 9447 2AT&TCustomer contractEnabled4 min
Vehicle gateway · VG-00412EID …5678 9448 8T-MobileHouse planDownloadingnow
Edge AI gateway · SE-00031EID …5678 9449 0Partner MVNOPartner profileEnabled11 min
5G router · 25A02-0007EID …5678 9450 3BootstrapCloud CareRolled back1 h
Asset tracker · F5-00912EID …5678 9451 1AT&THouse planEnabled6 min
Smart meter gateway · E2-10422EID …5678 9451 9BootstrapCloud CareAwaiting profile3 min
Showing 1–7 of 1,284‹ 1 2 3 … 184 ›
The Cloud Care eSIM Manager console: fleet of eUICCs, the profile each one runs, and the operations available per chip.

Console shown with sample data.

  • Download

    By activation code or EID pre-order, enabled on completion.

  • Enable · disable · delete

    One chip or a group, in maintenance windows. The bootstrap profile is protected.

  • Rollback & fallback

    An enable that doesn't re-attach reverts on its own. A fallback profile covers lasting loss of service.

  • Staged campaigns

    Fleet changes in waves, halted automatically when failures cross your threshold.

  • Add your own eIM

    Every chip is personalised so a second eSIM manager can be added. It's a contract term.

  • Audit & webhooks

    Who asked, when the device fetched it, what happened, as signed webhooks.

Before you sign anything

Four questions for any eSIM vendor. Including us.

SGP.32 removes carrier lock-in on paper. Whether it does in your programme depends on how the chip was personalised and what the contract says.

  1. 01

    Can I add a second eSIM manager later?

    Under SGP.32, lock-in moved from the carrier to the first eIM. If the chip isn't personalised for it, the answer is no for the life of the device.

    Cloud Care: Yes, written into the contract.

  2. 02

    Which carriers can download to it, by name?

    “Any operator” is a spec-sheet phrase, not a contract. US carrier support for SGP.32 is still uneven.

    Cloud Care: Named per programme, in writing. Verizon today runs on our multi-carrier plans.

  3. 03

    What happens when a switch fails?

    First downloads usually work. The second switch, on a device in a field, is where programmes fail.

    Cloud Care: Rollback timer on every enable, a fallback profile, staged campaigns.

  4. 04

    Has my device actually been tested?

    An SGP.32 card depends on the modem's BIP/STK path, and some firmware ships with it off.

    Cloud Care: We test your model in the lab before you commit to volume.

An engineer testing an industrial router on a lab bench beside a Cloud Care SIM card and eSIM chips

What every evaluation measures

  • Download and switch success, rollback included
  • Time from request to attached on the new carrier
  • Cost per device, by plan and carrier

How programmes start

Proven on your devices before you buy volume.

  1. 1

    Lab check Weeks 1–2

    Your device and modem on our bench: BIP/STK path, first download, second switch, forced rollback.

  2. 2

    Field evaluation Up to 90 days

    Cards or MFF2 samples, your eSIM Manager tenancy, and two profile sources, one of them yours.

  3. 3

    Rollout On the evidence

    Volume pricing and contract terms set against what the evaluation measured.

Send us

Your device and cellular module, units in the field and per year, the carriers you need, your device management platform and a target date.

Developer API

One API for the SIM, the plan and the bill.

Devices, SIMs, plans, usage, suspend and resume are live today, with scoped keys, idempotent writes and signed webhooks. The eSIM resources follow the same conventions and are in preview for programme customers.

  • Live/v1/devices · /v1/sims · /v1/subscriptions · /v1/usage
  • LiveSuspend, resume and signed webhooks
  • Preview/v1/euiccs · operations · staged campaigns
list-sims.http
GET /v1/sims?device=dev_01J9X5R8N2
Authorization: Bearer cc_live_…

→ 200 OK
{ "data": [
  { "object": "sim", "carrier": "tmobile",
    "role": "primary",  "profile": "enabled" },
  { "object": "sim", "carrier": "att",
    "role": "failover", "profile": "disabled" }
] }

Anywhere a second site visit costs more than the SIM

  • Solar & storage
  • Cold chain & logistics
  • Agriculture
  • Vending & micro-markets
  • Transit & rail
  • Clinics
  • Smart buildings & HVAC
  • Oil, gas & pipelines
  • Public safety
  • Education & lending

FAQ

Straight answers.

Anything else: +1 (224) 636-8890

What is SGP.32?

The GSMA eSIM standard for IoT devices. The device ships with a neutral eUICC, and a server called the eIM (eSIM IoT remote Manager) tells it which operator profile to download and enable. Carrier changes happen over the air, without a SIM swap.

Will SGP.32 work in the devices I already own?

Often. The triple-cut card carries its own profile assistant, so no new modem firmware is needed, but the modem must have BIP/STK enabled. We check each model in the lab before you commit. If a device doesn't qualify, our multi-carrier plans cover it.

Can I get Verizon on an SGP.32 eSIM?

US carrier support for SGP.32 is still uneven, so we name the carriers for each programme in writing. Verizon is available today on our multi-carrier plans.

Do I have to buy airtime from Cloud Care?

No. The eSIM Manager can load our plans, a partner's line or your own carrier contract by activation code, and one chip can hold several.

Am I locked into your eSIM Manager?

No. Every chip is personalised so a second eIM can be added, and that is a contract term. The standard doesn't guarantee it, and many offers leave it out.

Is there an API?

Yes. Devices, SIMs, plans, usage, suspend and resume, and signed webhooks are live at api.cloudcarenetworks.com. The eSIM resources (eUICCs, operations, campaigns) are in preview for programme customers.

What about phones, tablets and laptops?

They use consumer eSIM (SGP.22), not SGP.32. Partners who sell those devices can attach a Cloud Care line with a QR activation card through our partner programme.

Put the carrier under your control.

Multi-carrier plans for the devices you buy today. SGP.32 for the fleet you retrofit and the hardware you design.

A deep navy Cloud Care SIM card standing on a polished black surface, with beams of light converging behind it