Independent IoT connectivity

Your IoT, operated.

One accountable party for the connectivity, the devices and the cost of your estate — on a platform we build and run, over tier-one partner networks.

Network-independent
Tier-one partner networks, chosen per deployment
Platform in-house
Management, mediation, rating and billing built and operated by us
EU-based
Data residency and support inside the EU
IoTo FMP dashboard: active devices, active SIMs, offline devices, tenants and data pipeline, with a natural-language query bar

Getting started

Three steps, and none of them is a six-month procurement cycle.

Step 01

Tell us where your devices sit

A country list and a monthly volume. You get coverage, roaming constraints and a real ratecard.

Talk to an Expert
Step 02

Test SIMs in your own hardware

Physical SIMs or eSIM profiles in your own hardware, with portal and API access. No commitment.

Request test SIMs
Step 03

Scale with the numbers visible

Move across knowing what each session costs, and reconcile the invoice against the sessions behind it.

See how billing works

The IoT Operator model

Somebody has to own the whole thing.

Most estates run through four suppliers — a SIM vendor, a device platform, a data pipeline and a spreadsheet reconciling them. Nobody owns the join.

An IoT Operator takes the whole thing — connectivity, hardware, data and cost — and answers for it.

CMPConnectivity

The SIM estate: lifecycle, reach and what it costs.

  • SIM and eSIM lifecycle, provisioning orders
  • Session history and consumption analytics
  • Rate plans, mediation and billing
  • SGP.32 eUICC and eIM campaigns
DMPDevices

The hardware: whether it is alive, what it reports, and what you can make it do from here.

  • Live telemetry streamed from the device
  • Device health, signal and battery
  • Remote commands, cloud to device
  • Telemetry templates per device type
FMPFleet & assets

The operation the devices exist to serve — where connectivity and hardware answer the same question.

  • Assets, projects and customer dashboards
  • Geozones, trips and arrival tracking
  • Cross-domain alert rules and incidents
  • Bulk operations across the estate

To be precise about the word. We operate your IoT, not a mobile network. We buy coverage from operators who own the towers, and own everything that decides what your estate does and what it costs.

How we work

Eight questions, answered before you commit hardware.

Where the devices sit. Coverage and technology. Whether you are allowed to stay. Consumption, cost across the term, and what breaks the model. Which SIM, in which form. And what happens when it goes wrong.

Answered together in week one, with sources — or discovered one at a time over the following year.

How we work
Proceed

The shape holds. Ratecard and threshold policy with it.

Re-shape

It works with one thing changed. We say which.

Not yet

Sometimes the economics are not there. Better said now.

Every figure carries its source, and the questions run in parallel. The speed comes from removing the wait — never a check.

The platform

One platform, from SIM activation to settled invoice.

Most providers assemble connectivity management, mediation and billing from three vendors and hope the seams do not show. We run them as one.

Six services, one platform
01

SIM & eSIM management

Lifecycle, provisioning and IMEI lock, with SGP.32 eUICC registration and eIM campaigns.

SIM · eUICC · eIM campaigns · SGP.32
02

Fleet & asset management

Devices, assets and projects on one map, with telemetry, remote commands and geozones.

Device map · Telemetry · Commands · Geozones
03

Connectivity control

Networks and rate plans as system-of-record objects, with thresholds and hard limits.

Networks · Rate plans · Thresholds & limits
04

Mediation & billing

Real-time CDR processing feeding cost by network, customer and period. Exports in full.

CDR pipeline · Sessions · Cost breakdown · CSV
05

Alerts & assurance

Incidents, anomalies, alert rules and notifications. The fleet tells you.

Incidents · Anomalies · Alert rules
06

Analytics & reporting

Consumption trends, IMSI statistics and per-network breakdown. Plus scheduled reports.

Consumption · IMSI stats · Reports

Under the hood

Built as telecom infrastructure, not as a dashboard.

Engineered for the volumes each of them generates — in the same system of record.

Ingestion

MQTT at device scale

Devices publish to a broker. The platform subscribes, streams and stores.

Pipeline

Event-streamed, durable

Telemetry, CDRs and events on a streaming backbone. Nothing lost between network and invoice.

Rating

A dedicated mediation service

CDRs enriched, deduplicated and rated as a separate service.

Analytics

Column-store at fleet volume

Session history, telemetry and billing rollups in a store built for the query.

Isolation

Row-level tenancy

Enforced in the database, not by a filter someone can forget.

The difference

Most platforms show you usage. We show you business value.

Your fleet produces two separate worlds of data. Connectivity knows what each SIM cost, on which network, under which plan. The device knows where the asset is, how warm it is, what battery is left. Most platforms give you one. We join both in one system of record.

  • Connectivity: the financial truth. CDRs rated as they arrive, priced against the roaming records operators actually exchange — not estimated from a nominal rate. Cost by SIM, network, customer and period, reconciled to the source before you see an invoice.
  • Device: the physical truth. Location, movement, geozone, temperature, battery, signal, sensor state — what the asset is actually doing, stored beside its connectivity record.
  • Joined, so each explains the other. Not two products sharing a login. Both layers land on the same data plane and surface through the same visualisation plane — one query reaches a SIM’s rated cost and its device’s telemetry, one dashboard puts them on the same timeline. So a spend spike stops being a mystery: you see the device that caused it, where it was and what it was doing, without leaving the view.
  • Rules watch the estate. Set a threshold on anything either layer reports — spend, volume, battery, a sensor outside its band, a geozone crossing, a device gone quiet. Evaluated as the data arrives, alerting the moment it is crossed. You hear about it while it is still a threshold, not once it is an invoice or a truck roll.
  • Automation puts your intent into the fleet. The same conditions can act, not just alert. Cap a SIM before the overage exists. Drop a device parked in a warehouse into hibernate — battery and airtime held until something wakes it. Call your own systems, so the trigger raises the ticket. Write the ambition down once; the estate executes it, physical and financial together.
  • Auditable end to end. Every cost, device event and rule that fired breaks down by network, customer and period. If you want to check our arithmetic, we would rather you did.
