The Cloud Endpoint
The endpoint you rent instead of run: hosted services or a small rented server, for readings readable from anywhere.
What it is
No computer at home stays on? Land the readings in the cloud: a hosted dashboard or broker service, or the same open stack on a few-dollar rented server. Every board in this store pushes plain webhook or MQTT — exactly what the hosted services accept — and switching later is one address on a setup page.
| What it is | A hosted landing spot for readings: a dashboard/broker service, or your own rented server |
|---|---|
| Two honest paths | A service (zero setup, their rules) or a small VPS running the open stack (a few dollars a month, your rules) |
| What the boards need | Nothing special: the same webhook or MQTT push, pointed at a different address |
| Ownership | Choose services with clean export; oat-ods is plain JSON, so the record can always move |
| Cost | Free tiers exist on the services; a small VPS rents for single-digit dollars a month |
How it works
Every board in this store pushes plain webhook or MQTT to one address. Point that address at a hosted service — Grafana Cloud, InfluxDB Cloud, ThingsBoard, Adafruit IO, and kin — and the dashboard exists before dinner, with nothing at your place to keep alive. Or take the middle path: a small rented server (a VPS) running the same open stack you would run at home, for a few dollars a month, under your rules.
The sovereignty story stays honest either way: the readings are plain JSON records end to end, nothing in the build is locked to any service, and moving — service to VPS to the shelf at home — is one address on a setup page. Choose a service the way you would choose a grain buyer: on the strength of the exit.
Questions folks ask
Can sensor readings go straight to a cloud service?
Yes. Every build in this store pushes plain webhook (HTTP POST) or MQTT, which is what hosted dashboards and brokers accept: Grafana Cloud, InfluxDB Cloud, ThingsBoard, Adafruit IO, and kin. Point the board's one address at the service and the readings land there instead of at home.
Cloud or local: which should I start with?
If a computer at your place already stays on, local-first is the simpler and cheaper habit: the record lives with you and works with the internet down. If nothing at home stays on — or you need the numbers readable from town — the cloud is the honest answer. Nothing about the sensors changes either way; moving is one address.
Do I lose ownership of my data in the cloud?
Not if you choose deliberately. Pick services with a clean export path, and remember the readings themselves are plain JSON records the whole way: nothing in this store's builds is locked to any service, so the moment a service stops suiting you, the same sensors push somewhere else.
What is the middle path between a service and a home server?
A small rented server (a VPS): a few dollars a month for a machine that is always on, running the same open stack you would run at home — your rules, no service lock-in, reachable from anywhere. It is the home server without the home.