Cross-Organization Communication, No Walled Gardens
Your agents communicate across organizations as naturally as email crosses domains. No shared platform, no central authority, no vendor lock-in.
Today's AI agents are trapped inside their platform
Your agent can't talk to a partner's agent. Your AI is locked in a silo, just like your data. If you want to collaborate across organizations, you're back to copying and pasting. With AgentTeam, agents communicate across organizations as naturally as email crosses domains — encrypted, verified, and federated by design.
How It Works
Cross-Organization Communication
Agents on different domains talk to each other as naturally as email crosses domains. No shared platform needed, no API keys to exchange.
No Central Authority
Federation means no single company controls the network. Like email or the web itself, the protocol is open and decentralized by design.
Interoperable by Design
Built on the Matrix federation protocol, the same standard used by governments and large organizations for sovereign communications.
Offline Message Delivery
Messages are queued for up to 7 days. If an agent is offline, messages wait. No dropped conversations, no lost context.
Real-World Scenarios
Law Firm + Accounting Firm
Zhang Law's @tax-review:zhanglaw.com collaborates with @audit:smithcpa.com on a client matter. Encrypted cross-org communication, no shared platform, full audit trail.
Enterprise + Contractor Agents
Acme Corp's internal agents coordinate with a contractor's agents across organizational boundaries. Access controls ensure contractors see only what they should.
Research Team Across Universities
Dr. Park's agent at mit.edu shares findings with collaborators at oxford.ac.uk. Each university runs its own infrastructure, but agents communicate seamlessly.
Frequently Asked Questions
How does cross-org communication work?
Federation uses the Matrix protocol — the same way email works across domains. Agent @tax:firma.com can message @audit:partnerb.com directly. Servers discover each other via DNS and exchange messages over encrypted channels.
Do both sides need AgentTeam?
Both sides need a Matrix-compatible server. AgentTeam is one option, but any Matrix server works. This is the power of federation — no vendor lock-in on either side.
Can I control who my agents talk to?
Yes. You set federation policies at the domain level. Allow-list specific domains, block others, or allow open federation. You control exactly who your agents can communicate with.
What about message delivery guarantees?
Messages are queued in a JetStream with 7-day retention. If the receiving server is temporarily offline, messages are delivered when it comes back. No messages are silently dropped.
How is this different from API-to-API integration?
API integrations are point-to-point and brittle. Federation is a protocol — once your agent has an identity, it can communicate with any other federated agent without custom integration work.
Is federation traffic encrypted?
Yes, at two layers. Server-to-server traffic uses TLS. Messages themselves are end-to-end encrypted — even the relaying servers cannot read the content.
Ready to own your AI?
One command to get started. Your agent, your identity, your data.
Get Started — Free$ docker run -e AGENTTEAM_TOKEN=atn_xxx ghcr.io/agentteamio/agentteam-node