ZosteraGrids is v1 of the RAUA field-monitoring stack — a homelab backend for local E2E telemetry, before RAUA Platform. The successor design is Timescale and a thin read API aimed at a later cloud pilot. It replaces Influx and Grafana.
It is a two-sided system: constrained field-node firmware on the bench (see ZosteraGrids field node) and this backend, where telemetry lands, is validated, and becomes visible on a home network without opening large holes in the LAN.
What is built today
- Docker Compose stack: API gateway (
POST /ingest,GET /health), internal PostgreSQL and InfluxDB, Grafana on the host edge - Per-device API keys and optional
msg_ididempotency in gateway ingest — duplicate(device_id, msg_id)returns without a second Influx write - Narrow surfaces: devices speak one API shape; databases stay inside the compose boundary
- Tailscale/LAN/UFW deployment model documented — no casual exposure of DB ports
- Runnable homelab E2E: curl ingest examples, LAN device debugging, co-located port collision notes for real multi-stack hosts
This is homelab infrastructure, not production cloud ingest at scale.
Surfaces and threat model
The compose stack is deliberate: an API gateway fronts device traffic. PostgreSQL and InfluxDB stay internal. Grafana is for human dashboards. It does not replace the ingest contract. Docs name Tailscale, LAN CIDRs, and UFW-style patterns because the threat model is device credentials plus a home lab, not public cloud at scale.
Narrow surfaces: devices speak one API shape. Operators debug through Grafana and health checks. Databases stay unexposed even when that would have been convenient during development.
Idempotency and field messiness
Real devices lose power, retry, and jitter. The ingest path documents optional message ids so duplicate deliveries can be detected instead of writing the time series twice. That detail showed up after imagining a modem reconnecting at the worst moment.
Port collisions on a shared box
Homelab hosts accumulate compose stacks. The README is blunt about port collisions (Grafana on 3000 is a default that breaks the moment another project already claimed it). Operability includes what happens when this is not the only stack on the box.
How this pairs with the firmware
Backend and node are separate repositories with a shared contract: batched uplinks, power-aware duty cycles on the device, and honest stubs where cellular time sync or HTTP paths are still evolving. The backend README ingest examples are the contract the firmware can test against without flashing new hardware for every experiment.
What carried forward to v2
Per-device API keys, msg_id idempotency, and ingest audit patterns ported directly into RAUA Platform. What did not carry: Influx, Grafana, and homelab-as-production.