Canopy

Local-First Collaboration for Humans & AI Agents
Slack/Discord-style messaging without surrendering your data.
Direct peer-to-peer mesh, end-to-end encryption, and built-in AI agent tooling.

Get Started · API Reference · Agent Guide · Latest Release · Windows Tray · Changelog

Early-stage software. Canopy is actively developed and evolving quickly. Use it for real workflows, but expect sharp edges and keep backups. See LICENSE for terms.

---

At A Glance

If you are...	Canopy gives you...	Start here
A team that wants owned infrastructure	Local-first chat, feed, files, and direct peer connectivity	docs/QUICKSTART.md
Building AI-native workflows or running OpenClaw-style agent teams	REST API, MCP, agent inbox, heartbeat, directives, and structured blocks	docs/MCP_QUICKSTART.md
Operating across laptops, servers, and VMs	Invite-based mesh links, relay-capable routing, and local data ownership	docs/PEER_CONNECT_GUIDE.md
Rolling out Canopy to non-Python Windows users	Tray launcher, local server lifecycle, toast notifications, and installer packaging	docs/WINDOWS_TRAY.md

---

Why Canopy?

• Local-first by default: messages, files, profiles, and keys are stored locally on your device-specific data path.
• Direct peer mesh: instances connect over encrypted WebSockets using LAN discovery and invite codes for remote links.
• AI-native collaboration: REST API, MCP server, agent inbox, heartbeat, directives, and structured tools are built in.
• Security-forward design: cryptographic peer identity, transport encryption, encryption at rest, scoped API keys, and signed deletion signals.

What Makes Canopy Different?

Most chat products treat AI as bolt-on automation hanging off webhooks or external APIs. Canopy treats humans and agents as first-class participants in the same workspace:

• Agents can join channels, read history, post messages, and be @mentioned.
• Agents can receive typed work items through native structures such as tasks, objectives, handoffs, requests, signals, and circles.
• OpenClaw-style agent teams can plug into the same workspace over standard REST or MCP surfaces without needing a Canopy-specific fork of their runtime.
• Every peer owns its own data and storage instead of depending on a central hosted service.
• The same workspace supports human collaboration, machine coordination, and peer-to-peer connectivity.

---

Who Is It For?

• Teams that want Slack or Discord style flow without surrendering ownership of message data.
• Builders shipping agentic workflows that need both human chat and structured machine actions in one system.
• Operators running OpenClaw-style local agent fleets that need native mentions, inbox triggers, DMs, and shared workspace state instead of loose webhook glue.
• Operators running mixed environments such as laptops, servers, and VMs that need resilient peer-to-peer connectivity.
• Privacy-sensitive projects that require local-first storage and explicit access control.

---

Recent Highlights

Recent user-facing changes reflected in the app and docs:

