Agent sprawl
Your teams ship agents faster than anyone can track. Blocks registers each one, gives it an owner, and controls who can find it. Nothing your teams built gets torn down.
Example animation. Shadow agents across sales, finance, operations, support, legal, and HR register into one private registry. Each gets an owner, a team finds an existing pricing agent instead of building another one, calls cross the grants, and one grant is revoked so its next call is rejected.
Sales built one agent on one framework. Finance built another on a different model. Someone in operations runs a third from a laptop. Each one works, and each one was built without asking anyone.
Shutting them down isn’t the answer. These agents are how your teams get faster. Agent sprawl is good. Unmanaged sprawl isn’t.
Teams keep their frameworks and models. Each agent connects out to your private network, and that connection is where the control lives.
Each agent connects out and joins your private registry, wherever it runs and whatever it was built with. Nothing is re-platformed.
Whoever registers an agent owns it, inside an organization that maps to a team or business unit.
Agents start private. Owners share them with people, teams, or other agents, so teams find an agent before they build another one.
Every change to an agent, its access, and its owners lands in the audit log, with who did it and when.
Owners revoke access and the next call is rejected. Administrators can take any agent offline.
App
Sales application
Reps get pricing guidance without a new integration project.
Agent
Deal Desk agent
Calls pricing instead of rebuilding the logic in another workflow.
@Pricing Agent
in your private registry
Team
Finance analytics
Margin analysis reuses the same approved pricing capability.
Authenticated app
Partner portal
User identity determines whether the pricing capability exists.
Agents keep running where they run. You wrap each one with the Blocks SDK or CLI. It opens one outbound connection and registers into your deployment’s private registry under an organization. Your deployment is single-tenant: your agents never appear on the public network.
Organizations map to departments, teams, or business units, and people can belong to several with different permissions in each. SSO group sync assigns them automatically.
Run agents where the data lives.
When data can’t or shouldn’t move, your validated agents go to it, on partner infrastructure or at your own sites. The host opens no inbound ports, and you control and audit every agent from one place.
Connect agents you don’t own.
Partners and portfolio companies bring their own agents onto your network, with access they scope and can revoke. Nobody has to standardize on your stack, and companies join and leave cleanly.