One deck for the whole team

Every task,thread and note.Plus a teammatewho ships.

Projects, boards, chat and notes in one workspace — and an AI teammate you can assign real work to. It writes the code, proves the build passes, and opens a pull request for your team to review.

Backlog · In progress · In review · Done

The same deck, in order.

Scattered work becomes a board everyone reads the same way — with priorities, owners and due dates.

No signup needed

Try the actual product, right here.

Drag the cards. Write in the editor. Send a task to Claude and watch it open a pull request. Everything below is live.

Drag any card between columns — it's a real board.

Backlog

2
WAV-01urgent

Fix login redirect bug

401 when signing in with Google.

#auth#bug
RSRaj Singh
WAV-03medium

Add CSV export to the board

Finance needs a weekly pull.

#api
Unassigned

In Progress

2
WAV-02high

Design the new billing modal

High-fidelity mocks for project creation.

#design
ABAlex Brown
WAV-06medium

Refactor the API client

Collapse duplicate fetch logic.

#cleanup
SOSam Ortiz

In Review

1
WAV-04medium

Improve search UX

Show recent queries in the dropdown.

#ux
JSJane Smith

Completed

1
WAV-05low

Update the colour palette

Refine brand colours for accessibility.

#design
MPMira Patel

The difference

A teammate you can assign work to at 11pm.

Every other tool asks who is free. When nobody is, type @Claude in the task and describe what you need.

  1. 01

    Request

    Someone types @Claude in a task comment. The title, description and whole discussion travel with it as context.

  2. 02

    Isolate

    A fresh branch and a separate working copy are cut from your default branch. Nobody's work is touched.

  3. 03

    Build

    Claude explores the real repository and makes the change, following the conventions already there.

  4. 04

    Verify

    The project is compiled. If it fails, the errors go back to Claude and it fixes them. Broken code never leaves the machine.

  5. 05

    Pull request

    The branch is pushed and a PR opens, titled with the ticket code, describing what changed and why.

  6. 06

    You decide

    The task flips to PR ready and the requester is notified. A human reviews and merges. Always.

Two gates, always

A machine gate and a human gate. The build must pass before anything is pushed, and a person must approve before anything is merged.

Standard pull requests

Ordinary branches and PRs on your own repository. There is no proprietary review surface for your team to learn.

What's inside

Six surfaces. One mental model.

Everything shares one set of people, projects and permissions — so a task mentioned in chat, written up in notes and finished on the board is the same task everywhere.

My work

A private list for every member — personal tasks and projects nobody else can query, linked back to the shared board.

Chat

Channels and direct messages with @mention autocomplete. Messages land live, grouped by day and author.

Notes

A real block editor: slash commands, code blocks, page links, teammate mentions and Ask AI.

Notifications

Generated by database triggers, not app code — so a completed task always reaches the lead.

Ticket codes

Every task gets a code like WAV-01, so work can be named the way engineers already talk about it.

Row-level security

Private data is filtered by Postgres before a row is returned. A UI bug can't leak someone's list.

Get started

Bring one squad across and run a sprint.

The first person to sign up becomes the team head. Everyone else joins with a link.