A self-hosted Slack alternative used to mean a weekend of Docker and a system nobody wanted to maintain. That’s the part that changed: if you use an AI coding agent, one plain-English sentence now gets you a team chat you own — channels, DMs, logins, files — running on your own server.
This post walks through what you actually get, what it really costs, and — honestly — what you give up.
Key takeaways
- Per-seat chat pricing is a tax on growing; owning makes your 51st teammate free.
- One sentence to your AI agent builds the real thing on jerrycan — code in your repo, not a hosted service.
- Your message history lives in your database: no retention limits, no export requests.
- The trade-off is a small server bill and responsibility for one compiled binary.
Why per-seat chat pricing punishes growth
Somewhere between your fifth teammate and your fiftieth, the chat bill stops being a rounding error. Per-seat pricing means the better your team does, the more you pay — for the same channels and the same DMs.
Worse, the money buys access, not ownership. Stop paying and the archive, the integrations and the muscle memory all vanish. Rented tools also change their terms — pricing, retention, features — whenever they like. That leverage is the real cost, and it’s the core of the rent-vs-own math.
What “one sentence” actually gets you
Point your agent — Claude, Cursor, Copilot, Windsurf — at jerrycan and say:
I don’t want to pay my Slack subscription anymore — can you build me one using jerrycan?
That sentence is a valid instruction. Here’s what comes out the other side:
| You say | The agent builds |
|---|---|
| ”channels for each project” | Channels and DMs — workspaces, threads, mentions |
| ”everyone on the team can log in” | Auth with invites, sign-in and roles |
| ”we share files constantly” | File storage on your disk, searchable forever |
| ”it has to feel instant” | Real-time messaging, synced across devices |
Not a mock — a working Rust backend in a repository you control, built the way any jerrycan backend is built, deployed to a server you choose, on your own domain.
The cost breakdown, honestly
Owning has real costs. They’re just different in shape:
- A server. Team chat for a whole company runs comfortably on a modest VPS — a flat, single-digit-to-tens-of-dollars monthly bill that doesn’t care how many people you hire.
- Attention. Updates and new features happen by asking your agent — the same motion that built the product. You are, however, the one responsible when something needs restarting.
- Migration. Moving years of Slack history is its own project. Most teams start fresh and keep the old workspace read-only until it expires.
Compare that with per-seat pricing, where a growing team’s chat bill compounds annually and buys no asset at all.
What you give up
Fair is fair: Slack has a decade of polish, thousands of integrations, and an app your team already knows. On day one, your owned chat has the features you asked for — no more. You’ll add integrations by asking your AI for them, one at a time, as you actually need them.
If chat is far from your core and the bill doesn’t bother you, renting is a reasonable choice. The case for owning gets strong when the subscription has leverage over you — when the price could double and you’d grudgingly pay.
Frequently asked questions
Do I need to know how to code? No. You describe the product; your AI does the engineering. The code it writes is readable Rust in your repo if you ever want to look.
Where does it run? Anywhere you choose: a VPS, your cloud account, a machine in your office. It’s a compiled binary with encryption, backups and TLS defaults built in.
Is jerrycan really free? Yes — free and open source. You pay only for your own hosting.
What if my AI gets something wrong? The backend is code, not configuration in someone else’s dashboard. Ask the agent to fix it, or fix it by hand — either way, nothing is opaque.
The whole workflow is genuinely one sentence long. Open your agent chat and say what you’re tired of renting.