Acquired by SUSE, announced 19 February 2026

Migrating from Losant

What happened

Worth checking before you decide

• The stated direction is industrial and edge-first, wrapped into a broader enterprise open-source stack. If your use case is industrial, that alignment may work in your favour.
• If you are a smaller team or a system integrator delivering non-industrial projects, it is worth confirming how your segment fits the new roadmap.
• Open-sourcing the technology is a meaningful commitment against lock-in, and is a genuine argument for staying.
• As with any acquisition, packaging and commercial terms are the things to confirm at your next renewal.

How Losant concepts map to Qubitro

The migration, step by step

1. 1

   Export your historical data

   Pull device telemetry out of Losant before you change anything. Historical data is the piece that is genuinely hard to recreate; devices and dashboards can be rebuilt at any time.

2. 2

   Recreate devices, ideally from templates

   Check whether your hardware is in Qubitro's template library — if it is, the payload decoder and a starter dashboard already exist and there is nothing to write. Otherwise create the device and add a decoder function.

3. 3

   Re-express workflows as functions

   This is the bulk of the work. Losant workflows are visual; Qubitro uses JavaScript functions and JSONata expressions. Straightforward transforms port quickly; long branching workflows deserve a review rather than a literal translation.

4. 4

   Point connectivity at Qubitro

   Repoint your LoRaWAN network server integration, MQTT clients or webhooks. Devices can publish to both platforms during a cutover window so you can verify data before switching off the old path.

5. 5

   Rebuild dashboards and alerts

   Template-backed devices start with a working dashboard. Re-create alert rules and notification channels, then run both systems in parallel until the alerts match.

Common questions

Is Losant shutting down?

No. SUSE acquired Losant and is building it into SUSE Industrial Edge, with a stated intention to open source the technology. This is a change of ownership and direction, not a shutdown. If the new direction suits you, staying is a reasonable decision.

Why would I move if Losant is not shutting down?

Usually because of fit rather than urgency. The stated focus is industrial and edge within a broader enterprise open-source stack, and teams whose work sits outside that — smaller integrators, connected-product companies, non-industrial monitoring — sometimes find a change of direction is a good moment to re-evaluate. If your use case is industrial, that same change may be a reason to stay.

How long does a migration take?

For a project whose hardware is already in Qubitro's template library, moving devices and dashboards is typically days rather than weeks. The variable is workflow complexity: a handful of transforms ports quickly, while a large library of branching workflows needs to be reviewed and rewritten.