GET STARTED
Core concepts
Understand tenants, suites, resources, events and platform-wide governance.
Last updated July 17, 2026 · 6 min read#Tenants and isolation
A tenant is the primary security, data and entitlement boundary. Resource access is evaluated against tenant context on every authenticated request; client-supplied tenant identifiers are never trusted as authorization.
#Resources and identifiers
Platform objects use stable identifiers, timestamps and version metadata. Collection endpoints use cursor pagination so large, changing result sets remain consistent.
| Concept | Purpose |
|---|---|
| Resource ID | Stable identity for an object |
| Request ID | Trace a call across gateway and services |
| Idempotency key | Safely retry supported mutations |
| Event ID | Deduplicate and replay domain facts |
#Events, not coupling
Applications publish immutable domain facts to the event bus. Consumers build projections and automations without reaching into another service’s database.
Was this page helpful?