RAUA Platform is the ingest backend I architect and build as co-founder of RAUA Systems. Local Docker Compose E2E is verified: FastAPI worker raua-ingest, Timescale storage, per-device bcrypt API keys, msg_id dedup, and scripts/smoke_test.py automation.
Program scope and ownership
| Workstream | Owner | Where to read |
|---|---|---|
| Platform ingest (this repo) | Piotr (co-founder) | This page |
| Public site | Delegated lane; I stood up Cloudflare edge and routing | raua-systems.com |
| Field node firmware | Delegated workstream | Field node |
| v1 homelab backend | Predecessor | ZosteraGrids |
I delegate with separate repos and Linear backlog boundaries. Not every stream has an active non-Piotr owner yet.
| Local ingest signal | Implementation |
|---|---|
| Ingest paths | Direct and Hub-simulated |
| Storage | Timescale hypertable + PostgreSQL metadata |
| Verification | Automated E2E through smoke_test.py |
v1 stack and pilot backend
v1 ZosteraGrids paired homelab PostgreSQL, InfluxDB, and Grafana with bench field-node firmware. Per-device API keys, optional msg_id dedup, and ingest audit patterns held up under modem retries and homelab port collisions.
For an Indonesia pilot, the first success metric is archived time series an operator can query. A client dashboard can follow the data path.
Decision: Timescale + thin read API instead of Postgres + Influx + Grafana.
Constraints: a third time-series store and Grafana added ops surface without tightening the ingest contract. Homelab-as-production would not survive EU hosting or field LTE ingress.
Outcome: Influx and Grafana dropped. Metadata and measurements live in Postgres/Timescale. GET /devices/{id}/latest covers debug reads. Per-device credentials, msg_id dedup, and ingest_events audit trail ported from ZosteraGrids.
Sequencing: Docker Compose E2E and smoke tests on a laptop before Scaleway billing. The same raua-ingest image targets Serverless Container when cloud deploy happens.
Decision: local Docker Compose before Scaleway provisioning.
Hub route auth (POST /hub/ingest, topic devices/{id}/telemetry, X-Route-Secret) and direct device auth (POST /ingest, X-API-Key) were built before a real IoT Hub exists. Cloud deploy stays inside the tested ingest contract. Architecture, device auth, phased implementation, and the local runbook in the repo moved with the code across commits c8dadfa → 3f30222 → b49d940.
Device → FastAPI → Timescale
Two entry points on one worker share the same payload schema and write path.
Direct path: POST /ingest with X-API-Key. register_device.py creates a devices row and a one-time bcrypt-hashed key bound to device_id.
Hub-simulated path: POST /hub/ingest with X-Route-Secret and X-Topic matching devices/{id}/telemetry. fake_device.py --hub exercises the route locally. Production IoT Hub REST ingress is documented but not live.
Both paths validate the payload, check ingest_idempotency for duplicate msg_id, append ingest_events, and write a batch row to the measurements hypertable. sites seed Copenhagen bench and Indonesia pilot pond context.
Auth, idempotency, and read API
Device identity: device_id is provisioned in flash and stays stable across modem changes. API keys are bcrypt-hashed in devices.secret_hash. Plaintext is shown once at registration.
Idempotency: duplicate (device_id, msg_id) returns without a second hypertable write. ingest_events records accepted, rejected, and duplicate outcomes for audit.
Read path: GET /devices/{id}/latest returns the most recent accepted batch — enough for pilot ops and firmware debug without Grafana in v1.
Explicit v1 non-goals: Grafana, Influx, homelab-as-production, client dashboard.
Verified today and cloud roadmap
Verified locally
- Docker Compose E2E across FastAPI, Timescale migrations, device registration, simulation, and smoke tests.
- Direct and Hub-simulated ingest paths with topic binding.
Roadmap
- Scaleway Serverless SQL and Container provisioning.
- IoT Hub REST ingress and
ingest.raua-systems.comDNS. - Nordic LTE firmware ingest client in the separate firmware track.
The public site at raua-systems.com is top-of-funnel only: Cloudflare Pages, verified email capture, no device data path. Engineering ops scaffolding — GitHub org, Linear, Cloudflare routing — keeps marketing and ingest code in separate streams.