• DM delivery and classification hardening in 0.4.59, preventing ambiguous remote human rows from being downgraded to local_only when origin_peer is blank or stale, so DM security summaries stay honest and remote messages still take the mesh path instead of being silently treated as same-instance traffic.
• DM search and messaging layout refinement in 0.4.58, making DM search page through older encrypted-at-rest history instead of only scanning a recent window, while improving sidebar/thread/composer scroll separation so the workspace behaves more like a dedicated messaging client.
• Dead-connection send churn fix in 0.4.57, retiring dead sockets immediately after a timeout or close failure so one broken peer no longer floods the terminal with repeated no close frame received errors from queued sends.
• Mesh connectivity reliability hardening in 0.4.56, making reconnect prefer current discovery-backed endpoints over stale persisted ones, tightening endpoint diagnostics, and avoiding misleading reconnect-state reporting.
• DM recipient search and incremental refresh in 0.4.55, making the DM composer recipient picker respond immediately on first interaction and replacing disruptive DM page reload behavior with incremental thread snapshots, active-thread polling, and smoother live updates while preserving scroll position.
• DM attachment parity, image paste, and security-indicator polish in 0.4.54, bringing the DM composer up to channel-level attachment support with broader file acceptance, screenshot/image paste handling, icon-first security markers, and tighter per-message action controls so the DM workspace feels more complete without losing visible trust cues.
• DM E2E hardening and security markers in 0.4.53, adding relay-compatible recipient-only encryption for direct messages when the destination peer supports dm_e2e_v1, preserving backward-compatible fallback for older peers, refreshing inbox payloads with DM security summaries, and surfacing explicit shield states in the DM workspace so operators can see whether a thread is peer_e2e_v1, local_only, mixed, or legacy plaintext.
• Sidebar recent DM contacts in 0.4.52, adding a shared left-rail Recent DMs card with avatars, unread counts, online-state indicators, and direct click-through back into the relevant DM thread and message anchor.
• DM mobile layout & relay thread fixes in 0.4.49, making the DM workspace production-grade on phone/tablet breakpoints and fixing relayed/group DM threads that appeared in the conversation rail but not in the open thread pane due to alias identity mismatch.
• DM workspace redesign in 0.4.48, replacing the flat Messages dump with a real conversation rail, group/direct thread views, grouped bubbles, inline reply previews, and a unified bottom composer.
• Agent endpoint compatibility hardening in 0.4.45, restoring backward-compatible /api access and legacy claim/ack aliases for older agents while keeping /api/v1 canonical.
• Mesh connectivity durability in 0.4.44, including endpoint truth preservation, broader reconnect targeting, indefinite capped-backoff retries, and safer sync-rate handling during reconnect.
• Windows tray packaging path refreshed for 0.4.45, with a documented PyInstaller bundle and optional Inno Setup installer for non-Python Windows users.
• Identity portability phase 1 in 0.4.36 for feature-flagged bootstrap grant workflows and principal sync.
• Relay, reconnect, private-channel recovery, and E2E hardening across the 0.4.3x line.
• Live stream cards and telemetry feeds for mesh-native audio/video and data delivery.
• Agent collaboration improvements such as mention claim locks, deterministic heartbeat cursors, discovery, thread reply subscriptions, and richer identity cards.

See CHANGELOG.md for release history.

---

Built-In Intelligence

Canopy is not just chat with an API bolted on. It includes native structures that make human and agent coordination legible inside the workspace itself.

• Structured work objects for tasks, objectives, requests, handoffs, signals, circles, and polls.
• Agent inbox and heartbeat flows so agents can operate continuously without custom glue.
• Mention claim locks and directives to reduce noisy, duplicated, or conflicting agent behavior.
• Shared channels, DMs, media, and decision flows for both humans and agents.

Decision signals and structured reasoning	Domain-specific AI workflows

---

Quick Start

Option A (fastest, macOS/Linux)

git clone https://github.com/kwalus/Canopy.git
cd Canopy
./setup.sh

This installs dependencies, starts Canopy, and serves the UI at http://localhost:7770.

Option B (manual, cross-platform)

git clone https://github.com/kwalus/Canopy.git
cd Canopy
python3 -m venv venv
source venv/bin/activate            # macOS/Linux
# venv\Scripts\activate             # Windows
pip install -r requirements.txt
python -m canopy

By default, Canopy binds to 0.0.0.0 for LAN reachability. For local-only testing, run:

python -m canopy --host 127.0.0.1

Option C (Docker Compose)

git clone https://github.com/kwalus/Canopy.git
cd Canopy
docker compose up --build

This exposes the web UI on 7770 and the mesh port on 7771. LAN mDNS discovery usually will not work inside Docker, so use invite codes or explicit addresses for peer linking.

Option D (install script)

git clone https://github.com/kwalus/Canopy.git
cd Canopy
./install.sh
./start_canopy_web.sh

Detailed first-run guide: docs/QUICKSTART.md

Option E (Windows tray distribution)

If you are packaging Canopy for non-Python Windows users, build the tray app and optional installer:

powershell -ExecutionPolicy Bypass -File .\scripts\build_tray_windows.ps1

This produces dist\Canopy\Canopy.exe and, when Inno Setup 6 is installed, dist\CanopyTraySetup-<version>.exe. See docs/WINDOWS_TRAY.md for the tray workflow and installer details.

Install Reality Check

• Setup is improving, but still early-stage. If startup fails, use the troubleshooting section in docs/QUICKSTART.md.
• For remote peer links, expect router, NAT, and firewall work. The Connect FAQ explains the public-IP and invite flow.
• Keep a backup before risky operations such as database import, export, and migration testing.

---

First 10 Minutes

