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

// installation

Hosting options

Applies to

Product: Server · Audience: Platform Operator · IT · Security reviewer

Where the physical server stands: in the customer's data center or hosted in the basebox data center. Hosting at basebox does not turn Server into Cloud – the server remains dedicated to one organisation, and the Server documentation applies unchanged. What changes is exactly one row in the responsibilities table: the data center.

The two options

Customer data center basebox data center (hosting)
Physical access Customer basebox
Rack, power, cooling, network connectivity Customer or their housing provider basebox
Server Dedicated to the customer Dedicated to the customer – nobody shares it
User access From the company network or via VPN Via HTTPS or VPN over basebox's connectivity
Operation Customer – or basebox if commissioned Customer – or basebox if commissioned
Fully air-gapped operation Possible Network connectivity lies with basebox; isolation from the outside by agreement
Product basebox Server basebox Server – not Cloud

Why hosting at basebox is not Cloud

basebox Cloud means: basebox-owned infrastructure on which several customers have isolated environments, operated by basebox. A hosted server means: one physical machine for one organisation that happens to stand at basebox. No sharing at hardware level, own installation, own software stack, own version planning. That is why it is documented under Server – also in Security & Compliance → Hosting at basebox.

flowchart LR
  subgraph BBDC["basebox data center"]
    subgraph SRV["Dedicated customer server"]
      P["Platform"] --> S["Service models"] --> I["Inference"]
    end
    CLOUD["basebox Cloud<br/>isolated environments of several customers"]
  end
  U["Customer's users"] -->|"HTTPS / VPN"| P
  SRV -.- NOTE["Server – one customer, one machine"]
  style BBDC fill:#f4f2ee,stroke:#524e47,color:#1d1e1c
  style SRV fill:#dcefe2,stroke:#3a7a49,color:#1d1e1c
  style CLOUD fill:#e5e7eb,stroke:#6b7280,color:#1d1e1c
  style NOTE fill:#fbf0db,stroke:#b9770a,color:#1d1e1c

What changes per option

In the customer data center you fully control physical access, network and environment. You provide rack, power, cooling and network connectivity; you decide whether the server has internet access. The Server Preparation Guide starts from exactly this situation. Security posture: Customer data center.

In the basebox data center, basebox takes over the physical side: housing, power, cooling, network connectivity, physical access control. The hardware can be sourced through FAST LTA or provided by you. Your users reach the server via basebox's connectivity – via HTTPS or VPN. Who operates the software stack remains a separate decision. Security posture: Hosting at basebox.

What does not change

  • The installation: same stack, same Helm charts, same reference configurations.
  • Application administration: always with the customer.
  • Data sovereignty: your data lives on your dedicated server; whether basebox has access depends on the operating model, not on the location.
  • The documentation: all Server pages apply to both options.

Decision aid

Situation Option
Own data center with GPU-capable rack, power and cooling available Customer data center
Fully air-gapped operation required Customer data center
No own data center or no GPU capacity (power, cooling) Hosting at basebox
Dedicated server wanted, but no operational effort for the physical side Hosting at basebox, optionally with operation by basebox
Several sites, users over the internet Both possible; plan network connectivity

Location and operation are independent: a server at basebox can be operated by the customer, a server at the customer by basebox. See Operating models.

To be settled contractually

  • Who provides the hardware (FAST LTA, basebox, customer) and who owns it
  • Network connectivity and bandwidth; VPN for user access
  • Physical access rules and evidence for hosting
  • Procedure for hardware failure (replacement, access for technicians)
  • Return or erasure of storage media at the end of the contract

Next step: Operating models