Sovereign deployment
For organisations that cannot (or do not want to) use the public multi-tenant SaaS, betool offers four sovereign deployment formats.
Format 1 — Managed multi-tenant (EU)
The default format. The betool SaaS runs on our infrastructure hosted in the European Union. Strict per-organisation isolation.
Who it's for: startups, SMBs, and innovation departments of large enterprises that are comfortable with managed hosting.
Time to start: a few hours (account created, organisations configured, first LLM keys connected).
Format 2 — Private customer cloud
A dedicated instance deployed on your cloud tenant: AWS, GCP, Azure, Scaleway, OVH, Outscale. The code and images come from us; hosting, networking and secrets remain under your control.
Who it's for: organisations with a cloud-first policy that want to retain infrastructure sovereignty.
Time to start: 1 to 3 weeks, depending on the complexity of your tenant's network. We provide Terraform / Helm charts and support the run-up.
Format 3 — On-premise
Deployment on your own infrastructure (data centre, internal Kubernetes cluster, dedicated virtual machine). You manage the resources; we provide containerised images, installation documentation and updates through a validated channel.
Who it's for: regulated organisations that require on-site physical hosting.
Time to start: 2 to 6 weeks. Includes an installation support session and knowledge transfer.
Format 4 — Air-gapped
Deployment with no outbound Internet connectivity. No external API calls (except within your perimeter). Implications:
- Private LLM models required — Ollama, vLLM, Llama / Mistral / Qwen on your hardware.
- No outbound webhooks to the Internet — only to your internal systems.
- Updates via bundle — signed image transferred manually.
Who it's for: defence, critical infrastructure, certain banking environments.
Time to start: subject to assessment. Expect 4 to 12 weeks depending on complexity.
Quick comparison
| EU managed | Private cloud | On-premise | Air-gapped | |
|---|---|---|---|---|
| Hosting | betool | You | You | You |
| External connectivity | Yes | Yes | Yes | None |
| Updates | Automatic | Auto / validated | Validated | Signed bundle |
| BYOK required | No | Recommended | Recommended | Mandatory |
| Time to start | Hours | Weeks | Weeks | Months |
SLA & support
The SLA follows the plan, not the format:
- Business — 8 business-hour response, 99.5% availability.
- Enterprise — 1-hour response (24/7 on request), 99.95% availability on multi-tenant, negotiable on other formats.
Updates
On customer-hosted formats (private cloud, on-premise, air-gapped), updates go through a validated channel: we publish a release, you decide when to deploy it. Release notes accompany every release; DB schema changes are documented and reversible.
Getting started
Request the security dossier — it contains the detailed architecture for each format, infrastructure requirements and the onboarding RACI.