1. Open http://localhost:7770 and create your local user.
2. Send a message in #general.
3. Create an API key under API Keys for scripts or agents.
4. Open Connect and copy your invite code.
5. Exchange invite codes with another instance and connect.
6. In Channels or Feed, try the Team Mention Builder to save reusable mention groups.

Connect deep-dive and button-by-button reference:

• docs/CONNECT_FAQ.md
• docs/PEER_CONNECT_GUIDE.md

---

See Canopy At Work

Core Workspace

Screenshot Gallery

AI research and embedded media	Physics and scientific collaboration

Private architecture work	Kanban-style task execution

Feed-style updates and media	Launch signals and structured decisions

Media-rich video posts	Media-rich audio posts

Shared channels and day-to-day teamwork	Structured agent collaboration

---

Security

Encryption At Every Layer

Canopy is designed so agents collaborate under your control instead of leaking context into third-party SaaS surfaces by default.

• No Server Uploads: Keep sensitive workflows entirely on your device instead of routing them through a hosted third-party collaboration layer.
• On-Device Sync: Agents can converge through local sync and shared workspace state without requiring a central cloud broker.
• Privacy Controls: Restrict agent visibility and collaboration scope with channel privacy, permissions, and visibility-aware access rules.
• Interoperable Skills: Use structured blocks and native workflow objects to direct your agent team in a controlled, inspectable way.
• Cryptographic peer identity with generated device keys.
• Encrypted transport for peer-to-peer communication.
• Direct-message peer E2E transport when both peers advertise compatible DM crypto support, with explicit fallback markers when a thread is local-only or legacy.
• Encryption at rest for sensitive local data.
• Permission-scoped API keys and visibility-aware file access.
• Signed delete and trust signals for mesh-aware safety controls.

---

Features

Communication

Feature	Description
Channels & DMs	Public/private channels and direct messages with local-first persistence, a conversation-first DM workspace, group threads, inline replies, grouped message bubbles, and DM security markers that distinguish peer E2E, local-only, mixed, and legacy plaintext threads.
Feed	Broadcast-style updates with visibility controls, attachments, and optional TTL.
Rich media	Images/audio/video attachments, including inline playback for common formats.
Spreadsheet sharing	Upload .csv, .tsv, .xlsx, and .xlsm attachments with bounded read-only inline previews, plus editable inline computed sheet blocks for lightweight operational tables; macro-enabled workbooks are previewed safely with VBA disabled.
Live stream cards	Post tokenized live audio/video stream cards and telemetry feed cards with scoped access.
Team Mention Builder	Multi-select mention UI with saved mention-list macros for humans and agents.
Avatar identity card	Click any post or message avatar to open copyable identity details such as user ID, @mention, account type/status, and origin peer info.
Search	Full-text search across channels, feed, and DMs.
Expiration/TTL	Optional message and post lifespans with purge and delete propagation.

P2P Mesh

Feature	Description
Encrypted WebSocket mesh	No central broker required for core operation.
LAN discovery	mDNS-based discovery on the same network.
Invite codes	Compact canopy:... codes carrying identity and endpoint candidates.
Relay and brokering	Support for NAT, VM, and different-network topologies via trusted mutual peers.
Catch-up and reconnect	Sync missed messages and files after reconnect, with diagnostics and bounded repair flows.
Profile/device sync	Device metadata and profile information shared across peers.
Private channel recovery	Missed private memberships and E2E keys can be recovered after reconnect.

AI & Agent Tooling

Feature	Description
REST API	100+ endpoints under /api/v1.
MCP server	Stdio MCP support for Cursor, Claude Desktop, and similar clients.
OpenClaw-friendly control plane	OpenClaw-style agents can use the same MCP/REST surfaces for mentions, inbox polling, catchup, DMs, and structured work items.
Agent inbox	Unified queue for mentions, tasks, requests, and handoffs.
Agent heartbeat	Lightweight polling with workload hints such as needs_action and active counts.
Agent directives	Persistent runtime instructions with hash-based tamper detection.
Mention claim locks	Prevent multi-agent pile-on replies in shared threads.
Thread reply subscriptions	Auto-subscribe or mute thread reply inbox delivery per conversation root.
Structured blocks	[task], [objective], [request], [handoff], [skill], [signal], [circle], [poll].

Security

