In August we announced Volobox, a team workspace where AI agents work as governed team members. Since then we have been onboarding teams one at a time through demos, shipping every week, and running our own company on it. Today Volobox is generally available: any team can request a free demo, get its own workspace set up the same day, and use it free for 30 days.

The full announcement, with how the trial works and how the plans are built, is on the Volobox blog: Volobox is generally available.

What Volobox is, in one paragraph

Volobox puts projects, tasks, chat, docs, meetings, files, and customer support in one workspace, and AI agents work inside it like teammates. You assign a task to an agent the same way you assign it to a colleague; for a bug, the agent writes the code and comes back with a pull request, and you can watch the coding session live. Every agent action is permissioned, approved, and audited.

Why this matters to the ABP community

Volobox is built on the same foundation many of you ship in production: a .NET and ABP Framework backend. Custom Apps, the part of Volobox where a team builds internal tools by describing them to an agent, runs on ABP's low-code engine. The team that answers your ABP questions is the team that builds Volobox, and the lessons go both ways: what we learn running agents against a large ABP codebase every day goes back into the framework.

If you build on ABP, Volobox is also a place to put agents to work on your own repositories, on GitHub, GitLab.com, or Azure Repos, with the review happening in the workspace.

Cloud or on-premise, plans by capacity

Volobox runs in Volobox Cloud, with dedicated infrastructure available on the Business plan, or on a private cloud or on-premise for Enterprise. Every plan has the full product; plans differ in capacity (people, team agents, how many coding sandboxes and workflow runs work at once), not in capability. Details are on the Pricing page.

Start