Wardroom
ProductDocsChangelog

The team hub · designed, being built

Where the crew gathers.

One space per organisation. Every channel a feed of the things that already happen — a pull request, a support ticket, a sales lead, an alert, a deploy — and the conversation around them.

Read the design
wardroom — the shape of it
$ gh pr create --title 'Ship the thing'#backend · PR #212 opened by chris · 2 checks running#support · ticket #4181 from a customer · reply →#alerts · tripline: NetworkError spiked 4× in mobileyou: on it — pairing with priya in 10

What it is

What Wardroom owns.

The design in six lines. The full version is in the docs.

Spaces and channels

A space per organisation, channels for whatever the team wants; the feeds arrive as typed threads next to the talk.

GitHub

Every repo gets a channel: pushes, pull requests, reviews, failed checks and releases, one thread per PR or issue.

Support and leads

Purser's tickets and leads mirrored as threads — the customer's words rendered as theirs — with a deep link to act.

Alerts and deploys

Tripline's signed webhooks and runsheet's deploys land where the people who fix them are.

Anything with a webhook

A signed incoming webhook per channel: Stripe, Cloud Run, a cron. Slack's model, without Slack.

Owns nothing but the talk

A thread here is a mirror with a link; the ticket stays purser's, the PR stays GitHub's. Acting from a thread comes later, as an explicit action.

How it goes

Three steps.

  1. 01

    Claim a space

    Sign in through Latchkey and name your organisation; teammates join by invitation.

  2. 02

    Bind the feeds

    Install the GitHub App, paste a webhook secret from tripline or anything else. Channels appear per repo and source.

  3. 03

    Talk next to the work

    Threads under every event; mentions, unread, search, files. The consoles stay the work surface — the hub is where you see it all.

Questions

Asked already.

Is this a Slack replacement?
For a team whose tools are on this stack, yes: the feeds are first-class threads, not bot posts. For everyone else, it is not trying to be.
Can I reply to a customer from here?
Not in the first release. A plain message in a mirrored ticket thread is always internal; replying to the customer will be an explicit action that runs in purser on your behalf.

Bring the feeds home.

A space per organisation, every tool's events as threads, the talk in between.

Read the designThe house