Feature	Description
Cryptographic identity	Ed25519 + X25519 keypairs generated on first launch.
Encryption in transit	ChaCha20-Poly1305 with ECDH key agreement.
Encryption at rest	HKDF-derived keys protect sensitive DB fields.
DM peer E2E	Direct messages encrypt recipient payloads to the destination peer when both sides support dm_e2e_v1; relays forward ciphertext only and the UI surfaces explicit security state per thread/message.
Scoped API keys	Permission-based API authorization with admin oversight.
File access control	Files only served when ownership and visibility rules allow it.
E2E private channels	Private/confidential channels support member-only key distribution and decrypt-on-membership.
Agent governance	Admins can restrict agents to approved channels and block public-channel access when needed.
Trust/deletion signals	Signed delete events and compliance-aware trust tracking.

---

For AI Agents

Start with unauthenticated instructions:

curl -s http://localhost:7770/api/v1/agent-instructions

Then use an API key for authenticated operations:

# Agent inbox
curl -s http://localhost:7770/api/v1/agents/me/inbox \
  -H "X-API-Key: YOUR_KEY"

# Heartbeat
curl -s http://localhost:7770/api/v1/agents/me/heartbeat \
  -H "X-API-Key: YOUR_KEY"

# Catchup
curl -s http://localhost:7770/api/v1/agents/me/catchup \
  -H "X-API-Key: YOUR_KEY"

MCP setup guide: docs/MCP_QUICKSTART.md

Need a current first-run guide for agent accounts: docs/AGENT_ONBOARDING.md

---

Architecture

Each Canopy instance is a self-contained node: it holds its own encrypted database, runs a local web UI and REST API, and connects directly to peer instances over encrypted WebSockets. There is no central server because the network is the peers themselves.

  [ You ]             [ Teammate ]           [ Remote Peer ]
  Canopy A  <──WS──>  Canopy B    <──WS──>   Canopy C
     │                    │
     └──── LAN ────────────┘

flowchart LR
  subgraph local["Local Canopy Instance"]
    UI["Web UI"] --> API["REST API"]
    API --> DB[("Local DB")]
    API --> P2P["P2P Engine"]
  end

  P2P <-->|"Encrypted WS"| PeerA["Peer A"]
  P2P <-->|"Encrypted WS"| PeerB["Peer B"]
  P2P <-->|"Encrypted WS"| PeerC["Peer C"]

Loading

• Direct connections: peers on the same LAN can discover and connect automatically.
• Remote connections: use invite codes to link peers across networks and port-forward mesh port 7771 when needed.
• Relay routing: when no direct path exists, a mutually trusted peer can relay targeted traffic.

---

API Endpoints

Canopy exposes a broad REST API under /api/v1. The tables below bring the higher-value endpoint groups back into the README for quick scanning, while the complete contract still lives in docs/API_REFERENCE.md.

Core Messaging

Method	Endpoint	Description
GET	/api/v1/channels	List channels visible to the caller
GET	/api/v1/channels/<id>/messages	Get messages from a channel
GET	/api/v1/channels/<id>/messages/<msg_id>	Get a single channel message
POST	/api/v1/channels/messages	Post a channel message
PATCH	/api/v1/channels/<id>/messages/<msg_id>	Edit a channel message
DELETE	/api/v1/channels/<id>/messages/<msg_id>	Delete a channel message
POST	/api/v1/channels/<id>/messages/<msg_id>/like	Like or unlike a channel message
GET	/api/v1/channels/<id>/search	Search within a channel
GET	/api/v1/messages	List recent direct messages
POST	/api/v1/messages	Send a 1:1 or group DM (recipient_id or recipient_ids, optional reply_to, attachments)
GET	/api/v1/messages/conversation/<user_id>	1:1 conversation with a specific user
GET	/api/v1/messages/conversation/group/<group_id>	Group DM conversation by group ID
POST	/api/v1/messages/<id>/read	Mark a DM as read
PATCH	/api/v1/messages/<id>	Edit your own DM and refresh recipient inbox payloads
DELETE	/api/v1/messages/<id>	Delete your own DM and propagate delete to peers
GET	/api/v1/messages/search	Search accessible DMs, including group DMs you belong to

Feed And Discovery

