IoT dashboards that operations teams actually use.
Real-time visibility for sensors, gateways and edge devices — with alerting, historical trends, and per-site rollups. Built for ops teams, not just data teams.
From device to dashboard
Whether your sensors speak MQTT, HTTP webhooks, Modbus over TCP, or a vendor-specific cloud, we'll pull them into Surfsonix and put them in front of the people who need them — with the right escalation when something's off.
- Multi-protocol ingest
MQTT, HTTPS, webhooks, Modbus/TCP, vendor cloud bridges. Add your own.
- Historian-grade storage
Long-retention time series with downsampling — months of data, fast queries.
- Alerting that escalates
Email, SMS, Slack, webhook escalations. Snooze, ack, on-call rotations.
- Per-site rollups
Brand → region → site → device. Aggregated KPIs at every level.
- Custom widgets
Pre-built widgets for common KPIs, plus a low-code builder for one-off views.
- Public read-only views
Share a status dashboard with vendors, contractors, or customers.
What you can actually watch
One dashboard, every reading. Sensors, gateways and edge devices all report into the same place, so an ops team isn't switching between five vendor apps to see the state of a site.
Room and zone occupancy, footfall counters, desk and parking sensors — rolled up by floor, building or site.
Cold-chain and server-room temperature, humidity, CO2 and particulate readings, with per-zone comfort bands.
Circuit-level meters, submeters and UPS status — usage trends and load anomalies by site or panel.
Uptime, latency, signal strength and packet loss for gateways, APs and edge controllers — not just the sensors behind them.
HVAC units, refrigeration, pumps and other mechanical assets reporting run-state, faults and maintenance flags.
Leak detection, door/contact sensors and safety triggers, surfaced the moment they fire, not on the next walk-through.
Know the moment something drifts
Thresholds are set per device and per site, not as one global rule — because a loading-dock door sensor and a walk-in freezer don't share the same tolerance for "normal".
Static limits, time-of-day bands, or rate-of-change rules — configured per sensor type and per site, not copy-pasted across the whole estate.
Surfsonix raises the alert the moment a reading crosses the line — not on the next scheduled report or nightly batch.
Email, SMS, Slack or a webhook into your own systems. An unacknowledged alert steps up to the next person or the on-call rotation.
Every alert keeps an audit trail — who saw it, when, and what they did — so nothing gets lost between shifts.
Trends you can actually query
A dashboard that only shows "right now" can't tell you if a problem is new or if it's been getting worse for months. Surfsonix keeps the history to answer that.
Raw readings plus downsampled rollups, so you can zoom from a five-minute spike to a year-over-year trend without slow queries.
Compare this month against last, or one site against the regional average, from the same view.
Pull raw or aggregated data out for BI tools, audits or your own reporting — no copying numbers off a screen.
Configure how long each data type is kept, aligned to your internal retention policy or regulatory requirement.
Common questions
Usually, yes. We support MQTT, HTTPS webhooks, Modbus/TCP and a number of vendor cloud bridges out of the box, and we've added custom ingest paths for one-off protocols before. Send us a sample payload or the vendor's API docs and we'll tell you honestly whether it's a quick add or a bigger piece of work.
Thresholds can include debounce windows and rate-of-change rules instead of a single hard line, so a sensor that briefly crosses a limit and recovers doesn't page anyone. You control the sensitivity per device — tighter for a freezer, looser for a lobby thermostat.
Yes. Public or scoped read-only views can be shared for a single site, a single device group, or a status page, without giving out login access to the rest of your estate.
Gateway and device connectivity is monitored the same way sensor readings are — a loss of heartbeat from a gateway raises its own alert, separate from and in addition to whatever it was reporting.
Surfsonix is typically run as a hosted service, so there's no infrastructure for your team to maintain. If your environment requires an on-premise or private deployment, that's something we can scope on a case-by-case basis.
It depends on how many device types and protocols are involved, but a first working dashboard against a real data feed is typically a matter of days once we have a sample payload or API access — not a multi-month integration project.
Got devices already streaming somewhere?
Send us a sample payload (or your vendor docs) and we'll have your first dashboard live in days, not months.