If Slack and Discord had a baby.

Team chat with the layout you grew up with and the controls your company needs. Channels in a tree, rooms you can drop into, and agents at your side.

Save your place. You pick your @username when your invite arrives.

Web and Mac at launchiPhone nextWindows and Android after

The best of both. None of the compromises.

Discord got the shape of team chat right and never built it for work. Slack built for work and buried the conversation. Here's where team.chat lands.

Feature
SlackBuilt for work
DiscordBuilt for communities
team.chatBuilt for both
Channels in one shared tree
Personal sections
In community servers
Voice rooms in the sidebar
Huddles
Made for gaming
Stages for all-hands
—
For community events
Custom roles, per-channel permissions
Standard roles
Built for moderators
Replies that stay in the channel
Threads
No conversation view
One profile across workspaces
One per workspace
Also your gaming account
AI agents as members, with an owner
Apps
Bots
Company admin and audit log
Audit log on Enterprise
Moderation tools
Enterprise SSO
Business+ and up
—
Coming soon
Native Mac app
Electron, 321 MB
Electron, 480 MB
Swift, 21 MB

From Slack's and Discord's own documentation and Mac apps, September 2026. Plan-dependent features are noted.

Built for how your team actually works.

Voice rooms you can see into, conversations that stay in the channel, a message box that keeps up, and agents with a seat of their own.

Import history
ridgeline-slack-export.zipSlack export · 184 MB
Read
38channels
412,806messages
64people
9,127files
FromIntoMessages
#general# general121,403
#eng-deploys# deploys48,921
#incident-room# incidents3,318
64 people claim their history at sign-in.CancelImport 38 channels

Plug in the rest of your stack.

Anything that can send an HTTP request can post to a channel today, and anything that speaks MCP can take a seat. Native connectors come next.

Today: bring your ownPlanned: native connectors

Incoming webhooks

POST some JSON and it's a message, with mentions and replies. Slack-style payloads work as they are.

curl -X POST $HOOK_URL \
  -d '{"text": "Deployed *v2.14*"}'

Apps that answer

We POST new messages and mentions to your URL, signed. Answer with text and it's posted as a reply.

res.json({
  text: `On it, @${author.handle}`
})

MCP for agents and you

Seat an agent, or connect Claude as yourself. Read, search, post and react, never past what its owner can see.

claude mcp add --transport http \
  teamchat https://team.chat/api/mcp

Planned connectors aren't available yet. Product names and logos are trademarks of their owners.

Fast, because it's small.

A native Mac app with no browser inside, a web app that loads almost nothing up front, and search that doesn't make you wait.

21MB

The Mac app on disk, voice and video included.

0.2s

From launch to your messages, opened cold.

<25ms

A typical search across a million messages.

<60KB

The web app's first load. The rest arrives when you open it.

Mac app size on disk

team.chat21 MB
Slack321 MB
Discord480 MB

Sizes are app bundles on disk, measured on the same Mac in September 2026: team.chat for Mac with voice and video (LiveKit), Slack 4.52 and Discord 0.0.413. Launch time was measured before voice was built in; search is the median word search in a workspace of a million messages beside 200 others.

Private by construction.

Your conversations are protected from the database up, on every workspace.

Encrypted, per workspace

Messages and files are encrypted in transit and at rest, each workspace with its own key.

Isolated in the database

Row-level security keeps every query inside its own workspace, whatever the code above it does.

An audit log you can trust

Admin actions are hash-chained and sealed, so tampering shows. It never records what people wrote.

No passwords to leak

Sign in with a one-time code. Company SSO is coming for teams that need it.

Web and Mac first.

Every client speaks one protocol and shares one sync engine, so each new one arrives complete.

At launch

  • WebAny modern browser
  • macOSNative, for Apple silicon
  • WorkspacesPrivate and invite-only, for your team

Coming soon

  • iPhoneNative
  • CommunitiesFor your customers and users
  • Enterprise SSOPer workspace, your identity provider

After that

  • WindowsNative
  • AndroidNative

Questions, answered.

What is team.chat?

Chat for teams, with Discord's layout and Slack's grown-up side: channels in a tree, voice rooms, roles and stages, inside private workspaces with admin controls, an audit log and imports. People and AI agents work side by side.

We already pay for Slack. Why switch?

Rooms you can see instead of huddles, replies that stay in the channel, one account across every workspace, agents as real members, and a native Mac app a fraction of the size. Bring your Slack export and keep your history.

Why not just use Discord?

Discord is built for friends and communities. team.chat is built for a company: invite-only workspaces, admin roles, per-channel permissions, encryption at rest, a tamper-evident audit log, imports, and SSO on the way. It keeps the layout you like.

What does joining the waitlist get me?

A place in line for the beta. Invites go out in waves, in the order people joined, and yours lets you claim your @username.

When do I get my username?

When your invite arrives. Its link signs you in, and you pick 2 to 32 letters, numbers, dots or underscores. The first to claim a name gets it, and a few names, like staff and product words, are reserved.

Can we bring our history?

Yes: a Slack export, a Discord server, Microsoft Teams, or plain JSON. You preview every channel before anything is written, and people claim their old messages the first time they sign in.

Which platforms?

The web and a native Mac app at launch. iPhone next, then Windows and Android.

What can we connect?

Today, anything that can send an HTTP request: incoming webhooks, signed outgoing ones, apps that reply, and MCP for agents and personal tokens. Native connectors for GitHub, Linear, Jira, Sentry, Notion, Figma and more are planned.

How do agents work?

An agent is a member with an agent tag, its own name and roles, and a human owner. It never has more access than that owner. Connect Claude Code or any MCP client with the agent's token, and each agent holds a seat like a person.

Is our data safe?

Messages and files are encrypted in transit and at rest, each workspace is sealed off from every other in the database, and admin actions go into a hash-chained audit log that shows any tampering. The log never records what people wrote.

Do you support SSO?

Enterprise SSO is coming. It locks a workspace to your identity provider; accounts stay personal, so nobody loses their name when they change jobs.

Save your place.

Web and Mac at launch. Invites go out in the order people joined, and yours lets you claim your @username.

No password, no signup. One email when your invite is ready.