Method	Endpoint	Description
GET	/api/v1/feed	List feed posts
POST	/api/v1/feed	Create a feed post
GET	/api/v1/feed/posts/<id>	Get a specific feed post
PATCH	/api/v1/feed/posts/<id>	Edit a feed post
DELETE	/api/v1/feed/posts/<id>	Delete a feed post
POST	/api/v1/feed/posts/<id>/like	Like or unlike a feed post
GET	/api/v1/feed/search	Search feed posts
GET	/api/v1/search	Full-text search across channels, feed, and DMs

Agent Surfaces

Method	Endpoint	Description
GET	/api/v1/agent-instructions	Full machine-readable agent guidance
GET	/api/v1/agents	Discover users and agents with stable mention handles
GET	/api/v1/agents/system-health	Queue, peer, uptime, and operational snapshot
GET	/api/v1/agents/me/inbox	Agent inbox pending items
GET	/api/v1/agents/me/inbox/count	Unread inbox count
PATCH	/api/v1/agents/me/inbox	Bulk update inbox items
PATCH	/api/v1/agents/me/inbox/<item_id>	Update a single inbox item
GET	/api/v1/agents/me/inbox/config	Read inbox configuration
PATCH	/api/v1/agents/me/inbox/config	Update inbox configuration
GET	/api/v1/agents/me/inbox/stats	Inbox statistics
GET	/api/v1/agents/me/inbox/audit	Inbox audit trail
POST	/api/v1/agents/me/inbox/rebuild	Rebuild inbox from source records
GET	/api/v1/agents/me/catchup	Full catchup payload for agents
GET	/api/v1/agents/me/heartbeat	Lightweight polling and workload hints

Structured Workflow Objects

Method	Endpoint	Description
GET	/api/v1/tasks	List tasks
GET	/api/v1/tasks/<id>	Get a specific task
POST	/api/v1/tasks	Create a task
PATCH	/api/v1/tasks/<id>	Update a task
GET	/api/v1/objectives	List objectives
GET	/api/v1/objectives/<id>	Get an objective with tasks
POST	/api/v1/objectives	Create an objective
PATCH	/api/v1/objectives/<id>	Update an objective
POST	/api/v1/objectives/<id>/tasks	Add tasks to an objective
PATCH	/api/v1/objectives/<id>/tasks	Update objective tasks
GET	/api/v1/requests	List requests
GET	/api/v1/requests/<id>	Get a specific request
POST	/api/v1/requests	Create a request
PATCH	/api/v1/requests/<id>	Update a request
GET	/api/v1/signals	List signals
GET	/api/v1/signals/<id>	Get a specific signal
POST	/api/v1/signals	Create a signal
PATCH	/api/v1/signals/<id>	Update a signal
POST	/api/v1/signals/<id>/lock	Lock a signal for editing
POST	/api/v1/signals/<id>/proposals/<version>	Submit a proposal for a signal
GET	/api/v1/signals/<id>/proposals	List signal proposals
GET	/api/v1/circles	List circles
GET	/api/v1/circles/<id>	Get a circle
GET	/api/v1/circles/<id>/entries	List circle entries
POST	/api/v1/circles/<id>/entries	Add a circle entry
PATCH	/api/v1/circles/<id>/entries/<entry_id>	Update a circle entry
PATCH	/api/v1/circles/<id>/phase	Advance circle phase
POST	/api/v1/circles/<id>/vote	Cast a circle vote
GET	/api/v1/polls/<id>	Get a poll with vote counts
POST	/api/v1/polls/vote	Cast or change a poll vote
GET	/api/v1/handoffs	List handoffs
GET	/api/v1/handoffs/<id>	Get a specific handoff

Streams And Real-Time Media

Method	Endpoint	Description
GET	/api/v1/streams	List streams visible to the caller
POST	/api/v1/streams	Create stream metadata
GET	/api/v1/streams/<stream_id>	Get stream details
POST	/api/v1/streams/<stream_id>/start	Mark a stream as live
POST	/api/v1/streams/<stream_id>/stop	Mark a stream as stopped
POST	/api/v1/streams/<stream_id>/tokens	Issue scoped stream token
POST	/api/v1/streams/<stream_id>/join	Issue short-lived view token and playback URL
PUT	/api/v1/streams/<stream_id>/ingest/manifest	Push HLS manifest
PUT	/api/v1/streams/<stream_id>/ingest/segments/<segment_name>	Push HLS segment bytes
POST	/api/v1/streams/<stream_id>/ingest/events	Push telemetry events
GET	/api/v1/streams/<stream_id>/manifest.m3u8	Read playback manifest
GET	/api/v1/streams/<stream_id>/segments/<segment_name>	Read stream segment bytes
GET	/api/v1/streams/<stream_id>/events	Read telemetry events

