Platform
ScaiWave ScaiGrid ScaiCore ScaiBot ScaiDrive ScaiKey Models Tools & Services
Solutions
Organisations Developers Internet Service Providers Managed Service Providers AI-in-a-Box
Resources
Support Documentation Blog Downloads
Company
About Research Careers Investment Opportunities Contact
Log in

Tenants and realms

Proxility uses the same two-level structure as the rest of the ScaiLabs platform, so an organisation's shape carries across products.

Tenant#

Your organisation is a tenant. It is the hard boundary: identities, services, policy and logs never cross it. The tenant short name appears in every identity and every service name, which is what keeps two customers on shared edge from colliding.

Realm#

Inside a tenant you create realms, one per team, product or environment — prod, staging, partner-integrations. A realm owns:

  • its connectors and their identities,
  • its published services,
  • its policy rules,
  • its slice of the decision log.

Realms are the delegation unit. Grant a team roles on their realm and they operate independently without being able to touch another realm's policy.

Names#

text
1
2
identity   prox://<tenant>/<realm>/<name>
service    <service>.<realm>.<tenant>         → resolves as <service>.<realm>.<tenant>.prox

The prefix is not decoration. payments.prod.acme is unambiguous across the whole platform, which means a rule, a log line and a support conversation all refer to the same thing without further context.

Crossing realms#

Within a tenant, one realm may reach another's service — but only with an explicit rule naming both realms. Wildcards do not span realms (see Policy). This makes cross-realm access a visible, auditable decision rather than an emergent property of a selector.

Crossing tenants is different: it requires both tenants to agree, and is modelled as partner access. See Partner access.

Roles#

Role Can
realm:viewer Read services, policy and the decision log
realm:operator Enrol and retire connectors, publish services
realm:policy Change policy rules
realm:admin All of the above, plus grant roles within the realm
tenant:admin Create and delete realms, grant tenant-wide roles

Separating realm:operator from realm:policy is worth doing: the person who installs a connector does not automatically get to decide what it may reach.

Updated 2026-11-08 18:08:05 View source (.md) rev 2