Licensed to be used in conjunction with basebox, only.
// installation
Operate
Applies to
Product: Cloud · Server · Audience: Platform Operator · Administrator
This section answers one question: I have this infrastructure – how do I install and operate basebox on it correctly?
It is written for Platform Operators and DevOps. Which hardware you need for how many users and models is summarised in Sizing. API tutorials are under Develop → API.
Start here
- Understand the architecture – basebox platform, service models and inference are three separate layers with very different resource needs.
- Deployment models – Cloud and Server, the Cloud transition phase until November 2026, and why a customer server hosted at basebox is still Server.
- basebox components – the services an installation consists of and how they talk to each other.
- Responsibilities – who does what in self-managed vs. basebox-operated setups.
Then choose your product.
basebox Cloud
basebox operates the infrastructure; you administer the application. The Cloud part of this section is for your IT: what your environment contains, how users and your systems reach it and how you go live: basebox Cloud (operated by basebox).
basebox Server
A server for your organisation alone – at your site or at basebox, operated by you or by basebox. The Server part is the main part of this section:
| Section | Content |
|---|---|
| Plan the server | Server architecture & topologies, hardware, hosting, operating and installation-path decisions, Sizing, Reference configurations |
| Install the server | Path A: the end-to-end path in ten steps from an empty server to a validated installation · Path B: Existing cluster · Local quick start |
| Models & inference | Inference architecture, backends, configuration, tested and recommended models, benchmarks |
| Operate the server | Monitoring, logging, backup, updates, scaling, troubleshooting |
| Advanced architectures | Multi-GPU, dedicated service GPU, multiple inference instances, multi-node |
| Reference | Helm chart and services, using Helm charts, Keycloak LDAP |
Three things to know before anything else
basebox itself needs little GPU. A server's GPUs serve the service models (RAG, OCR, speech-to-text) and inference (the language model). A sentence like "basebox needs two H200s" describes inference, not the platform.
A server at basebox is Server, not Cloud. Hardware source, location and operation are properties of a server, not products. This documentation describes every server deployment along exactly these dimensions.
Buying the software does not include operations. Who operates the server – you or basebox – is a separate agreement. The table: Responsibilities.
Related areas
- Security properties per deployment model: Security & Compliance
- Versions and changes: Develop → Getting started & reference
- Entry for decision makers without the technology: Start with basebox Server · Start with basebox Cloud
Next step: Understand the architecture · Sizing