Administration
Deployment and models
Where Volobox runs (our cloud, your private cloud or on-premise), which models it uses, and where coding sandboxes and your data live.
Volobox runs where your organization needs it: on Volobox Cloud, or in your own private cloud or on-premise. Its AI works from the first day on models included with your workspace, or on model providers you connect with your own keys. This page is for the people who decide where Volobox runs and which models it uses; plans, prices and what each plan includes are on Pricing.
Deployment options
- Volobox Cloud. We set up and run your workspace. An administrator chooses an update window for new releases, or upgrades when it suits the team; mandatory releases are installed either way. Microsoft 365 features, including Microsoft Entra ID sign-in, connect through one Microsoft 365 connection with nothing to register in Entra.
- Private cloud or on-premise. Volobox runs in infrastructure you control (which plans offer it is on Pricing), and whoever operates it decides when it upgrades. Microsoft Entra ID sign-in uses your own app registration.
Note
On-premise and private cloud start with a conversation rather than a trial: request a demo.
Models: included, or bring your own
A Volobox Cloud workspace arrives with model access we manage, so chat, agents and coding work on the first day with no provider setup. Administrators choose which of those models are enabled and which one coding sessions start on.
You can also bring your own models, with your own keys. Connect providers such as OpenAI, Anthropic and OpenRouter, Azure OpenAI deployments, or another OpenAI-compatible endpoint. Examples are model families such as Claude, GPT, Gemini and Kimi, and self-hosted open-source models. See Add a model provider.
Note
Whether your plan includes your own providers is listed on Pricing. If a plan does not include them, a provider added earlier is paused with its settings kept, never deleted.
Coding agents
Coding agents add one more choice:
- OpenCode runs on the organization's models.
- Cursor and Codex run on each person's own account.
- Claude Code runs only on a person's own machine signed in to their Claude subscription, never in the cloud sandbox.
See Coding.
Where sandboxes run
Agents run code, and coding sessions run, in sandboxes: isolated computers created for the work.
- Cloud sandboxes are the default.
- Your machines: a person can add a computer they own. It connects to Volobox outbound with no open port, and runs only that person's private work. See Run coding sessions on your own machine.
Where your data lives
Data location follows the deployment you choose. On-premise or private-cloud deployments let you keep Volobox and your model endpoints in infrastructure you control.
Volobox sends the context a request needs to the model endpoints your workspace configures. Whether a provider retains requests or uses them for training depends on your agreement with that provider.
For managed-cloud regions, retention and backup requirements, bring your policy to the security review: see Trust.