Licensed to be used in conjunction with basebox, only.
// reference
Reference & Releases
Applies to
Product: Cloud · Server · Audience: All
Facts, versions and history. This section contains no how-tos but the things you look up: what changed when, what is planned, which version runs where and how this documentation uses its terms.
In this section
| Page | What you find there |
|---|---|
| Versions | Every version since 1.1: the essentials, notes before upgrading and all changes |
| Roadmap | What is planned for upcoming releases |
| Version matrix | Which Helm chart version ships which basebox version and which components are bundled |
| Glossary | The terms of this documentation – Cloud, Server, platform, service models, inference, reference configuration – and the terms it deliberately avoids |
How basebox names versions
Releases follow the pattern major.minor.patch, for example 1.8.6. The changelog groups releases by minor version (1.8.x); patch releases bring fixes and security updates within that line. Security and feature updates are announced by e-mail and release notes.
On basebox Server the basebox version is delivered through the Helm chart version: a chart bundles frontend, AISRV, storesrv, ragsrv, ragsrv-support, identity provider, databases and inference in mutually compatible versions. Currently: chart 0.3.32 → basebox 1.8.8. The mapping is in the Version matrix.
Which version am I running?
- In the interface: user menu at the bottom left → Version Info. It shows version, active model, context size, realm and whether speech recognition and the API are available.
- On basebox Server additionally:
helm list -n baseboxshows chart and app version of the installed release. - In basebox Cloud, basebox keeps the environment up to date; you find changes in the changelog.
Binding terminology
This documentation uses basebox Cloud and basebox Server as product terms and describes a server by hardware, location and operation – not by labels such as "on-prem" or "hosted". Instead of "hardware profile" it says reference configuration with the statuses Validated · Supported · Experimental · Custom. The definitions are in the Glossary; older configuration keys such as AISRV_ON_PREMISE remain unchanged and mean "basebox Server".
Legal documents
The compliance package under the EU AI Act – Compliance, Disclaimer, Infra Policy, Model Register, Safety Notice – is in the Security tab under Compliance, not in this section.
Need help? Contact support