Copyright © 2022-2026 basebox GmbH, all rights reserved.
Licensed to be used in conjunction with basebox, only.
Licensed to be used in conjunction with basebox, only.
// reference
Glossary
Applies to
Product: Demo · Cloud · Server · Audience: All
The terms this documentation uses – and, where it matters, the terms it deliberately avoids.
- Demo
- The public evaluation environment. For trying basebox only; never a production deployment. Statements about Demo infrastructure apply to the Demo alone.
- basebox Cloud
- Production environment on basebox-owned infrastructure in the Noris data center. Isolated customer environments, operated by basebox. No customer-owned physical server.
- basebox Server
- A dedicated physical server for one customer. Hardware from FAST LTA or customer-procured; located in the customer's or basebox's data center; operated by the customer or, where commissioned, by basebox. Hosting at basebox does not make it Cloud.
- FAST LTA
- Hardware partner through which Server hardware can be purchased. A hardware source – not a product, not a deployment model.
- basebox platform
- The management/application layer: UI, apps, authentication, permissions, audit, APIs, connectors, orchestration. Does not need large GPU resources.
- Service models
- Additional AI services used by basebox features: embeddings, RAG processing, OCR, STT, TTS, long-term memory. Ideally on dedicated GPU capacity.
- Inference
- The LLM/VLM/reasoning-model layer. Separate from basebox itself; sizing depends on model, quantization, context, concurrency and latency targets.
- Reference configuration
- A concrete, known hardware setup with documented topology, allocation and tested models. Not a requirement. Replaces the older terms hardware profile and hardware requirement.
- Validated / Supported / Experimental / Custom
- Status of a configuration or model: exactly tested by basebox · supported though not every combination recently benchmarked · expected to work, not production-validated · customer-specific, needs individual verification.
- Self-managed / basebox-managed
- Who operates a Server: the customer, or basebox under a separate commission (access via PAM/VPN or as agreed).
- Connector (MCP)
- An MCP server that gives the assistant a tool – web search, a wiki, a ticket system. Enabled per organization and per app; users sign in with their own account where required.
- Knowledge base / RAG
- The documents behind an app, searched before answering (retrieval-augmented generation). Answers cite sources.
- Terms this documentation avoids
- On-Prem / On-Premises as a product name (say Server, then state location and operation) · Hosted / Self-hosted as products · Hardware profile / hardware requirement (say reference configuration).