Ambimat’s eSIM property is the engineering practice for the SIM itself — eUICC and eSIM applet development, remote SIM provisioning, and using the SIM as a root of trust for authentication rather than as a connectivity component alone.
It sits inside the AmbiSecure family, because the underlying discipline is the same one AmbiSecure applies to smart cards and secure elements: writing and personalising applets that run on tamper-resistant silicon. The SIM just happens to be the secure element that is already in every phone and most cellular IoT devices.
Using the SIM already in the device to prove who is calling, instead of sending a one-time code to a messaging inbox that can be intercepted, redirected or socially engineered.
The profile and provisioning side: eUICC platforms, remote SIM provisioning, and what changes operationally when the SIM stops being a card somebody physically inserts.
Java Card applets written for SIM and eSIM form factors, loaded and personalised through the same tool-chain discipline AmbiSecure uses for smart cards and secure elements.
Getting the platform into an operator’s environment, and applying the same identity model to eSIM in IoT fleets where devices outlive their deployment contracts.
The problem the practice is built around is a specific one: authentication has been living in the messaging inbox, and the messaging inbox was never designed to be a security boundary. Moving that proof into the SIM changes where the trust actually sits — into silicon the subscriber already carries, issued through a process an operator already controls.
The work is being taken through an India telecom collaboration path, from sandbox deployment toward operator evaluation and production. The current programme status is documented on the specialist site rather than summarised here, because it moves.
Four decades of embedded engineering sit underneath this. Ambimat has been building electronics since 1982 and secure identity hardware since 2017, and the eSIM practice draws on the same secure-element selection, applet engineering and personalisation capability as the rest of AmbiSecure — together with the device-side experience that decides whether a security model survives contact with real hardware in the field.
Architecture, solution detail, case studies and the current telecom-collaboration status are on the dedicated eSIM property.