Limits#
Cloud Hosted
Limit |
Free |
|---|---|
Registered devices [1] |
3 |
Active batches |
5 |
Active taps |
2 |
Active vessels in storage |
5 |
How often a device can send readings |
1 reading / 15 min |
Stored gravity readings (including the temperature sent with them) |
100,000 readings |
How limits work#
BrewGraph checks each limit when you create a device, batch, tap, or storage vessel. The count applies to your account, whichever screen you use.
The create button shows your current count and becomes unavailable when you reach a limit, for example “Device limit reached (3/3)”. To make room, remove or archive something you no longer use.
The effective reporting interval follows the account’s plan. On the Free plan, a device can send one reading every 15 minutes; paid plans use their own interval rather than the Free interval. A reading refused for arriving too soon appears in Settings > Ingestion log. Set the device to report no more often than the interval for the account.
What’s different from self-hosted#
The core device, batch, tap, and vessel workflows are described in Devices, Batches, Taps, and Storage Vessels. The hosted version adds:
Managed hosting — no server to run, automatic backups and uptime
A batch summary report and downloads of your brewing data and full backup
Data lifecycle and portability#
The reading limit counts stored gravity readings; temperature sent with a gravity reading is part of that reading. When you reach the limit, new readings stop being accepted until you remove eligible old data. BrewGraph does not silently remove current readings.
The batch summary report, brewing-data export, and full backup download are available on every beta account in Settings > Data & Privacy. You can also download your data before closing your account. User-deleted data and closed accounts have a 30-day recovery window and are then deleted from BrewGraph and from backups, which takes up to 60 days in total.