Skip to content

// installation

Customer environment

Applies to

Product: Cloud · Audience: Administrator · IT

What a customer environment in basebox Cloud consists of, how it is provisioned and what an administrator can change and what not. In short: you receive a fully operated basebox organisation with everything the application needs – and you shape it through the administration.

What your environment contains

Component What it is Who manages it
Address <your-organisation>.basebox.ai; the subdomain is also the X-Realm for the API Assigned by basebox; not changeable
Organisation Name, logo, system prompt, settings, limits You
Identity A Keycloak realm for your organisation; local accounts via invitation, optionally LDAP federation or SSO You (accounts, roles, groups); basebox (Keycloak configuration on request)
Platform services Frontend, AISRV, storesrv, databases, audit log basebox
Service models RAG, document extraction, OCR, speech-to-text basebox
Models The language models provided by basebox; you choose the default and per app basebox provides; you choose
Connectors The connector services provided by basebox (calculator, web search, e-mail, more by arrangement) basebox provides; you configure and enable
API OpenAI-compatible and REST API at https://aims.basebox.ai, with X-Realm = your subdomain; API keys You
Data Users, apps, knowledge bases, chats, audit log You – as controller

Provisioning

  1. Contract and master data. basebox receives organisation name, desired subdomain and the person for the first administrator account.
  2. Provisioning by basebox. Environment, realm and organisation are created; the first administrator account is set up.
  3. Handover. The named person receives credentials and signs in.
  4. Setup by you. Organisation, model, users, groups, apps, connectors, policies – order under Start with basebox Cloud.
  5. Go-live following the checklist.

What you can change

Everything in the Administration:

What you cannot change

  • Subdomain and address – fixed.
  • Infrastructure – data center, Kubernetes, storage, platform network.
  • The list of provided models beyond what basebox offers – request an additional model from basebox.
  • Keycloak configuration such as LDAP federation or SSO brokering – set up by basebox on your request (LDAP integration, OIDC / single sign-on).
  • Connector workloads – additional or custom MCP servers are connected by basebox in coordination with you (Connect an MCP server).
  • Versions and update timing – basebox keeps the environment current; changes are in the Changelog.
  • Inference parameters at server level (context size, output limit) – model properties set by basebox; per app you control thinking effort and temperature.

Where your data lives

In your isolated environment on basebox's own server in the Noris data center in Munich; the language model also runs there. Other customer organisations have no access. Only what you deliberately allow leaves the environment: web search queries (without user identity) and connector access to your own systems with the respective person's credentials. The chat history is stored by the user's browser. Details: Infrastructure · Data flows · Storage.

Several organisations

If your company needs separate areas – e.g. per subsidiary – these are separate organisations with their own subdomain, own users and own limits. Upload and usage limits can be set per organisation. Arrange this with basebox.

Frequently asked questions

Can I move my environment to basebox Server later? The application is the same; a switch is a contractual and migration question – contact sales@basebox.ai.

Can I see which version is running? Yes, under user menu → "About": version, active model, context size, realm.

Can I get a second test environment? For tests without real data there is the Demo. A separate test organisation in the Cloud is a contractual question.

Next step: Network connectivity