Platform & Extensibility
A workspace you can shape.
Volobox is built as a framework: install capabilities like apps, connect your own tools and models, publish what you build, and extend the workspace itself, in your cloud or ours.


A spectrum, not a ceiling
Configure, compose, or build.
Start with settings. Assemble reusable capabilities without a new codebase. When the need becomes truly yours, extend the same workspace in code.
Library packs
Install agents like apps
Packs bundle agents, skills, commands, and connections. Install first-party packs like the Software Delivery Team (Release Manager, Delivery Coach, Tech Writer), publish your own packs from workspace content, move them between workspaces as files, or pull them from a private registry you host.
Nothing installs automatically; installed items become normal, editable workspace resources; secrets and tokens never travel inside a pack.
Open by design
Connect it to everything
MCP out
Agents call your MCP servers (GitHub and beyond), with calls recorded in the audit trail.
API and MCP in
External agents (Cursor, Claude, and others) and your own scripts read and write Volobox through its hosted MCP server or its public HTTP API, described in OpenAPI. They act within the access of the person they connect as.
Apps and tokens
An administrator registers each outside app: one people sign in through, approving what it may do group by group, or a service with its own secret that pulls the audit log. A person can also create a personal token with the groups and expiry they choose.
Webhooks
Signed events, such as a task closing, a pull request merging, or a customer replying, sent to your systems from the projects, repositories, and desks you pick, with a delivery log. Messages and meetings never leave the workspace.
Model freedom
Claude, GPT, Gemini, Kimi, or an open-source model you host, with your own keys, allowlists, and usage visibility.
Secret scopes
Encrypted, scoped secrets for repos, previews, and connections.
Microsoft 365 and Google
On Volobox Cloud, connect your Microsoft organization once for Entra ID sign-in, Teams meetings, Outlook calendars, and OneDrive and SharePoint files. Google Calendar, Meet, and Drive work with your company Google accounts.
Code hosts and meeting providers
GitHub, GitLab.com, and Azure DevOps for code; Zoom, Microsoft Teams, Google Meet, and Jitsi for meetings, next to Volobox Call.
Need a workspace app rather than another connection? Build a Custom App by describing it to an agent.
Administration
Admin controls that match the ambition
LLM providers and models, an AI kill switch for the whole workspace or one area, Reports on usage, cost, and health, run queues and concurrency, sandbox templates and budgets, MCP allowlisting, API apps and webhooks, alert recipients, working calendar, and an exportable audit log: a detailed admin surface for an AI workspace.
A setup checklist walks a new workspace through models, sandboxes, code hosts, and teammates, and reopens a step on its own if a connection breaks. Usage limits cap AI spend, sandbox compute, and workflow runtime, and alerts reach the people you choose when one nears its cap. On Volobox Cloud, you choose the window in which new releases install.
Beyond configuration
When configuration is not enough, we build with you
At the Build end of the spectrum: custom modules, company-specific workflows, and integrations, delivered by the team that builds Volobox.