The hub in the building
Safety and comfort rules run next to the sensors, so they keep working when the internet doesn't.
SURDS Platform
Bring devices, equipment and existing systems together. Build workflows around the information they generate.
Understand
readings / s0
01 · Connect different devices
Connect sensors, equipment and existing systems through one common foundation. A SURDS sensor takes eight clicks.
Available SURDS sensors onboard from the browser over USB (WebSerial and esptool-js): the page reads the board's identity, installs firmware, sends Wi-Fi and claims it to your account. Readings arrive over MQTT.
Pilot Setup over Bluetooth for sensors without a cable nearby.
In development Connectors for existing equipment and building systems: Modbus meters, BACnet chillers and AHUs, OPC UA, REST and webhooks, files.
02 · Communicate reliably
Supported devices and local operations stay connected through a distributed network and a hub on site.
Pilot SURDS Mesh runs on Thread (IEEE 802.15.4). Sensors relay for each other, and when a link drops the mesh routes through a neighbour that is still in range, within radio reach.
The gateway spools readings while its uplink is down and sends them when it returns. Thread links are encrypted with network keys.
The hub runs safety and comfort rules locally. Functions that need the cloud, such as cross-site reports, wait for the connection.
03 · Understand infrastructure
Know where every signal comes from, what it belongs to and how it relates to the rest of your site.
27.4 °CA temperature on its own is just a number.27.4 °C · Rack A4-07 inletTied to a rack in Row 4, it tells you who to call.Available Every reading lands on a place and a thing. Units and clocks are fixed on the way in, history and events are kept, and scopes decide who may read and act.
Pilot Operational models of assets, their relationships and live states, shown on floor plans and site maps.
In development 3D room layouts from ordinary photos, without LiDAR.
04 · Build specific applications
Build new applications on top of a foundation that is already connected.
Occupancy sensor → room empty 15 min → check AC state → send AC off
Rack temperature → threshold exceeded → raise alert → notify the operator
Cold room probe → outside 2–8 °C → alert with the reason → log for the audit
Try it · simulated data
Same data, different applications. Switch the runner to see the code behind it.
For developers · subscribe, decide, emit
Connect a supported runtime to the same physical data. No SDK to adopt: a scoped token, a stream and two calls.
room("1204").occupancy, assets(type="fridge").temp, or a schedule.event() to tell people, act() to change something. Every act carries a reason and lands in the audit log.05 · Operate physical systems
Connect information to authorised actions, wherever the hardware and integrations support it.
Meeting Room 2 has been empty for 15 minutes.
The rule checks the AC: still on.
SURDS Pulse sends the off code to the AC's IR receiver.
Logged with the reading, the reason and the code version.
What's real today
Readings, workflow runs and sites shown on this page are demonstrations, not deployment data.
Deployment
Safety and comfort rules run next to the sensors, so they keep working when the internet doesn't.
Heavier work across sites: forecasting, reports, AI agents that read a month of history before they answer.
Point a runner at your own Kubernetes or a laptop under a desk. It connects out to the platform; nothing has to be opened in.
One foundation. Many possibilities.
We set up the hub and the first workflows with you in the pilot. After that, your team adds the next one.