The invoice arrives and it does not match the quote. A batch of devices crossed a border in the night and picked up a roaming surcharge nobody costed. Three SIMs burned through their allowance while forty sat at 10% of theirs. Buried in the line items is an activation fee you were told had been waived.
This is the normal state of enterprise IoT connectivity billing. The per device figure on a pricing page is the start of the conversation, not the price you pay in month 14 across six countries.
Most IoT connectivity is priced per SIM, per month, with a data allowance attached. That model works when every device sits in one country and uses roughly the same amount of data every month. Few enterprise fleets look like that.
Real fleets have a long tail. A vehicle tracker crossing three borders before lunch behaves nothing like a static meter in a basement. A camera streaming after an alert behaves nothing like a sensor sending 2KB a day. Price the fleet on an average and you pay twice: overage on the devices above the line, waste on the devices below it.
The fees that follow are not fraud. They are the cost of a pricing model that does not match how devices behave.
None of these are secret. They are in the contract. They are hidden in the sense that they do not appear in the number you compared providers on.
Three things have to be true before a per device cost holds up over a multi year deployment.
Data has to pool. If allowances are locked to individual SIMs, a fleet with varied usage will always produce overage and waste at the same time. Pooling across the fleet means the heavy devices draw on the headroom the light devices leave behind.
The carrier relationships have to sit with one party. Five country contracts mean five renewal dates, five rate cards, and five sets of zone definitions to reconcile. Consolidation saves admin time. It also removes the seams where surcharges appear.
Usage has to be visible while it is happening. A cost control conversation that starts 48 hours after the spend is a post mortem. Many provider portals report usage with a 24 to 48 hour delay, which means the first signal of an anomaly is the invoice.
IXT Global SIM is one SIM covering 600+ mobile networks across 190+ countries, as a physical SIM, eSIM, or iSIM. IXT holds the carrier relationships. You do not negotiate per country.
IXT Global Data Pool combines the data allocation of every SIM in the fleet into one pool, sized on average usage per SIM across the active estate. High use devices draw from the headroom of low use ones. Per SIM overage stops being a line item because there is no per SIM cap to exceed.
TheIXT CMP is included with every subscription and shows the fleet in real time: active SIMs by country, connectivity status, data usage with threshold alerts, and billing overview. Thresholds fire while the spend is happening. The API pulls the same live data into your own systems.
Security is part of the standard offering, not a line you add later. IXT SecureNet keeps device traffic off the public internet with private APN and DNN, private IP addressing, dual IPSec tunnels, and direct connections to AWS, Azure, GCP, and Alibaba. IXT Zero Trust adds Zscaler ZTNA with no exposed ports and no client software on the device, plus real time traffic mapping and policy based segmentation through IXT Zero Trust Visualisation. For customers who choose not to take Zero Trust, SecureNet on its own is the lighter option.
On price itself: fleets under 100 SIMs order directly at store.ixt.io. Above 100 SIMs, or where SecureNet or Zero Trust is in the picture, pricing depends on fleet volume, usage pattern, and pool sizing, so it is scoped with a person, not quoted from a page. IXT does not compete on the lowest price per MB.
1NCE prices a fixed data volume over a fixed device lifetime, paid once. For simple, high volume, low bandwidth deployments that never move much, that model is hard to beat on cost and easy to forecast. It does not include private networking or Zero Trust, so compliance driven fleets outgrow it.
Soracom, Hologram, and Emnify publish per MB and per SIM rates on cloud native, virtualised architectures. Rate transparency is good. Cost predictability across a large multi country fleet is a different question, because per SIM pricing reintroduces the overage and waste problem, and reporting delays limit in month control.
Carrier IoT data plans from operators such as Deutsche Telekom offer strong domestic terms and a familiar procurement route. Cross border behaviour is where the zone definitions matter, and that is where the comparison should be run.
IXT runs a dedicated mobile core built for IoT from the ground up, not virtualised on shared infrastructure. That gives direct control over routing, policies, and pooling behaviour. Fewer trade-offs for most multi country IoT deployments.
It depends on data volume per device, the countries involved, whether data is pooled, and whether private networking is required. A quoted per device figure without those four inputs is not comparable between providers. For IXT, fleets under 100 SIMs are priced at store.ixt.io and larger fleets are scoped directly.
The recurring ones are per SIM data overage, roaming surcharges outside the home zone, activation and reactivation charges, separately billed SMS and signalling, platform tiers that put API access behind an upgrade, and shortfall billing against a minimum device commitment.
Pooling removes per SIM overage, because there is no individual cap to exceed. The pool itself has a size. If the whole fleet exhausts it, every SIM is affected until it is topped up, so realistic usage estimates at setup matter.
Because cost control depends on acting inside the billing period. With a 24 to 48 hour reporting delay, a runaway device is discovered after the spend. Real-time visibility with threshold alerts turns that into an intervention.
Not always on the raw rate. It is more predictable, because there is one rate card, one set of zone definitions, one renewal, and one party accountable when a device does not connect. For most cross border fleets that predictability is worth more than the per MB difference.
Private networking and Zero Trust are part of how IXT delivers connectivity, not a bolt-on bought after a security review. They are scoped with the subscription, which is why security led deployments are priced with a person, not from a page.
Bring the real fleet to the conversation: device count now, device count in year 3, countries, data per device per month, and how much of the estate moves. Pricing built on that holds. Pricing built on an average does not.
Ask us how it works for your deployment. Book a demo at ixt.io.