Licensed to be used in conjunction with basebox, only.
// security
Isolation
Applies to
Product: Cloud · Audience: Security / Compliance reviewer
How customer environments in basebox Cloud are isolated from one another: at the level of the application (organization, realm, address), identity, data and outbound connections. The aim of this page is that you can describe tenant separation in a vendor assessment – and know which details to additionally request from basebox.
What a customer environment is
Every customer organization receives an isolated environment on the platform operated by basebox, on shared servers in the data center of noris network AG in Munich-East (Infrastructure):
| Level | Separation | Effect |
|---|---|---|
| Address | Own subdomain <your-organization>.basebox.ai; the subdomain is also the API's X-Realm |
Requests are assigned to one organization from the first connection |
| Identity | Own Keycloak realm per organization: users, roles, groups, OIDC clients, LDAP federation or SSO brokering | An account exists in one realm only; tokens of one realm are not valid in another |
| Application | Own organization with its own apps, knowledge bases, settings, policies, audit log, limits; the chat history sits in the users' browsers | Administrators see and manage exclusively their organization |
| Connectors | Configuration and approval per organization; credentials per user; egress allowlist per connector | A connector reaches only the target systems configured for this organization |
| Platform services | Own virtual Kubernetes environment per organization with frontend, AISRV, storesrv and databases | The environments run on a shared server |
| Inference | On the Cloud's servers, operated by basebox | Compute and AI model are shared by default; every request is processed without permanent storage and stays logically separated. An AI model just for your organization is available on request; you will find the price in your personal offer |
Several divisions of a company (for example subsidiaries) are separate organizations with their own subdomain, own users and own limits (Customer environment).
What the separation achieves
- No user and no administrator of one organization can see data of another: the assignment via realm and
X-Realmapplies equally to the interface, GraphQL and OpenAI-compatible API. - Chat histories are private per user; even within an organization an administrator does not see them – except via the explicitly configured recording in the audit log, which is then shown to all users.
- Connector credentials are stored per user and loaded per request; there is no cross-organization service account.
- Web search queries go to the provider without user identity and without user IP; whether the query can be attributed to an organization depends on the provider contract, not on basebox.
What you should additionally request
For a complete assessment of tenant separation you need details this documentation does not substantiate and which basebox provides for your environment:
- Which network policies apply between the virtual environments.
- How the shared inference technically separates requests from different organizations.
- How backups are separated per customer (Backup).
Contact: datenschutz@basebox.ai.
Distinction from Server
Whoever needs separation at the hardware level – one customer per physical server – is right with basebox Server, also when hosted at basebox (Dedicated hardware). The Cloud isolates at the level of application, identity and data.
Next step: Infrastructure