Licensed to be used in conjunction with basebox, only.
// installation
basebox Cloud (operated by basebox)
Applies to
Product: Cloud · Audience: Administrator · IT · Security reviewer
This section is for the customer's IT: network connectivity, integration with your systems and go-live. basebox operates the platform itself.
basebox Cloud runs on basebox-owned infrastructure in the Noris data center. Every customer receives an isolated environment. basebox operates the platform, the service models and inference; you administer the application – users, apps, models, connectors, policies. There is no customer-owned physical server, nothing to install and no Kubernetes knowledge you need.
What Cloud is – and what it is not
| basebox Cloud | |
|---|---|
| Infrastructure | Owned by basebox, located in the Noris data center |
| Isolation | One isolated environment per customer organisation |
| Operation, updates, platform backups | basebox |
| Application administration | You |
| Real, sensitive data | Yes – production environment |
| Customer-owned server | No |
A server for one customer alone, physically located at basebox, is not Cloud but basebox Server with the hosting option basebox data center – see Hosting options. This description applies 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).
This section
| Page | What you find there |
|---|---|
| Architecture | How the Cloud is built: basebox-owned infrastructure, isolation per customer, where inference and service models run |
| Customer environment | What your environment consists of, how it is provisioned, what you can change and what you cannot |
| Network connectivity | How users reach the Cloud, how the Cloud reaches your systems, egress aspects for connectors |
| Enterprise integration | Identity, mail, SIEM, connectors from the Cloud – what differs from Server |
| Go-live | Checklist for going into production |
Who does what
| Area | basebox | Your organisation |
|---|---|---|
| Data center, hardware, platform network | ✔ | |
| Operating system, Kubernetes, basebox installation | ✔ | |
| Service models (RAG, OCR, STT) and inference | ✔ | |
| Updates, monitoring, platform backups | ✔ | |
| Monitoring of the environment; basebox handles incidents during support hours | ✔ | |
| Users, groups, roles | ✔ | |
| Model selection, apps, knowledge bases | ✔ | |
| Connector enablement, policies, audit | ✔ | |
| Connecting your systems (firewall on your side) | Configuration of the Cloud side | Approvals in your network |
| Application data (documents, chats, knowledge bases) | ✔ – controller |
In full: Responsibilities.
How you start
- Contract → basebox provisions the environment at
<your-organisation>.basebox.aiand creates the first administrator. - First login, set up the organisation, invite users – step by step under Start with basebox Cloud.
- Go through the go-live checklist before production.
For data protection and security
The Cloud-specific statements – isolation, infrastructure, administrative access by basebox, backup – are collected under Security & Compliance → Cloud and Cloud security. What is the same in every environment (connectors, web search, audit): External services.
Next step: Architecture