Why we built an open team-chat app

Team chat became infrastructure — the place decisions get made and work gets coordinated. That makes it strange how little control most teams have over it: your history lives on someone else’s servers, behind someone else’s pricing.

Your data, your box

This app is built to run on your own infrastructure. A Postgres database and a single web process is the whole story. Deploy it, point a domain at it, and your messages, files and members are yours.

Boring, modern foundations

Under the hood it’s Next.js, Postgres via Prisma, and Server-Sent Events for the live updates. Nothing exotic — the kind of stack you can read, understand and extend in an afternoon, with file uploads that work against S3-compatible storage or the local disk.

Start small, grow later

Two people or two hundred, the model is the same: workspaces, channels, threads, DMs, mentions, search. No seat-based surprises, no feature gates hiding the parts you actually need.