Where your team's conversations meet the work.
Channels, DMs, threads, and email — under one roof, on your servers, pinned to the projects and docs they're about. Stop losing context to scattered tools.
Built for the way your team actually works.
Real teams don't pause work to log it. They talk about it where it's easy. Comms makes wherever they talk be the right place.
Channels, DMs, and threads.
The team chat model you already know — channels for topics, DMs for private chats, threads to keep noise low. Markdown, code blocks, reactions, and pins included.
- Public and private channels
- Group DMs and threaded replies
- Reactions, custom emoji, and pins
- Edit, delete, and bookmark messages
Email, in the same inbox.
Stop tab-hopping between Slack and Gmail. Comms treats email as another channel — read, reply, and route it alongside team chat with subject lines, threading, and shared inboxes.
- Shared team inboxes
- Email threads alongside chat
- Convert any chat message into a mail thread
- Auto-responders and forwarded-email capture
Pinned to the work it's about.
Talking about a deal? It surfaces in Track. Discussing a doc? It surfaces in Ink. Comms is the conversation layer for every other ARK product — same conversation, two surfaces.
- Track integration — discuss board items inline
- Ink integration — comment on docs without leaving Comms
- One conversation, multiple surfaces — never duplicated
- Read state syncs everywhere
Search that respects your data.
Full-text search across channels, DMs, mail, and meeting transcripts — running on your own Postgres. No third-party indexing. No data leaking to an AI vendor you didn't approve.
- Cmd+K global search overlay
- Filter by source, person, or date
- Indexed locally — never leaves your servers
- Respects channel membership permissions
A complete feature set, grouped by what you're trying to do.
Messaging
- Public and private channels
- Direct messages and group DMs
- Threaded replies
- Emoji reactions and custom emoji
- Message edits, deletes, and pins
- Save / bookmark for later
- Shared team inboxes
- Email threads alongside chat
- Assign and route messages
- Auto-responders and canned replies
- Forwarded-email capture into channels
- Convert chat messages to mail threads
Cross-product
- Track integration — board item discussions
- Ink integration — doc-level conversations
- Recap integration — meeting summaries
- Open-in-Track / Open-in-Ink shortcuts
- Unified read state across products
Voice & video
- One-click huddles per channel
- Screen sharing in huddles
- Audio-only mode for low bandwidth
- WebRTC, self-hosted signaling
Search & navigation
- Cmd+K global search
- Full-text across messages, mail, transcripts
- Filter by source, person, date
- Keyboard-first navigation
Admin & security
- SSO — Google, GitHub, SAML
- Retention policies per channel
- Granular notification rules
- Export every message as JSON
- Row-level security on every table
Pay once. Own it forever.
Comms
Team chat, mail, and threads — pinned to the work they're about.
- Full source code
- Onboarding videos
- Live webinars
- Community access
Get ARK
All six products in one purchase. The whole platform working as one team.
- CComms · Chats & messages
- TTrack · CRM & projects
- IInk · Documents
- PPulse · Standups & surveys
- RRecap · Meeting notessoon
- HHive · Team overviewsoon
Secure checkout by Stripe. License key emailed the moment payment completes. Source code in a private GitHub repo on your account.
Questions, answered.
For most teams, yes. Comms has channels, DMs, threads, reactions, huddles, and full-text search. If you depend on a specific Slack integration, check the integrations list — or ask Claude Code to build a bridge in a few hours.
You point a domain at your Comms deployment and it routes incoming email into shared inboxes. Team members reply inline. Every message is searchable alongside chat.
Yes — Comms uses WebRTC with a lightweight signaling layer running on your own infrastructure. Works fine for teams up to ~15 in a call.
Comms accepts Slack's JSON export for channels, users, and messages. Attachments are relinked during import.
Transport is TLS. At-rest encryption follows your hosting provider's defaults (AES-256 on managed Postgres). End-to-end encryption is not a built-in mode.