Skip to content
Copyright © 2022-2026 basebox GmbH, all rights reserved.
Licensed to be used in conjunction with basebox, only.

// installation

Architecture

Applies to

Product: Cloud · Audience: Administrator · IT · Security reviewer

How basebox Cloud is built: basebox-owned infrastructure in the Noris data center, one isolated environment per customer, the three layers platform, service models and inference – and what of that is shared or dedicated. The application is the same as on basebox Server; the difference is who owns the infrastructure and who operates it. This page describes the Cloud from the Cloud launch onwards.

Transition phase until November 2026

Accounts created before the Cloud launch in November 2026 run, until they are moved, in a shared environment at Hetzner in Nuremberg with AI models from Google Vertex in Frankfurt – logically separated from each other, with shared user management. basebox moves these accounts to the Cloud; no new registration is needed. basebox is a data processor in the transition phase as well. Health data and other special categories under Art. 9 GDPR are best processed only after the move. Details: basebox Cloud (transition phase until November 2026).

The picture

flowchart TB
  subgraph DC["Noris data center · basebox-owned infrastructure · operated by basebox"]
    direction TB
    subgraph A["Customer A – isolated environment"]
      A1["basebox platform<br/>frontend · AISRV · Keycloak realm · databases"]
      A2["Service models<br/>RAG · OCR · STT"]
    end
    subgraph B["Customer B – isolated environment"]
      B1["basebox platform"]
      B2["Service models"]
    end
    INF["Inference · language models<br/>operated by basebox"]
    A1 --> A2 --> INF
    B1 --> B2 --> INF
  end
  UA["Users A"] -->|HTTPS| A1
  UB["Users B"] -->|HTTPS| B1
  A1 -.->|"connectors · mail · SSO<br/>only if set up"| SA["Systems of customer A"]
  style DC fill:#f4f2ee,stroke:#524e47,color:#1d1e1c
  style A fill:#dcefe2,stroke:#3a7a49,color:#1d1e1c
  style B fill:#dcefe2,stroke:#3a7a49,color:#1d1e1c
  style INF fill:#dbeafe,stroke:#1e40af,color:#1d1e1c

The three layers in the Cloud

Layer What belongs to it In the Cloud
basebox platform Frontend, AISRV (chat, apps, APIs, MCP gateway, audit), storesrv, Keycloak, PostgreSQL Isolated per customer: own organisation under its own subdomain, own Keycloak realm, own data storage
Service models Embeddings, RAG processing, document extraction, OCR, speech-to-text Operated by basebox; your documents and embeddings live in your environment
Inference The language models Operated by basebox on basebox infrastructure; AISRV talks to it via the OpenAI-compatible API

What the layers are and why they belong apart: Understand the architecture.

Shared or dedicated?

The question security reviewers ask first. The state of affairs:

  • Your organisation, your data, your realm are assigned to your environment. Other customer organisations have no access to them.
  • The physical infrastructure – servers, network, storage backend – is owned by basebox and operated by basebox for the Cloud; isolation happens at platform level, not through separate physical servers. Whoever needs a physical server for their organisation alone chooses basebox Server.
  • Inference is operated by basebox. The customer environments share the AI model on the server. A model for your organisation alone is possible; you will find the price in your personal quote.

The security properties of this split – tenant separation, administrative access by basebox, encryption, backup – are under Cloud security.

What is the same as on Server

  • The application: same interface, same features, same APIs, same permission model.
  • The handling of connectors: per-user credentials, enablement per app, egress allowlist, tool results as data.
  • Web search: off by default, consent before the first search, query without user identity, audit metadata without query text.
  • The audit log with configurable retention and detail level.

What differs from Server

basebox Cloud basebox Server
Who operates platform, service models, inference basebox You – or basebox if commissioned
Model list Provided by basebox Connected by the Platform Operator
Connector workloads Provided by basebox Platform Operator via Helm
Keycloak configuration (LDAP, SSO) basebox on your request Platform Operator
Network direction to your systems From the Noris data center into your network Within your network
Fully air-gapped operation Not possible Possible
Infrastructure and application logs At basebox With you

Next step: Customer environment