Agent sprawl
Bring every agent into the light.
Register every shadow agent, give it an owner, and control who can find it. Nothing gets torn down, and teams stop building the same agent twice.
Partner networks
Connect agents you don’t own.
Get answers from companies you don’t run: portfolio companies, franchisees, partners, and suppliers. Their agents join your network with access they scope and can revoke. Nobody has to standardize.
Example animation. Portfolio companies, a partner, and a supplier join your network, each as its own organization, each with its own stack: nobody standardizes. Each company grants your firm specific agents through a gate at the edge of your network, and your calls cross those grants. One company revokes its grant, so the next call is rejected. Later one company exits, its organization detaches cleanly, and a newly acquired company joins.
Every company runs its own stack. You still need answers from all of them.
A private equity firm needs data from every company in its portfolio. Each company has its own CRM, its own agent platform, and its own decisions about both. Asking them all to standardize would take years, and wouldn’t hold.
With Blocks, each company’s agents join the firm’s network instead. Each company decides which agents to share and with whom, and can take that access back at any time. A company joins when it is acquired and leaves cleanly on exit.
The same shape fits franchise systems, holding companies, and supplier networks.
How it works
Bring each company in
Each company becomes its own organization on your Blocks deployment. Its people accept an invitation and sign in.
They connect their agents
Agents stay on the company’s own infrastructure and platform. Each one connects out and registers under the company’s organization, owned by the company.
They choose what to share
The company shares an agent with your organization, a team, a person, or one of your agents. Your side accepts, and the grant is live.
They can take it back
The company sees every grant it has made and can revoke any of them. Revocation takes effect immediately.
Exits are clean
When a company leaves, its grants are revoked or its organization removed, and its agents are off your network.
Each company’s own stack
Connects out only →
Scoped access →
Your firm, by grant
Each company’s own stack
- Portfolio company
- Another company
- A third
Connects out only
Blocks
Your private agent network
Scoped access
Your firm, by grant
- Your analysts
- Your agents
- Your apps
What you get
- One network across the portfolio
- Reach every company’s agents through one network instead of one integration per company.
- No standardization project
- Each company keeps its CRM, its agent platform, and its decisions.
- Clean entry and exit
- Companies join when they are acquired and leave cleanly on exit.
- Trust on both sides
- Each company controls what it shares, and every grant is on the record.
For your security team
Security overview- Outbound only
- Each company’s agents connect out. Neither side opens inbound ports to the other.
- Identity on every request
- Organization, participant, role, and scope are verified on every request, with short-lived, isolated credentials.
- Scoped access
- Companies share specific agents with specific organizations, people, or agents. Nothing is shared by default.
- Revocation
- A company can revoke a grant at any time and the next call is rejected. Your administrators can remove a company’s organization.
- Audit
- Every invitation, acceptance, grant, and revocation is in the audit log, with who did it and when.
- Kept apart
- Each company is its own organization, with its own members and permissions.
- Up to 99.999% SLA
- SOC 2 Type II
- SOC 3
- HIPAA with BAA
- GDPR
- CCPA
- ISO/IEC 27001
For your architects
Each company is an organization on your single-tenant Blocks deployment. Its agents register under that organization, and sharing works through invitations to an organization, a person, or an agent’s own identity. An invitation becomes a grant once it is accepted.
Owners list and revoke grants from the CLI or from the agent’s page. Organization invitations are accepted by someone with org:manage on the receiving side.
Other solutions
Distributed agents
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.