IoTWeb AppSvelteMicroservices

Senify

2026-11-17

What it is

Senify is a self-hosted platform for monitoring IoT sensors, built around a fleet of ESP32/ESP8266 microcontrollers that report readings like temperature, humidity, and GPS position back over MQTT. It started out of a very concrete need: keeping an eye on things like cold-room temperatures, where a single sensor dropping offline unnoticed is the whole point of the system.

New devices announce themselves over UPnP discovery the moment they connect, listing whatever sensor hardware is wired to them, and get their measurement config (what to measure, how often, under what name) pushed back over MQTT without anyone touching a config file. From there, every device and sensor shows up live on a dashboard with its own status — online, offline, no data, or erroring — so a dead sensor is a glance away instead of something you discover when it’s too late.

Tech stack

The platform is split into a handful of small services instead of one monolith, so a flaky MQTT connection or a long-running backup can’t take the dashboard down with it.

Frontend: SvelteKit with TypeScript, using layerchart/Chart.js for live sensor graphs and Socket.IO for pushing new readings to the browser as they arrive..

Broker service: an aedes-based MQTT broker handling device connections, UPnP discovery, and config push, talking to the rest of the system over gRPC.

WebSocket service: a dedicated real-time layer that fans sensor data out to connected dashboards over Socket.IO, decoupled from the broker so ingest and live updates can scale independently.

Backup service: handles scheduled database backups (node-cron) and ships them to S3-compatible storage.

Shared layer: a common shared-utils package (Prisma schema, protobuf definitions, utility code) is pulled into every service as a submodule, so the data model and gRPC contracts stay in sync across the whole platform instead of drifting between repos.

Data & ops: MySQL via Prisma across all services, Protobuf/gRPC for inter-service calls, and each service shipped as its own Docker container behind Coolify, wired together on a Docker bridge network with static IPs.