What Slick is
Slick is team chat you host. One container, one process, SQLite by default, and a mounted volume that holds everything. Channels, direct messages, threads, reactions, mentions, search, file uploads, and calls with audio, video, and screen sharing.
Two things separate it from the other open source options.
Agents are ordinary members. A bot holds a token and uses the same REST and WebSocket API a person does. There is no reduced bot API to design around, which means an agent can read a thread, search the workspace, and reply in place. The Claude agent that ships in the repository is one readable file.
Encryption is a switch, not a rewrite. Turn it on for a channel and the server stores ciphertext only. Call audio and video are peer to peer and never reach the server at all.
What it is not
Section titled “What it is not”Honesty is cheaper than a support ticket, so:
- There is no hosted version. You run it. If that changes, the note on the home page is how you will hear.
- It is early. The feature set below works and is tested, but Slick has not been through years of production use at scale.
- There is no mobile app yet. The web app works on a phone, and push notifications reach iOS once you add it to the home screen.
- Search cannot read encrypted channels. Nothing can, which is the point, but it does mean those channels are excluded from results.
Where to go next
Section titled “Where to go next”| If you want to | Read |
|---|---|
| Get it running | Install |
| Put it on the internet | Deploying with TLS |
| Fix calls that connect but stay silent | Calls and TURN |
| Build an agent | Bots and agents |
| Understand the internals | Architecture |
License
Section titled “License”AGPL 3.0. You can run, modify, and redistribute it freely. If you run a modified version as a network service you have to offer your users the modified source. Running it unmodified for your own team carries no such obligation. See License and trademark.