Licensed to be used in conjunction with basebox, only.
// installation
Responsibilities
Applies to
Product: Server (and, for comparison, Cloud) · Audience: Platform Operator · Administrator · Security reviewer · Procurement
Who does what depends on the operating model, not on where the server stands. This page is the single canonical place for that split; the compliance view under Security & Compliance → Shared responsibility refers back here.
The two operating models for basebox Server
- Self-managed Server
- The customer is responsible for infrastructure and operation after receiving the software. basebox provides the software, updates, documentation and support.
- Installation / operation by basebox
- If separately commissioned, basebox installs and/or operates the system using PAM/VPN or another agreed access path. The scope is defined per project.
Purchasing the software does not include operating the infrastructure
A basebox Server licence is a software licence. Infrastructure operation by basebox is a separate commission. Do not assume it is included.
Shared-responsibility table
| Area | Self-managed Server | basebox-managed / commissioned Server | basebox Cloud (for comparison) |
|---|---|---|---|
| Physical hardware | Customer / hardware partner | Customer / hardware partner | basebox |
| Data center | Customer or housing provider | Depends on hosting model (customer DC or basebox DC) | basebox |
| Operating system | Customer | basebox, if in scope | basebox |
| NVIDIA drivers | Customer | basebox, if in scope | basebox |
| Kubernetes | Customer | basebox, if in scope | basebox |
| basebox installation | Customer | basebox | basebox |
| Service models | Customer | Based on project scope | basebox |
| Inference | Customer | Based on project scope | basebox |
| Network | Customer | Shared (customer network, basebox access path) | basebox platform; customer connectivity |
| Ongoing operation | Customer | basebox, if contracted | basebox |
| Application administration (users, models, apps, connectors) | Customer | Customer | Customer |
| Application data (documents, chats, knowledge bases) | Customer | Customer | Customer |
Reading the table
- "Customer" may be the customer's own IT or a third party the customer commissions.
- "basebox, if in scope" means the item can be part of a basebox operations commission but is not automatically included.
- Application administration is always the customer's, in every model. basebox operating the infrastructure does not make basebox the administrator of your users, apps or data.
- Hosting at basebox changes only the data center row. A customer server hosted at basebox remains Server; everything else in the Server columns still applies.
Access for basebox-managed operation
Where basebox is commissioned to install or operate, access is provided through a controlled, agreed path – typically privileged access management (PAM) and/or a VPN. What is logged, who approves, and how access is revoked are documented under Security & Compliance → Remote maintenance.