Deployment options
SaaS or on-premise: you choose where Sensor-Online runs
Same platform, same features, same API. Run it as a hosted service, or install it on your own servers behind your own firewall.
500+ customers · 100,000+ active sensors · Trusted by Akademiska Hus, Vattenfall, LKAB and HSB
SaaS
We host and run it for you
- Nothing to install, ready in days
- Updates handled by us
- Role-based access and isolated tenants
- Best for property managers, pilots and fast rollouts
On-premise
In your own network, as Docker containers
- Your data never leaves your infrastructure
- Runs on your local network, also offline*
- You control updates, users and network access
- Best for municipalities, water utilities and industry
Side-by-side comparison
The platform is the same. What changes is who runs it and where your data lives.
| SaaS | On-premise | |
|---|---|---|
| Hosting and operation | Hosted and operated by Nodeledge | Installed on your own servers or in your data center, as Docker containers |
| Where your data lives | In our hosted environment | On your infrastructure, never leaves your network |
| Internet dependency | Internet connection required | Runs on your local network, also when the connection is down* |
| Updates | Handled by us | You decide when to update |
| Security perimeter | Role-based access, isolated tenants | Your firewall, authentication and audit logs, air-gap capable |
| Integration | REST API, MQTT, webhooks, Node-RED, n8n | Same, plus direct links to your internal systems |
| Getting started | Nothing to install, ready in days | Planned and installed together with us |
| Operation and support | We run it | Your IT team runs it, we support you |
| Pricing | Tailored to your project, ask us | Fixed license, no per-device or per-message charges |
| Best for | Property managers, pilots and fast rollouts | Municipalities, water utilities and industry with strict data requirements |
* Optional features such as e-mail/SMS alerts, AI analysis and public LoRaWAN networks use external services.
Why teams choose on-premise
For organisations where data control, uptime and security requirements come first.
Data sovereignty and ownership
Your sensor data stays on your own infrastructure. No external provider has access to your readings, production data or consumption figures.
Works without internet
Collection, storage, alarms and dashboards keep running on your local network, even when the connection to the outside world is down.
Security on your terms
Your team controls network access, firewall rules, authentication, certificates and audit logs. The platform can run in air-gapped networks.
Fewer suppliers to assess
Fewer external providers in the chain makes it easier to meet NIS2-era requirements on control over data and suppliers.
Fast local response
Processing next to your equipment keeps latency low for alarms, protocol transformation and closed-loop control.
Predictable cost
A fixed license model means cost does not grow with every extra sensor, data point or message.
Why teams choose SaaS
For teams that want results quickly and prefer not to run infrastructure.
Up and running in days
Nothing to install. Connect your sensors and start building dashboards the same week.
No servers to manage
We take care of hosting and updates so your team can focus on the use case.
Access from anywhere
Dashboards, alarms and reports in any browser, for operators, managers and customers.
Scales with you
Start with a pilot and grow to thousands of sensors without changing platform.
The same platform, either way
- Dashboards
- Alarms and notifications
- Automated reports
- REST API
- MQTT
- Node-RED and n8n
- Protocol transformation
- Private LoRaWAN server
- Multi-tenant
Which one fits you?
Choose SaaS if you…
- want to start within days
- prefer not to run servers
- run a pilot or a first rollout
- need access for many users in many places
Choose on-premise if you…
- must keep process data inside your own network
- operate in a regulated sector such as water, energy or the public sector
- need operation to continue without internet
- want to integrate directly with SCADA, PLC and internal systems
- have an IT team that can run the servers
Not sure? Tell us about your project and we will recommend the right model.
Frequently asked questions
What is the difference between SaaS and on-premise IoT?
With SaaS, Sensor-Online runs in a hosted environment that we operate for you. With on-premise, the same platform is installed on your own servers or in your data center, as Docker containers, so your data stays inside your own network.
Are the features the same in both models?
Yes. Both deployment models offer the same core capabilities: device connectivity, real-time monitoring, dashboards, alarms, reporting, automation and the REST API.
Can Sensor-Online run without an internet connection?
Yes, when installed on-premise. Data collection, storage, alarming, dashboards and reporting run on your local network. Optional features that rely on external services, such as e-mail/SMS alerts, AI analysis or public LoRaWAN networks, need a connection.
Does on-premise help with NIS2?
It helps you meet NIS2 requirements on control over data and your supplier chain, because fewer external providers handle your process data. NIS2 and the Swedish Cybersecurity Act apply to organisations, so compliance remains your own responsibility.
How is the on-premise version installed?
As Docker containers in your environment, behind your firewall. We plan the installation together with you and your IT team.
What does it cost?
It depends on the number of sites, sensors and the model you choose. Talk to us and we will give you a clear proposal.
Not sure which model fits? Talk to an engineer.
Tell us about your sensors, sites and requirements, and we will recommend how to run Sensor-Online.
Sensor-Online helps you meet NIS2 requirements on control over data and your supplier chain. Compliance remains each organisation's own responsibility. All trademarks belong to their respective owners.