IoT platform
Log9
Wireless sensors are cheap now; making sense of what they report is the hard part. Log9 takes a stream of readings off the plant floor and turns it into something a maintenance team can act on before anything stops.
The problem
Condition monitoring fails in the gap between the sensor and the decision. Readings arrive from gateways in whatever shape the hardware emits, land in a database nobody queries, and the first anyone hears of a failing bearing is when the line stops.
What a maintenance team needs is lead time: the same reading, in context, against last month's trend, with someone told automatically when it crosses a line.
What we built
- Device and gateway provisioning, grouped by site and asset
- High‑volume ingestion over MQTT and HTTP, tolerant of gateways that drop offline
- Time‑series storage sized for long retention rather than a rolling window
- Live dashboards alongside historical trend charts, so drift is visible
- Threshold and anomaly alerting by email and webhook
- Open API and CSV export — the data stays portable, with no lock‑in
Under the hood
What it runs on
Chosen for long support horizons and large talent pools, so Log9 stays maintainable by someone other than us. Documented, version controlled, and handed over without drama if it ever needs to move.
Visit log9.ioBuild
- Node.js
- TypeScript
Data
- PostgreSQL
- Time‑series
- Redis
Ingest
- MQTT
- HTTP API
- Webhooks
Run
- AWS
- Docker
- Linux
Your project next
Something like this in mind?
Tell us the problem rather than the spec. We will come back with an honest view of what it takes — including whether we are the right people for it.