Technical guides

How to choose an IoT SIM

Picking the wrong SIM at project start costs money and usually delays launch by months. This guide walks the decisions in the right order, starting from your use case and ending at the tariff. Each step keeps the essentials and leaves detail to the glossary and comparison pages.

How to size your IoT data plan

Oversizing the plan throws money away. Undersizing blows the bill on overages. This guide gives you the method to estimate, pick the plan type, and put controls in place to avoid surprises.

How to configure the APN on an IoT SIM

A misconfigured APN is the number-one reason a device does not connect after install. This guide shows the right flow on industrial routers, modems via AT, and the checks to rule out other problems.

How to migrate from 2G to LTE-M

The 2G sunset is underway in Spain and the rest of the EU. If your IoT fleet runs on GPRS, you have a window between 2026 and 2030 to migrate, depending on carrier. This guide orders the process so you do not get caught with stuck devices.

How to plan a multi-country deployment

Selling or deploying IoT abroad multiplies the headaches: roaming regulation, uneven coverage, time zones, taxation. This guide orders the decisions you must take before manufacturing or shipping the first device.

How to detect IoT fraud and anomalies

A stolen IoT SIM, a buggy firmware, or an attacker abusing the modem can multiply your bill 100x in hours. This guide shows how to see it coming and cut it before it hurts.

How to integrate with the iot.cards REST API

The iot.cards REST API lets you manage every SIM's full lifecycle (activate, suspend, terminate, change plan, alarms, CDRs) from your own system, without touching the portal. This guide walks through the minimum viable integration that 90% of customers implement, with Python and Node examples and notes on the mistakes we see most often in production.

Pre-deployment IoT checklist

This is the list to sign off before ordering the first mass batch of SIMs and devices. Every item is a failure mode we've watched stall deployments mid-campaign. Print it, walk through it with your hardware, software, and operations leads, and file it with the project contract. Anything missing when the batch arrives costs between 5x and 20x more to fix in the field than to fix beforehand.