SPIEngine
Where the fleet is actually run. Provisioning, monitoring, configuration, updates and remote access for every device on the platform — the same way, whether that is two hundred units or fifty thousand.
One view of the whole estate.
- Updated
- 7,987
- Pending
- 286
- Rolled back
- 3
Console figures shown are illustrative
What SPIEngine covers.
Provisioning
Bring devices into service with identity and configuration applied from the start.
Registry
One authoritative record of every device, its variant, firmware, site and ownership.
Monitoring
Connectivity, health and last-seen state across the fleet, filtered by site or model.
Telemetry
Ingest, retain and route device data to dashboards, storage and downstream systems.
Commands
Send instructions to one device or a selected group, with delivery and result tracked.
Configuration
Versioned configuration applied per device, per group or per site.
OTA updates
Staged firmware rollout with cohorts, verification, pause and rollback.
Remote access
Brokered terminal access to a device without exposing it to the public network.
Alerts
Threshold and state-change alerting routed to the people who own the asset.
Lifecycle
From first provisioning through redeployment to decommissioning and audit.
APIs
REST and MQTT interfaces so the platform fits into systems you already run.
Multi-tenancy
Separated tenants, role-based access, and deployment options that respect data residency.
From first power-on to decommissioning.
A device is a long-lived asset. SPIEngine holds the record of what it is, what it runs, who touched it and what changed.
- 01
Provision
Identity and initial configuration applied before the device reaches the field.
- 02
Register
The device enters the registry with its model, site, owner and firmware recorded.
- 03
Operate
Telemetry, health and connectivity monitored continuously across the estate.
- 04
Configure
Versioned settings pushed per device, per group or per site, with results tracked.
- 05
Update
Firmware rolled out in cohorts, verified on arrival, paused or rolled back on failure.
- 06
Intervene
Remote commands and brokered terminal sessions when a device needs hands on it.
- 07
Retire
Decommissioning, credential revocation and a retained audit record.
The platform goes where the data has to stay.
Data ownership and residency are customer decisions. SPIEngine is built to be deployed under the constraints those decisions create, rather than requiring the customer to work around a single hosting model.
Managed cloud
SPIDEX-operated multi-tenant deployment, fastest route to a running fleet.
Sovereign cloud
Deployed in-country to meet data residency and regulatory requirements.
On-premise
Inside the customer network for environments that cannot route data outward.
Tenant separation and role-based access apply in all three models. Specific residency and hosting arrangements are confirmed per engagement.
See SPIEngine against your own fleet.
Tell us the device mix, the sites and the constraints. We will walk through how the estate would be provisioned, monitored and updated.