I have always liked the idea of telemetry. Devices out in the world, quietly posting readings, and a dashboard somewhere showing what is happening right now. Temperature, pressure, vibration. Simple numbers, but they tell you a lot.

The problem was that every real telemetry stack I looked at wanted a server farm. A message broker, a time-series database, a cluster, a cloud account. I did not have any of that. I had a laptop and an evening.

So I built a small one. A local telemetry ingestion system. Devices POST sensor readings to a REST API, the readings land in SQLite, and a dashboard shows live stats, per-sensor trends, and recent readings. It is the kind of data-logging tool used in industrial operations support, just shrunk down to something one person can run.

What it does

The API takes a reading with a sensor id, a value, a unit, and a timestamp, validates it, and stores it. Bad input gets rejected with a 422, so junk never reaches the database.

The dashboard is served by the API itself.…