SURDS Platform

One connected view of your infrastructure.

Bring devices, equipment and existing systems together. Build workflows around the information they generate.

Connect

  • SURDS ThermalMQTT
  • Radar Pod802.15.4
  • Energy metersModbus
  • Chillers · AHUsBACnet
  • POS · bookingsREST
  • Weather · tarifffeeds

Understand

One site graph

  1. Normalise units, clocks, names°C · kW · ppl
  2. Place every point in the buildingsite › room › asset
  3. Keep history and eventstime-series
  4. Check who may read and actscopes

readings / s0

Build

  • Pythonon hub
  • JS functioncloud
  • Containerany image
  • AI agenttools
  • Node-REDflow

Operate

  • AC off via Pulse
  • WhatsApp · email
  • BMS set point
  • Ticket · on-call
  • Report · ESG

01 · Connect different devices

Bring your physical systems together.

Connect sensors, equipment and existing systems through one common foundation. A SURDS sensor takes eight clicks.

Technical details: devices and integrations

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.

WebSerialesptool-jsMQTT802.15.4ModbusBACnetOPC UARESTCSV

02 · Communicate reliably

Your infrastructure shouldn't go blind when the internet goes down.

Supported devices and local operations stay connected through a distributed network and a hub on site.

Technical details: SURDS Mesh and the hub

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.

Thread802.15.4store-and-forwardlocal rulesencrypted links

03 · Understand infrastructure

See your physical infrastructure as one connected system.

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.
  1. SITESURDS DC-1
  2. FLOORGround · Hall A
  3. ROOMRow 4 · cold aisle
  4. EQUIPMENTRack A4-07
  5. SENSORSURDS Thermal 55° · inlet °C · current A
Meeting Room 01occupancy 3
24.1 °C
AC on
Electrical Roomcurrent 41 A
power 9.6 kW
UPS normal
DC Rack 04inlet 27.4 °C
current 12 A
above normal
Technical details: the site graph and digital representations

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.

site › floor › room › asset › sensortime-serieseventsscopes

04 · Build specific applications

Don't rebuild your platform every time your requirements change.

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

Pick a workflow. Press run.

Same data, different applications. Switch the runner to see the code behind it.

empty-room-ac-off · Halden · Floor 12ready

          
Occupancy—
Choose a workflow and press Run.

For developers · subscribe, decide, emit

Build workflows with the tools you already use.

Connect a supported runtime to the same physical data. No SDK to adopt: a scoped token, a stream and two calls.

  1. 01
    SubscribeAsk for a slice of the graph: room("1204").occupancy, assets(type="fridge").temp, or a schedule.
  2. 02
    DecideYour code, your language, your libraries. Models, thresholds, LLM calls, anything.
  3. 03
    Emitevent() to tell people, act() to change something. Every act carries a reason and lands in the audit log.

      

05 · Operate physical systems

From knowing what is happening to doing something about it.

Connect information to authorised actions, wherever the hardware and integrations support it.

  1. SIGNAL

    Meeting Room 2 has been empty for 15 minutes.

  2. DECISION

    The rule checks the AC: still on.

  3. ACTION

    SURDS Pulse sends the off code to the AC's IR receiver.

  4. RECORDED

    Logged with the reading, the reason and the code version.

Scoped
A workflow reads and changes only what its manifest lists, per site.
Explained
Every action is logged with the reading that caused it and the code version.
Shadow mode
Run a new workflow beside the old one and compare before it touches anything.
Versioned
Roll a workflow out room by room, roll it back in one click.

What's real today

We'd rather show you clearly than claim too much.

AvailableBrowser onboarding in eight clicks, the site graph, history and scopes, rules on SURDS sensors.
PilotSURDS Mesh and offline operation, encrypted links, Bluetooth setup, Matter and Google Home integrations.
In developmentThe visual workflow builder, packages and runners, Modbus / BACnet / OPC UA connectors, 3D layouts without LiDAR.

Readings, workflow runs and sites shown on this page are demonstrations, not deployment data.

Deployment

On the hub, in the cloud, or on your own servers.

Edge

The hub in the building

Safety and comfort rules run next to the sensors, so they keep working when the internet doesn't.

Cloud

SURDS cloud

Heavier work across sites: forecasting, reports, AI agents that read a month of history before they answer.

Yours

Your infrastructure

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.

Start with one room. Build the next thing yourself.

We set up the hub and the first workflows with you in the pilot. After that, your team adds the next one.