JackComma
Weekly product sync in 15 minutes. Since last week:
- Pull request #482 merged
- ENG-219 closed
Slack channels
Comma follows the channels you choose. It answers questions, shares notes and drafts the replies that you approve.
Your company's agent, on your own servers
Comma answers in your channels, updates your issues and docs, and takes notes in your meetings. You choose its servers, its models and who can use it.
Comma at work for a company
An example of Comma's Home on an instance a company runs itself. You ask Comma to catch you up on Slack, Linear, email and Notion. It lists the work it finished this morning, and a reply to Priya waits for you to send it. This week it answered 48 questions in Slack, triaged 23 Linear issues, sorted 112 emails and updated 17 Notion pages. The Routines suggest the next step in each tool, and the Tasks rail shows four Tasks in progress, one in each tool.
You decide where your data goes
Comma reads mail, issues, documents and calls to do its work. Self-hosted, it reads them on servers you manage.
Tasks, memory, files and transcripts stay in your own PostgreSQL, ClickHouse and object storage. Model calls go to the provider you choose, with your key.
Your servers
One Docker Compose file starts the web app, the Admin console, the server and its data stores on a machine you choose.
Your models
Set your provider's endpoint, model and key, or let each person add a private model. Calls bill to your provider account, not to Comma credits.
Your people
Sign-up stays off until you turn it on. In the Admin console, the owner creates accounts and chooses which models people can select.
Comma keeps your tools up to date
Linear issues
Comma triages and assigns new issues, and it closes an issue when its fix merges. A decision that is yours waits for you.
In Gmail and Outlook, Comma drafts replies, files invoices and unsubscribes from newsletters. Set it to draft only, and you send each reply yourself.
Notion pages
Comma keeps plans, notes and checklists in Notion current, with a link to each source. Changes that need review wait for you.
Comma joins your meetings
It joins Google Meet calls on the calendars you choose, keeps the transcript, and turns the call into notes and next steps.
Before the call
Comma posts a brief to the team's channel: what changed since the last meeting, with links.
In the call
Comma joins as a named participant and keeps the transcript.
After the call
The summary, action items, transcript and recording arrive in one thread. Ask Comma there to file the action items in Linear.
You stay in control
Deploy
Start every service with Docker Compose on a machine you choose. Upgrades keep your data.
Self-host guideGovern
The owner manages accounts and models in the Admin console. An audit log records each privileged command.
ConfigurationSecure
Apps connect with scoped permissions that you can revoke. Agents never see raw credentials.
SecurityVerify
The agent runtime is built in Elixir and Lean. Lean and TLA+ check its core rules.
How Salix worksFAQs
What runs on our servers?
The Comma web app and Admin console, the Comma server with its agents, PostgreSQL, Redis, ClickHouse, and MinIO for stored files. One Docker Compose file starts them on one machine, and sign-in codes go out through your mail server.
Which models can we use?
The model provider you set for the instance: its endpoint, protocol, model ID and key. People can also add a private model in Settings. Calls bill to your provider account, and a self-hosted instance needs no Comma credits.
Which tools can Comma work in?
Linear, GitHub, Gmail, Google Calendar, Google Drive, Notion, Outlook and Slack, each through its own sign-in. Some need an app registration with the provider in your name, and we help you set those up. Plugins add MCP servers and Skills for other tools.
Which meetings does Comma join?
Google Meet calls on the calendars you choose, or a call you send it a link to. The meeting runtime is not part of the Compose stack, and we set it up with you.
How do upgrades and backups work?
Upgrade with the Compose project name the instance started with, and your data stays. Back up the five volumes together: config, PostgreSQL, objects, ClickHouse and Redis. The config volume holds the encryption key, so never regenerate it.
Is our data used to train AI models?
No. We do not use your files, conversations or prompts to train our own or third-party general-purpose AI models. Self-hosted, they stay in your stores, and model calls go to the provider you set.
Contact sales
- Plan your self-hosted deployment
- Connect your team's tools
- Set up the meeting bot