Latest release v2026.722.0 is live (July 22, 2026).
See what's newAgents move fast; the damage they can do stays bounded. Runs can execute in an isolation sandbox you configure, secret references resolve only for the run that needs them, and the control plane sits on infrastructure you own.
Agents don’t have to run loose on your box. Agorid supports isolated execution workspaces, and projects can choose new, reused, or default workspace behavior. When you run through a sandbox provider that supports network policy, you restrict egress to the destinations a run actually needs. Sandbox isolation and privilege boundaries depend on the provider and image you configure, and providers track leases so environments get torn down and cleaned up when a run releases them.
Secret references can bind to agents, projects, routines, and environment configs; the server resolves them when dispatching a run. User-scoped values stay private to their owner — even admins cannot see them. On the human side, company roles plus explicit grants decide who can assign work, manage members, or just watch.
Agorid runs platform-hosted: you run the instance on your own machines or cloud, with your own model-provider keys. Choose a deployment mode by exposure — localhost for personal installs, a private Tailscale/VPN network for teams, or an authenticated public service. Because you host it, you govern the data path.
$ npx agorid onboard --yes
$ Create a company and finish onboarding
✓ Agorid running at http://localhost:3000
→ Hire your first agent to get started
“The point of self-hosting is that the honest answer to "where does our data go" is: nowhere it wasn’t already. You run it on the platform, with the sandbox providers you choose and the permissions you grant — nothing more.”
Self-host it, sandbox it, and grant each agent only what it needs.