FMP Live Telemetry: active devices, points today, average battery and signal, a live map of the fleet across Europe, an event feed and battery and signal distributions
FMP geozone detail: the zone boundary drawn on a map of Rotterdam, its radius, hysteresis and operating hours, and the assets currently inside it
FMP new alert rule: asset triggers for zone enter, zone exit, arrival overdue and sustainability threshold, and device triggers for low battery, no report, signal strength, firmware, temperature, tamper and metric threshold
CMP console: tenants, customers, SIMs, MNO rate plans, networks and threshold policies as system-of-record objects

System of record

One place where the truth about your fleet lives.

Tenants, customers, SIMs, networks, rate plans and thresholds as objects in one system — not rows in four spreadsheets.

  • Multi-tenant to the core. Organisations, customers and users with their own scoped views. If you resell connectivity onward, your customers see their fleet and never yours.
  • Rate plans are objects, not attachments. MNO rate plans and customer rate plans live in the platform, versioned and linked to the SIMs they price.
  • Bulk operations and an audit log. Change a thousand SIMs in one action, and keep a record of who changed what, when, and to which value.
  • Ask it in plain language. Bob, the built-in assistant, answers questions like "show offline devices" or "top ten data consumers this month" without anyone writing a query.

Coverage

Coverage, with the part everyone else leaves out.

Everyone publishes a country list. Almost nobody publishes the constraint that decides whether you are still connected in month four.

CountryNetworksTechnologiesPermanent roamingNotes
Germany34G · 5G · LTE-M · NB-IoTPermitted
Denmark34G · LTE-M · NB-IoTPermitted
Türkiye24G · NB-IoT90–120 daysBTK data localisation; enforced
Spain34G · 5G · LTE-MPermitted
Brazil24G · LTE-MCappedLocal breakout available
China24G · NB-IoTLocal onlyRequires local profile

Illustrative rows for this concept — the live page renders from the coverage database and is searchable by country and technology.

Industries

Fleets that cross borders and stay deployed for years.

Roaming-heavy · high mobility

Fleet, logistics & telematics

Network changes several times a day, across jurisdictions with different rules.

High count · long lifecycle

Industrial automation & metering

Installed once, running a decade on LTE-M or NB-IoT. High count, low data, real roaming exposure.

Regulated · procurement-led

Utilities, energy & EV charging

Uptime is contractual and the auditors want to see how the invoice was produced.

Insights

What we know, published.

Regulation

Permanent roaming, country by country

Permitted, capped or prohibited — and what to do about each.

August 2026
Billing

How to read a roaming invoice

What the line items mean, and how to reconcile them.

August 2026
Networks

LTE-M or NB-IoT for a ten-year meter

Choosing a radio for devices you will not touch again.

July 2026

Enterprise plans

Plans shaped around how your fleet actually behaves.

Not tiers off a price list. Every plan is assembled from the same mechanics and sized to your deployment.

Pilot

Prove it in your own hardware

For teams validating a design or a supplier.

  • Test SIMs and eSIM profiles in your devices
  • Full portal and API access from day one
  • Bounded data allowance, no commitment
Typically 10–100 SIMs · 90 days
Fleet

The standard enterprise plan

For a deployed fleet across borders that needs predictable, explainable cost.

  • Pooled data across the whole fleet
  • Zone-based roaming, priced in — not added after
  • Threshold policies and hard limits per SIM group
  • Rated usage with full CSV export
  • Named support contact and agreed response times
Committed volume · annual term
Wholesale

For those who resell onward

For those carrying connectivity into their own customer contracts.

  • Multi-tenant portal with scoped customer views
  • Your own rate plans on top of ours
  • Wholesale terms and settlement-grade reporting
  • Bulk operations and full audit log
Wholesale agreement · multi-year

How every plan is built

Mechanic

Pooled data

One allowance across the fleet. No buying headroom per SIM.

Mechanic

Zones, not surprises

Zones with a stated rate. Roaming priced in, not added afterwards.

Mechanic

Bundles & credits

Commit and get a bundle. Overshoot and get credited, not penalised.

Mechanic

One line, one meaning

Invoice categories match the portal. Every charge traces to its sessions.

Why the numbers come from us, not this page. Your rate depends on where the devices sit, how they behave and what you commit to. Send a country list and a monthly volume; you get a real ratecard, usually within two working days.

Tell us about the deployment.

The questions we would ask on a first call. Answer what you know.

  • A real ratecard, usually within two working days.
  • An honest read on roaming exposure before you commit hardware.
  • Test SIMs in your own devices if it fits.

Prefer email? info@ioto-communications.com — a person reads it.

Tired of fighting your connectivity stack instead of your market?

Quietly, and without wasting each other’s time.

Start a conversation