Licensed to be used in conjunction with basebox, only.
// installation
basebox Cloud
Applies to
Product: Cloud · Audience: Administrator · IT · Security reviewer
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 dedicated customer server physically located at basebox is not Cloud but basebox Server with the hosting option basebox data center – see Hosting options. And the Demo is not a Cloud product: statements about the Demo infrastructure apply to the Demo only.
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 | ✔ | |
| Availability of the environment | ✔ | |
| 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