Oasis · Lifecycle management via REST API

Your interface. Full lifecycle control.

Every operation in the Oasis management console is available through its REST API. Bring provisioning, configuration, firmware updates and fleet operations into your existing platform, with your own customer-facing front end.

Your experience. Oasis behind the scenes.
Your integration Your platform Existing customer front end and workflows
Optional interface Management console Operates through the same REST API
Shared REST API Oasis lifecycle engine Every console operation available to your platform
Device fleet · Provision, operate and update

Every console operation. Available through the API.

Oasis is designed to be operated entirely through REST API calls. Its management console is built on the same API: every operation available in the console can be performed behind another customer-facing front end, including provisioning, configuration, firmware updates and lifecycle state management.

Device manufacturers, system integrators and solution providers can keep the interfaces their customers already use. Oasis supplies the lifecycle engine behind that experience. A new management interface is optional; your existing dashboards, workflows and branding can remain the place people work.

One lifecycle. From onboarding to retirement.

Device state and fleet operations

Oasis is RIoT Secure’s lifecycle management and integration layer, delivered as a Platform as a Service. It coordinates device onboarding, provisioning, configuration, active operation, updates, reassignment and decommissioning. Device state, software versions and fleet-wide operations remain part of one lifecycle.

For devices combining long-lived firmware with evolving application logic and local AI workloads, that management continues throughout their time in service. The REST API makes these lifecycle capabilities available inside the platform responsible for the customer experience.

Firmware and software updates

Oasis coordinates secure over-the-air firmware delivery through the RIoT Secure platform. Teams can manage software versions and update campaigns across geographically distributed devices, using the management console or the same REST API from their own operational tools.

Remote lifecycle operations matter when devices are difficult or costly to reach. Firmware maintenance remains part of the operating model as device applications evolve, including systems performing local processing, real-time decisions and AI workloads at the edge.

Oasis lifecycle diagram showing device deployment, provisioning, monitoring, over-the-air updates, decommissioning and reassignment.
Deployment, provisioning, monitoring, updates and reassignment · View full-size diagram

Your workflow. The same lifecycle engine.

Your existing front end

Integrate Oasis as a backend lifecycle service within your own IoT platform, operational portal or customer application. Visualisation, analytics and business logic stay with the systems that own them, while your front end calls the REST API for device management operations.

Oasis works with µTLS for protected communication, Fusion for hardware separation and Brawl for portable WebAssembly execution. This modular approach lets teams introduce lifecycle capabilities into an existing product and expand the integration over time.

The Oasis management console

The management console provides a ready-made interface for monitoring devices, viewing locations, grouping a fleet by deployment, function or lifecycle state, and managing firmware versions, update campaigns and device status. It can be useful for evaluation and day-to-day operations.

It is one interface to the same lifecycle engine. Every console operation is available through the REST API, so teams can provide those capabilities through their own customer-facing front end and operational workflows.

Keep your cloud protocols. Optimise the device link.

On the device link, µTLS carries data using RIoT Secure’s patented, size-optimised protocol. The integration gateway translates those compact transmissions into JSON or another data format required by the destination cloud service.

Your existing cloud-to-cloud integrations can keep their protocols and message formats. The constrained device link benefits from efficient µTLS transmission, while downstream platforms receive data in the form their existing systems expect. Adopting µTLS fits into those integrations through the gateway’s translation layer.

RIoT Secure integration diagram connecting embedded devices through µTLS and an integration gateway to a cloud dashboard or analytics platform, with MQTT, TCP, UDP and CoAP shown on the cloud side.
Integration gateway between µTLS device communication and existing cloud protocols · View full-size diagram
Historical Oasis management console view from the Stockholm Arlanda deployment, showing equipment locations alongside device status, power readings and firmware information.
Oasis management console from the Arlanda deployment · View full-size image

Lifecycle management. In daily operations.

SAS ground-handling operations

Oasis has been used in production at Stockholm Arlanda Airport with SAS ground-handling operations. Connected equipment supplied operational data from aircraft towing, pushback, baggage handling and other time-sensitive ground services, while Oasis managed the device fleet and firmware lifecycle.

Device events fed higher-level business systems for task assignment, status tracking and service records. Those records supported downstream billing, reporting and operational analytics, helping digitise work that had previously relied on manual or paper-based processes. The business workflows lived in the surrounding systems, supported by the device data and lifecycle infrastructure.

The console view shown here is an example from that deployment. Customers can expose the same management capabilities through their own front end using the REST API.

Keep your front end. Add lifecycle control.

Oasis provides complete lifecycle management through its REST API, with the management console available as an optional interface.