Skip to main content

Multi-Tenancy

Null Autos is multi-tenant: many organizations share the same platform while remaining fully isolated from one another. This page explains what a tenant is, how isolation works, and what that means for your data.

What is a tenant?​

A tenant is your organization on the platform. It is the top-level container that owns your users, emulators, snapshots, groups, and fleet definitions. Every resource belongs to exactly one tenant, and the platform enforces that boundary on every request.

Each tenant gets:

  • its own identity boundary (its own users, login, and optional federation to your identity provider),
  • its own isolated resources that no other tenant can see or touch, and
  • its own groups and permissions for organizing access internally.

How isolation is enforced​

Tenancy is enforced at multiple layers, not just in the UI:

  1. Identity: users authenticate within their tenant's identity boundary, and their identity carries the tenant they belong to.
  2. Authorization: every API call is checked against the platform's authorization service. A user can only ever see or act on resources their tenant owns and they have been granted access to.
  3. Data: resources are scoped to their tenant. Snapshots, for example, are tagged with their tenant so they are invisible to other tenants, and backup and restore operations are forced into the caller's tenant scope.
  4. Listing: when you list emulators, snapshots, or other resources, results are filtered to what you are allowed to see, so you never receive another tenant's objects.

Dedicated isolated environments​

Behind the scenes, the platform can deploy itself into dedicated, isolated environments per tenant. Each environment is a self-contained installation of the platform's services with its own boundary.

This gives platform operators a clean way to run dedicated deployments, for example a stricter isolation boundary for a regulated customer, without maintaining bespoke setups by hand. Each environment is kept in sync with the platform automatically, and its lifecycle (create, update, suspend, delete) is managed for you.

Tenant lifecycle​

  • Creation: a platform administrator provisions a tenant, which sets up its identity boundary and seeds its initial admin.
  • Onboarding: the tenant connects its VCS (GitLab) provider and sets up the integrations it needs. See the Onboarding guide.
  • Day-to-day: tenant admins manage users, groups, and access from the portal's account and admin sections.

What this means for you​

  • Your emulators, snapshots, logs, and source integrations are private to your organization.
  • Access within your tenant is yours to control through groups and permissions.
  • You can integrate your own identity provider so your team signs in with existing corporate credentials.