One IoT SIM for Canada, the US and the world.

An IoT SIM is built for machines. A phone SIM is tied to one carrier and a monthly bundle. An IoT SIM roams across many networks, falls back to another network if the active one has a problem, supports LTE-M and NB-IoT alongside 2G–5G, and is managed in bulk from a portal and API. It also comes in industrial form factors such as MFF2, which is soldered to the board.

Yes. Our SIMs connect in more than 150 countries and territories across 700+ mobile operators, including the national networks in Canada and the US. LTE-M roaming is available on Bell, Rogers and TELUS in Canada and on AT&T, T-Mobile and Verizon in the US. We confirm coverage for your sites before you order.

A multi-IMSI SIM carries more than one network identity. When the device registers, a central server picks the best identity for that country and pushes it to the SIM over the air. If the active identity has a problem, the SIM switches to a fallback identity on its own, so the device stays online without anyone touching it.

It can be. Operators in Canada and the US can push back on devices that roam on their network long-term. Our multi-IMSI SIMs can take a local profile where one is available, so the device is treated as local while you keep the same portal and API.

Yes. Our SIMs support LTE-M and NB-IoT wherever the local network offers them, alongside 2G, 3G, 4G and 5G. LTE-M suits devices that move and need modest data; NB-IoT suits fixed, very low-power sensors. Devices can be tested on live networks for LTE-M and NB-IoT operation, fallback, eDRX and PSM before rollout.

Yes. Our eSIMs use eUICC technology and follow the GSMA SGP.32 standard for IoT. SGP.32 replaces the older SGP.02 machine-to-machine model, which relied on SMS and heavy operator integration, with a lighter push-based model built for headless, low-power devices. One eSIM can hold a bootstrap profile for first connection, operational profiles for global roaming and local profiles where regulations need them, all switched over the air.

Plug-in triple-cut cards (2FF, 3FF and 4FF) suit devices that already have a SIM slot. MFF2 is soldered to the board, so it suits vehicles, meters and outdoor equipment exposed to vibration, heat and cold. eUICC eSIM is available in plug-in and MFF2, and iSIM sits inside the cellular module for OEMs. Tell us about your hardware and we will recommend one.

Yes. Dedicated APNs with custom routing keep your traffic segregated, an IPsec VPN can carry it into your data centre or cloud, and devices can use static private IPs, your own public IPs or your RADIUS server. Traffic between the mobile network and the data centre travels over a private network isolated from the public internet.

From one self-service portal, or from your own systems through more than 200 APIs. You can activate, suspend and troubleshoot SIMs in bulk or one at a time, see usage in real time, set alerts, and connect to AWS, Microsoft Azure or Google Cloud.

Yes. Your application can send SMS to devices through the API and receive SMS sent by devices, with delivery reports posted back to your server. SMS is useful for commands and alerts when a data session is not available.

You pay per SIM and per MB used, on one contract and one invoice for every country. SIMs can be suspended when equipment is not in use — useful for seasonal assets — and reactivated later. Talk to an IoT specialist for pricing for your fleet.

It depends on the use case. IoT SIMs suit devices that move, send more data or need real-time control, and sites with strong carrier coverage. LoRaWAN suits battery sensors that must last years, hard-to-reach spots such as basements and culverts, and wide sites covered from a few gateways. Most deployments combine both on one platform, and we design for both.