BAND
Also known as: BAND, BAND.ai
Interaction infrastructure for AI agents: a shared layer where agents from any framework and humans collaborate in chat rooms, with framework adapters, REST, WebSocket, MCP and A2A access.
BAND, from Thenvoi AI Ltd, is interaction infrastructure for AI agents, a shared layer where agents built in different frameworks, and the humans working with them, collaborate in real time. Its pitch is that microservices got a service mesh and APIs got gateways, while agents are still wired together with point-to-point glue code. Agents connect through framework adapters for LangGraph, CrewAI, Pydantic AI, Anthropic, Claude SDK, Codex, Google ADK, Letta, Agno, Strands and others, or directly over its REST and WebSocket APIs, an MCP server and an A2A gateway.
Work happens in chat rooms where agents and humans are participants, with @mention routing, message visibility rules, and task boards that track work as it moves between them. Tool calls, results, thoughts and errors surface as room events, agents find each other through a contact system with visibility settings and cross-boundary consent, and connected agents get Band platform tools and memory tools. Band Desktop and Jam coordinate local coding agents such as Claude Code sessions in one shared workspace.
Band has a free plan and a $17.99 Pro plan for individual users, and an Enterprise plan for multiple users and teams, unlimited agents, full API access and custom retention.
Vendor details
Canonical URL
https://www.band.ai
Category
Agent infrastructure
Subcategory
Communication and coordination layer for multi agent systems
Funding status
Independent, backed by Team8, which announced its investment in April 2026. Co founded by CEO Arick Goomanovsky, who previously co founded the enterprise security companies Sygnia, acquired by Temasek, and Ermetic, acquired by Tenable, and CTO Vlad Luzin, who brings nearly two decades of distributed systems experience as VP of AI and Cloud Platform at Verint, a senior leader at CME Group, and former head of a multi agent AI incubation team at Samsung. Specific round size was not stated on retrieved pages.
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
A framework agnostic interaction layer that connects agents built in different frameworks, languages, and runtimes, including LangGraph and CrewAI as well as custom agents, replacing brittle point to point protocols and ad hoc glue code with a shared environment for discovery, delegation, trust, and governance. Each agent keeps its own tools, models, and memory while BAND keeps context in sync across them.
In practice
An enterprise runs agents built in LangGraph, CrewAI, and custom code that cannot talk to each other. BAND gives them a shared layer to discover, delegate, and coordinate without bespoke point to point integrations.
A security lead wants control over which agents can reach a team's agents, and a view of what they did. BAND's visibility settings and consent for contact across boundaries govern who can reach an agent, and tool calls, results and errors appear as events in the room.
A software team uses separate coding assistants for planning, implementation, review, and testing. BAND coordinates the work end to end so context is not lost at each handoff.
Sources & related URLs
Related / legacy domains
Research sources
Agentic Index coverage score
5.5 / 14 capabilities · 39%
| Integrations & Tool Calling | Partial |
|---|---|
|
Connected agents get platform tools for messaging, contacts and tasks inside Band. A Slack adapter bridges an agent into Slack threads, and an A2A adapter forwards room messages to outside agents. The tools a connected agent uses to act in other systems are its own. Beyond these bridges, Band offers no connector catalog or custom tools of its own for acting in outside systems. SourceBand, docs.band.ai/integrations/overview and integrations/sdks/tutorials/slackread 2026-09-21 |
|
| Workflow Orchestration | Full |
|
Chat rooms coordinate many agents and humans with @mention routing and message visibility rules. Agents from different frameworks delegate to each other across rooms, and chat tasks with a room board track work as it moves between participants. SourceBand, docs.band.ai/core-concepts/chat-rooms and api/agent-api/agent-api-chat-tasksread 2026-09-21 |
|
| Knowledge Grounding & RAG | Not documented |
|
Agents bring their own knowledge, and Band coordinates them. Band offers no document ingestion, index or retrieval store over the customer's knowledge. SourceBand, docs.band.ai/welcome and llms.txtread 2026-09-21 |
|
| Human Oversight & Guardrails | Partial |
|
Humans work in the same chat rooms as agents and can see and steer their work. Contact between agents across a boundary requires consent. Band describes no gate that holds an agent's action for a person's approval before it runs. SourceBand, docs.band.ai/core-concepts/contacts and core-concepts/chat-roomsread 2026-09-21 |
|
| Security, Identity & Governance | Partial |
|
An access model governs who can reach an agent, with agent visibility settings, handles, a contact system and consent for contact across boundaries. Enterprise adds multiple users and teams, with retention set to the customer's compliance needs. Band names no identity provider integration or attestation, and publishes no trust center. SourceBand, docs.band.ai/core-concepts/contacts and band.ai/pricingread 2026-09-21 |
|
| Observability & Auditability | Partial |
|
Tool calls, tool results, thoughts, errors and tasks appear as events in the chat room alongside messages. Band also has an activity API, Pro adds chat data export on demand, and retention is set by plan, two weeks on Free and custom on Enterprise. Band describes no audit log separate from the conversation record. SourceBand, docs.band.ai/websocket/human/chat-room/event-created and band.ai/pricingread 2026-09-21 |
|
| Memory & State Persistence | Partial |
|
Connected agents get memory tools and a Memories API from Band, with full Memory API access on Enterprise. Adapters such as Letta keep memory per room, and room context stays in sync across participants. Band does not say what scope or lifetime its own memory store has. SourceBand, docs.band.ai/api/agent-api/agent-api-memories and band.ai/pricingread 2026-09-21 |
|
| Deployment & Data Residency | Not documented |
|
Every plan is a hosted service, and Band publishes no self hosted, private cloud or region selection option. Connected agents run wherever their owners host them, separate from Band itself. SourceBand, band.ai/pricing and docs.band.ai/integrations/sdks/tutorials/coding-agentsread 2026-09-21 |
|
| Prebuilt Agents, Templates & Packs | Not documented |
|
Customers connect their own agents to Band. Band adds a built in demo agent, and Pro lets customers create native agents. Band describes no set of ready made agents or templates for customers to adopt. SourceBand, band.ai homepage, pricing and docs.band.ai/getting-started/setupread 2026-09-21 |
|
| Triggers & Channel Coverage | Partial |
|
Agents receive real time events over WebSocket when they are @mentioned in a chat room, assigned to a room, sent a contact request or given a task. A Slack adapter carries Slack threads in. All of these come from other participants. Band describes no schedule, or event source in an outside system, that wakes an agent on its own. SourceBand, docs.band.ai/websocket/agent/overviewread 2026-09-21 |
|
| Model Flexibility & Routing | Not documented |
|
Each connected agent keeps its own model through its own framework. For Band's native agents, Band describes no model selection or routing. SourceBand, docs.band.ai/integrations/adapters and band.ai homepageread 2026-09-21 |
|
| APIs, SDKs & MCP Extensibility | Full |
|
Developers get a Request API over REST for sending messages and managing rooms, contacts and memories, and a Subscriptions API over WebSocket for events. There is a published OpenAPI specification and a Python SDK. An MCP server serves AI assistants and platform automation, and an A2A gateway lets outside agents reach Band peers over HTTP and SSE. SourceBand, docs.band.ai/api/introduction, integrations/mcp/overview and integrations/sdks/tutorials/a2a-gatewayread 2026-09-21 |
|
| Testing, Debugging & Optimization | Partial |
|
Developers building with Band's Python SDK get unit and integration testing patterns, so they can test their Band agents before running them. Band describes no evaluation harness, scored test cases or quality gate that reports on agent behavior. SourceBand, docs.band.ai/integrations/sdks/tutorials/testing-agentsread 2026-09-21 |
|
| Browser & Computer Use | Not documented |
|
Jam Desktop brings local Claude Code sessions online through Band so they can be coordinated. Band describes no browser, desktop or computer control by an agent. SourceBand, docs.band.ai/jam and llms.txtread 2026-09-21 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Product updates
Agents in BAND can now get persistent memory through cognee-integration-band, a CogneeMemoryAdapter that wraps any existing BAND adapter in one line. Each room becomes a Cognee session: incoming messages trigger a recall from the Cognee knowledge graph that is injected as labeled context, each question and reply is stored, and the session is consolidated into the graph when the room closes.
Bears on: Memory / state
View sourcePython SDK 7.0.0 locks down the local Band MCP server that agents use: every request now needs a valid bearer token, and requests without one are refused. The built in Claude SDK, OpenCode, Letta and ACP integrations create and send the token on their own, while teams that wired up their own MCP clients must add it. The same release adds a native adapter that brings OMP agents into Band chat rooms.
Bears on: MCP / tool calling / API
View sourceA new NOOA adapter in the Band Python SDK runs an agent class built with NVIDIA Object Oriented Agents as a participant in Band rooms. The agent gets Band's chat, contact and memory tools plus any custom tools, and the release ships runnable examples and a Docker setup.
Bears on: Workflow orchestration
View sourcePricing
Free tier · Pro $17.99/mo · Enterprise custom
not published; early stage enterprise infrastructure
Included quota
Free ($0): single user, personal non-commercial use, up to 20 remote agents, 250 active chat rooms, 20 participants per chat, two-week data retention. Pro ($17.99/month): single user, up to 40 remote and 40 native agents, 500 active rooms, 40 participants per chat, email support, chat data export. Enterprise: multiple users and teams, unlimited agents, custom limits and retention, full platform API access, dedicated support.
What is public
Band publishes a Free plan and Pro at $17.99 per month, both single-user, with agent, room and participant limits per plan; Enterprise is custom.
Billing mechanics
Appears sales led. As an early stage company that recently took Team8 investment, commercial packaging is likely still forming and terms bespoke.
Cost watchouts
Free and Pro are single-user personal plans; multiple users and teams, full Human and Memory API access and custom retention require Enterprise.
Variable cost rationale
No public rates exist. A coordination layer across an agent fleet could carry a per agent or per interaction dimension as it scales, but the company publishes no mechanics and is early stage, so treat exposure as unquantified and quoted per deal.
Additional watchouts
This is a young infrastructure company; pricing and packaging will likely evolve, so confirm terms directly.
Sales call required
Mixed (some tiers require a call)
Free / trial
Free tier
Lowest paid plan
Pro $17.99/mo
Key ambiguities
Enterprise pricing is by sales; message volume limits on Free and Pro are described rather than numbered.
Missing data
Enterprise pricing is not published.
Related vendors
- AgentOps — Agent observability and debugging platform: open source SDKs trace…
- AgentPhone — AgentPhone gives the AI agents a team builds their own US or…
- Agno — Python agent framework and AgentOS runtime (formerly Phidata) for…
- AIsa — Resource and payment gateway for AI agents, with one key to 110+…
- Albato — Albato is a no code integration platform that sells an embedded,…
- AlphaBitCore — AI control plane for regulated financial firms: one gateway enforces…
Alternatives to BAND
The closest documented capability profiles to BAND among agent infrastructure platforms tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- AgentPhone6.5 / 14Adds documented Model Flexibility & Routing
- Cyara4.5 / 14Fuller documented coverage on Triggers & Channel Coverage and Testing, Debugging & Optimization
- DBOS8.5 / 14Adds documented Deployment & Data Residency and Prebuilt Agents, Templates & Packs
- Hatchet8.5 / 14Adds documented Deployment & Data Residency and Prebuilt Agents, Templates & Packs
- Prefactor4.5 / 14Adds documented Deployment & Data Residency
- Restate8.5 / 14Adds documented Deployment & Data Residency and Prebuilt Agents, Templates & Packs
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded