The Router Isn’t the Story Anymore: Robustel, Kigen and the Plastic eSIM
The Router Isn’t the Story Anymore: Robustel, Kigen and the Plastic eSIM
For a couple of years, “eSIM router” meant new silicon and a new SKU. Robustel’s move with Kigen argues otherwise: the shortest route to an eSIM fleet is often the router you already own, a plastic SIM doing a different job, and a platform orchestrating the switch.
Most eSIM coverage starts with the chip: eUICC versus MFF2 versus iSIM, which module carries what, which vendor certified first. All of that matters, but it quietly implies you need a new bill of materials to get there. A new router SKU, different silicon, a fresh procurement cycle.
What Robustel actually shipped with Kigen in late 2025 undercuts that assumption. They did not redesign the router. They put a genuine eUICC, running Kigen’s provisioning stack, inside the same plastic SIM card format the router already accepts, and paired it with their RCMS platform for the orchestration. The router did not become smarter. The SIM did.
The retrofit, in three parts
1. The card: eUICC in a familiar shape
Instead of soldering eUICC onto a new board revision, the eUICC and Kigen’s stack ship inside a standard plastic SIM. It goes into the same slot the router has always had. Nothing about the enclosure, antenna or certification of the router itself needs to change.
2. The standard: SGP.32, doing what it is built to do
Because the card is genuinely eUICC and carries SGP.32 support, the router gains real remote-provisioning capability, not a proprietary switching trick. Multiple operator profiles, provisioned and swapped over the air, on hardware designed years before SGP.32 existed.
3. The platform: RCMS as the orchestration layer
None of that is useful without orchestration. RCMS is where fleet visibility, zero-touch provisioning and profile management actually happen. It is the console that turns “the SIM technically supports this” into “we switched 400 routers onto a new operator profile this morning without a site visit.”
Why the product stopped being the star
This is the bit worth sitting with. The eSIM pitch in industrial IoT has largely been framed around the device: buy the eUICC-native router, replace the fleet. Robustel and Kigen’s retrofit quietly argues the opposite. If a standards-compliant eUICC can be delivered in the same physical format the industry has used for twenty five years, the differentiator moves up the stack, to the card’s provisioning stack and the platform orchestrating it, not to whichever enclosure happens to house the modem.
That is useful if you are sitting on a large installed base of perfectly serviceable routers that predate SGP.32. It reframes the buying question from “which eSIM router should we buy next” to “does our connectivity partner have a route to retrofit the fleet we already have.”
The push behind it is familiar: permanent-roaming clampdowns in markets like Brazil and Turkey, public tenders that now specify eSIM readiness, and buyers wanting insurance against single-carrier dependency without a hardware refresh cycle to get there.
Before you assume a retrofit path exists
- Confirm the card is genuinely eUICC. A plastic form factor alone tells you nothing. Get explicit confirmation of eUICC and SGP.32 support from whoever is supplying the card.
- Check your router’s firmware. The card carries the standards compliance, but the router still needs firmware that can work with it correctly.
- Ask which platform is orchestrating. RCMS is Robustel’s answer. On different hardware, ask what plays the equivalent role for your fleet.
- Ask if your exact model qualifies. Retrofit stories sometimes only cover the current product line, not the units already deployed.
FAQ
Can an existing router become an eSIM router without new hardware?
Yes, if the SIM slot accepts a genuine eUICC SIM with SGP.32 support and the router’s firmware can work with it. Robustel’s approach with Kigen delivers eUICC inside a standard plastic SIM card, avoiding a board redesign for existing routers.
What does RCMS actually do here?
It provides fleet visibility, zero-touch provisioning and profile orchestration, effectively playing the enterprise-facing role an eIM plays in the SGP.32 architecture.
How does a plastic eUICC card compare to a soldered chip?
Functionally the same if both are genuinely eUICC and SGP.32-compliant. The difference is physical: a soldered MFF2 chip suits sealed, tamper-resistant builds, while a plastic card keeps the option to swap it and works with hardware never designed around embedded silicon.
By James Hatton for IoT UK. Details of the Robustel/Kigen retrofit reflect their own public announcement; confirm exact model compatibility, firmware requirements and RCMS licensing directly with Robustel before specifying it into a deployment.