Pricing & Modules. Five plans, three deployments, and what sits on top of them.
Every plan ships the whole platform: the same dashboards, the same rules engine, the same connectors and the same public API. A plan sets the ceilings (how many devices, messages, users and workspaces) and the deployment sets who runs the infrastructure underneath. Nothing is switched off in the smaller ones.
All five plans operate under the same verified information security, interoperability and data residency standards.
Three of the five are tenancies on our EU cloud and differ only in how much room they give you. The other two are dedicated: one on your infrastructure, one on a cluster we run for you alone. We do not publish a price list: what a deployment costs depends on the ceilings, the modules and how much of the setup is project work, so we quote against a scope instead of a number on a page.
Devices and messages are included up to the ceiling, with no separate per-device licence underneath it.
A first deployment: enough room to prove the data flow end to end, with no infrastructure to run and nothing to size.
Room for a working department: a team of five in two workspaces, and a fleet that can report every few minutes without watching the counter.
The full shared-cloud tier: separate workspaces per team, dashboards you can publish to citizens, and headroom for a fleet in the hundreds.
No shared tenancy and no counters: the capacity is either yours or reserved for you.
The platform inside your own datacentre, on hardware your team controls. We license and support it; the hosting never leaves you, and neither does the data. Chosen by organisations whose security review ends with “not in a shared cloud”.
A cluster we run for one organisation and nobody else, sized to a throughput you can name: around 1,000 devices, around 5,000, or 20,000 and above. The dedicated option for teams who do not want to operate infrastructure themselves.
Where a row says project, it is scoped and quoted per site; where it says add-on, it is licensed on top of any plan.
| Feature |
Starter
Shared EU cloud |
Basic
Shared EU cloud |
Pro
Shared EU cloud |
Enterprise
Your infrastructure |
Special
Dedicated cluster |
|---|---|---|---|---|---|
| Devices | Up to 25 | Up to 100 | Up to 600 | No ceiling; bound by your hardware | Per cluster size (S, M, L) |
| Messages a month | Up to 2M | Up to 8M | Up to 25M | No ceiling; bound by your hardware | Dedicated cluster capacity |
| History retention | 12 months | 12 months | 12 months | As long as your storage allows | Sized with the cluster |
| Management users | 1 | 5 | 20 | Unlimited | Unlimited |
| Workspaces | 1 | 2 | 5 | Unlimited | Unlimited |
| Dashboards | 3 | 8 | 20 | Built to your spec | Sized with the cluster |
| Public dashboards | None | 1 | 3 | Built to your spec | Sized with the cluster |
| Real-time alarms | 5 | 15 | 25 | Unlimited | Sized with the cluster |
| Scheduled reports a month | 2 | 5 | 10 | Unlimited | Sized with the cluster |
| Public REST API and MCP server | Included, and never metered per call. | ||||
| Connectors and LoRaWAN network server | Integrated | Integrated | Integrated | Integrated | Private / dedicated |
| Modbus, OPC-UA and SCADA | Through an edge gateway, scoped as project work on any plan. | ||||
| Libelium hardware support | Yes | Yes | Yes | Yes | Yes |
| White-label | Add-on | Add-on | Add-on | Included | Included |
| Conversational assistant | Add-on | Add-on | Add-on | Add-on | Add-on |
| 3D digital twin | Add-on | Add-on | Add-on | Add-on | Add-on |
| Blockchain fingerprint | Add-on | Add-on | Add-on | Add-on | Add-on |
| AI data quality for air | Add-on for air deployments, licensed per record processed. | ||||
| Vertical modules | envair360, grid360, parking360 and crowd360 are licensed on top of any plan, in any deployment. nebula360 and berry360 are scoped on request. | ||||
| Runs on | Our EU cloud | Our EU cloud | Our EU cloud | Your infrastructure | A cluster we run for you |
| Data residency | EU | EU | EU | Wherever your infrastructure is | Named in the contract |
| ENS and ISO/IEC 27001 | Certified at platform level. The applicable ENS level per plan is stated in the evidence pack, with the certifying body and the valid-until date. | ||||
| Availability commitment | Commercial terms | Commercial terms | Commercial terms | Shared responsibility; your infrastructure | Contractual, named per cluster |
Five capabilities sit outside the plans because not every deployment wants them, and pricing them into the base would charge everyone for what a few use. Each one is licensed on top of whichever plan you are on, in any deployment.
White-label
Your domain, your logo and your colours across the whole interface, so the platform reads as yours to the people using it. The route resellers and partners take.
Included on Enterprise and SpecialConversational assistant
Ask the deployment questions in plain language and get answers grounded in your own readings, not in a generic model. Useful where the people who need the number do not use dashboards.
Add-on on any planBlockchain fingerprint
Readings are hashed and anchored on Polygon in batches, so a third party can verify that a series was not edited after the fact. For evidence that has to survive a dispute.
Add-on on any plan3D digital twin
The site as a navigable 3D model with live telemetry on it, built on Cesium. What a control room shows on the wall when a map is not enough to explain the situation.
Add-on on any planAI data quality for air
Cross-validates and corrects Smart Spot F air readings before they land, so the series you report against is the corrected one. Licensed per record processed.
Add-on for air deploymentsCrossing a ceiling on a shared-cloud plan does not stop ingestion and does not force a plan change. Each resource can be topped up on its own, monthly, and the finder below tells you which ceiling you are close to.
Fleet and throughput
When the field grows faster than the plan did.
People and workspaces
When another team needs its own view of the same core.
What the platform puts out
When more people need to be told, more often.
Each one adds its own data models, algorithms and screens to the deployment you already have. You license them per department, on top of any plan, and the core underneath does not change.
Measures what people breathe and models where it goes next, so a restriction can be defended in public with a number attached to it.
Deployed for low-emission zone scenario modelling in a city of 800,000.
Four numbers you already know, and the two constraints that override them. It names the plan your scope lands in and shows how close you are to each ceiling. It does not quote a price: there is no list price to quote, and a made-up figure would waste your afternoon and ours.
The commercial questions that come up between the demo and the tender.
Because there is no list price to publish. What a deployment costs depends on the plan ceilings you need, where it runs, which vertical modules you license and how much of the setup is project work. We quote against a scope, and the finder above tells you which plan that scope lands in before any commercial conversation starts.
Nothing stops ingesting. You either add the resource that ran out as a top-up (devices, users, workspaces, dashboards, reports, storage or ingestion) or move up a plan, which is usually the better deal once the overage is permanent rather than seasonal.
Yes. Moving between Starter, Basic and Pro is a change of ceilings on the same tenancy: no migration, no downtime. Moving to Enterprise or Special is a migration: your organisation, data models, dashboards and rules are exported and restored, and the fleet is re-pointed at the new endpoint. We have done it inside a maintenance window, but it is planned work, not a button.
The same platform. The same dashboards and rules engine, the same connectors and LoRaWAN network server, the same public REST API and MCP server, and Libelium hardware support. Plans differ in ceilings and in who runs the infrastructure, not in which features were switched off.
Enterprise and Special include full white-label as part of the plan. On Starter, Basic and Pro it is an add-on covering your own domain, logo and colours across the interface. If you are reselling iris360 to your own customers, talk to us before you quote: the licence structure differs from a direct deployment.
No. envair360, grid360, parking360 and crowd360 are licensed on top of any plan, in any deployment. Two more, nebula360 and berry360, exist as product and are scoped on request. Each adds its own data models, algorithms and screens to the deployment you already have; the core underneath does not change, which is why a module can be added mid-contract without touching what is already running.
Forty minutes on your data model, with one source you need ingested and one system that needs the data afterwards.
English English 
Español
