Skip to content
Free public beta until December 4, 2026: every course is open, no card needed. After that, the first chapter of each course stays free and full access is a one-time $39 ($19 for up to 100 founding members chosen for helpful feedback). Your progress is kept. How the beta works

tenant

One customer whose devices and data share a system with other customers' but must stay separate.

A tenant is an isolated customer or organisation in a multi-tenant system; every device, topic, record and user belongs to exactly one tenant, and the server enforces that boundary.

Examples

  • Growers acme, hilltop and riverside share one system, so GET /devices/gh-a1/latest from a hilltop user only finds gh-a1 if its tenant_id is hilltop.

See also

role-based access control access control list topic tree
Read the full section →