Space Engine Edge + Cloud (hybrid, HA/DR)
Space Engine Edge runs in your building and Space Engine Cloud keeps a mirror copy of it. The building works offline, data syncs to the cloud whenever a link is available, and the cloud copy keeps your data and remote access if the building server goes down.
| Deployment model | hybrid deployment: Space Engine Edge in the building + Space Engine Cloud as its mirror replica |
|---|---|
| Synchronisation | store-and-forward replication from Edge to the cloud copy |
| Offline operation | full local operation in the building without internet access |
| Failover (HA/DR) | the cloud copy keeps data and remote access if the building server fails |
Works offline (on-premise)
Doors, permissions and event history keep working in the building without internet access, because Space Engine Edge holds the local database and API.
Syncs when it can (store-and-forward)
Changes are queued on Edge and sent to the cloud copy whenever a link is available, so nothing is lost during an outage.
Cloud as a safety net (failover, HA/DR)
If the building server goes down, Space Engine Cloud keeps your data and remote access to the system until Edge is back online.
How Space Engine Edge + Cloud (hybrid, HA/DR) works
Space Gate hubs and devices talk to Space Engine Edge in the building over the local network. Edge replicates its data to your instance in Space Engine Cloud, and your systems can use the REST API and WebSocket of Edge on site or of the cloud copy remotely.
One platform, several deployment models
Space Engine runs in these models: Cloud (shared SaaS), Cloud (managed private cloud) and Edge (on-premise: appliance or BYOI), which can be combined as Space Engine Edge + Cloud (hybrid, HA/DR). All of them use the same software, API and devices, so you can switch models without replacing devices and keep control of the infrastructure and security procedures on your side.
Specifications
| Deployment model | hybrid deployment: Space Engine Edge in the building + Space Engine Cloud as its mirror replica |
|---|---|
| On site | Space Engine Edge (on-premise): appliance or your own infrastructure (BYOI), local database and API |
| In the cloud | Space Engine Cloud (managed private cloud), a single-tenant replica of Edge |
| Synchronisation | store-and-forward replication from Edge to the cloud copy |
| Offline operation | full local operation in the building without internet access |
| Failover (HA/DR) | the cloud copy keeps data and remote access if the building server fails |
| Device communication | MQTT; about 30 MB per hub per month, mostly heartbeat |
| API and integration | REST API (HTTP/JSON), live events over WebSocket, HTTP webhooks |
| Typical customer | sites that must keep working offline and also need a cloud copy for remote access and recovery |
With Edge alone, all data stays only in the building. Edge + Cloud adds a mirror copy in Space Engine Cloud, so your data and remote access survive a failure of the building server.
The building keeps working on Edge. Changes are queued and sent to the cloud copy as soon as the link is back (store-and-forward).
Click “BUY IN SHOP” to open the product in the Space BMS shop. For larger orders and projects, call +48 533 909 533 or use the contact form.
In the “Downloads” tab. If a document you need is missing, we will send it on request.
Downloads
Datasheets and manuals in PDF format. If you need a document in another language, please contact us.
Technical documentation is available on request.
Questions about this product?
Call us on +48 533 909 533 or send us a message. We will match the solution to your building.