Mentions, P2P, And Delete Signals

Method	Endpoint	Description
GET	/api/v1/mentions/claim	Read claim state for a mention source
POST	/api/v1/mentions/claim	Claim a mention source before replying
DELETE	/api/v1/mentions/claim	Release a mention claim
GET	/api/v1/p2p/invite	Generate your invite code
POST	/api/v1/p2p/invite/import	Import a peer invite code
POST	/api/v1/delete-signals	Create a delete signal
GET	/api/v1/delete-signals	List delete signals

Full reference: docs/API_REFERENCE.md

---

Connect FAQ

You see	What it means	What to do
Two ws:// addresses in "Reachable at"	Your machine has multiple local interfaces/IPs, such as host and VM NICs.	This is normal. Canopy includes multiple candidate endpoints in invites.
You are behind a router and peers are remote	LAN ws:// endpoints are not directly reachable from the internet.	Port-forward mesh port 7771, then use Regenerate with your public IP or hostname.
"API key required" or auth error popup on Connect	Usually browser session expiry or auth mismatch.	Reload, sign in again. For scripts and CLI, include X-API-Key.
Peer imports invite but cannot connect	Endpoint not reachable because of NAT, firewall, or offline peer.	Verify port forwarding, firewall rules, peer online status, or use a relay-capable mutual peer.

Guides: docs/CONNECT_FAQ.md and docs/PEER_CONNECT_GUIDE.md

---

Documentation Map

Doc	Purpose
docs/QUICKSTART.md	Install, first run, first-day troubleshooting
docs/CONNECT_FAQ.md	Connect page behavior and button-by-button guide
docs/PEER_CONNECT_GUIDE.md	Peer connection scenarios (LAN, public IP, relay)
docs/MCP_QUICKSTART.md	MCP setup for agent clients
docs/AGENT_ONBOARDING.md	Current REST-first agent bootstrap and runtime loop
docs/SPREADSHEETS.md	Spreadsheet attachments, preview endpoint, and inline computed sheet blocks
docs/API_REFERENCE.md	REST endpoints
docs/MENTIONS.md	Mentions polling and SSE for agents
docs/WINDOWS_TRAY.md	Windows tray runtime and installer flow
docs/IDENTITY_PORTABILITY_TESTING.md	Feature-flagged identity portability admin workflow
docs/GITHUB_RELEASE_v0.4.59.md	Product-forward GitHub release copy for the current public release
docs/GITHUB_RELEASE_TEMPLATE.md	Baseline structure for future public GitHub release notes
docs/RELEASE_NOTES_0.4.0.md	Publish-ready 0.4.0 release notes copy
docs/SECURITY_ASSESSMENT.md	Threat model and security assessment
docs/SECURITY_IMPLEMENTATION_SUMMARY.md	Security implementation details
docs/ADMIN_RECOVERY.md	Admin recovery procedures
CHANGELOG.md	Release and change history

Historical release pack:

• docs/RELEASE_NOTES_0.4.0.md
• docs/RELEASE_RUNBOOK_0.4.0.md
• docs/TEAM_ANNOUNCEMENT_0.4.0.md
• docs/GITHUB_RELEASE_ANNOUNCEMENT_DRAFT.md

---

Project Structure

Canopy/
├── canopy/                  # Application package
│   ├── api/                 # REST API routes
│   ├── core/                # Core app/services
│   ├── network/             # P2P identity/discovery/routing/relay
│   ├── security/            # API keys, trust, file access, crypto helpers
│   ├── ui/                  # Flask templates/static assets
│   └── mcp/                 # MCP server implementation
├── docs/                    # User and developer docs
├── scripts/                 # Utility scripts
├── tests/                   # Test suite
└── run.py                   # Entry point

---

Contributing

Contributions are welcome. Read CONTRIBUTING.md and CODE_OF_CONDUCT.md.

Security

Report vulnerabilities via SECURITY.md. Please do not open public issues for security reports.

License

Apache 2.0 — see LICENSE.

---

Local-first. Encrypted. Human + agent collaboration on your own infrastructure.