Features

Everything else. Which is a lot.

The factory gets the headlines. This is the tracker underneath it: the part your whole team uses every day, with or without agents.

Plan the work

Epics down to tasks. The why travels with the what.

  • Organizations, projects, teams. Project keys (ACME-123) you'll quote in commits for years.
  • Hierarchy: Epic → Feature → Story → Task, plus Bugs. Parent chains travel with the ticket, so agents read the why, not just the what.
  • Board with WIP-aware paged columns, Backlog with ranking, Sprints with a taskboard.
  • Items list with inline quick edits, duplicate, bulk actions and saved views (personal or shared).
  • Relations: blocks, blocked by, duplicates, related. Time tracking with estimate and remaining hours.
  • Templates per type (Bug report and User story built in), labels, custom workflows. CSV import and export.
  • Portfolio view of epics and features across projects, with CSV export.

Write things down

A wiki that lives next to the work.

  • Wiki per project, with page tree and revision history.
  • Markdown everywhere, #ACME-123 references with autocomplete that render as links.
  • Attachments: images (re-encoded to WebP), PDF, Word, Excel, PowerPoint, OpenDocument, CSV, ZIP.
  • Threaded comments, emoji reactions, mentions, newest first. Shareable item links.

Know what's happening

Finally an answer to "what is the AI doing?"

  • Cycle insights: cumulative flow, cycle-time scatter, throughput, P50 and P85 cycle and lead time.
  • Throughput split by human and agent.
  • Dashboards with widgets: burndown, velocity, CFD, Markdown notes.
  • Inbox with unread badge, per-kind notification settings.
  • Email (off, immediate, or a daily digest at 08:00 your time), plus Slack, Discord and Telegram, personal and shared org channels. Quiet while you're active in the app.
  • Run notifications: succeeded, failed, needs input. Analytics definitions.

Move fast

Fast at 100,000 items. A slower build fails CI.

  • Command palette (Ctrl/Cmd + K), keyboard sequences (g then i).
  • Dark mode that's actually dark, including the native dropdowns.
  • In-app product tour and a Get started checklist that checks real status.
  • We hold ourselves to a 200 ms budget at 100,000 items. We're at 15. Enforced nightly by k6. Performance.
p95 latency on 100,000 items, 20 projects and 400,000 history rows
Endpointp95Budget
Item list15 ms< 200 ms
Board77 ms< 200 ms
Search20 ms< 300 ms
Item detail6 ms< 200 ms
MCP list_ready_work50 ms< 300 ms

100k items, 20 projects, 400k history rows.

Connect things

Plays well with the rest of your stack.

  • GitHub App: commits with ACME-123: attach to the item, PR opened and merged can move the ticket to states you pick.
  • Outgoing webhooks: 8 events, HMAC-signed, retries with backoff, delivery log and redeliver. Webhooks.
  • REST API with OpenAPI and an interactive reference at /docs on every instance. REST API.
  • Sign in with Google or GitHub, or email and password.

Bring the client in

Invite your client in a minute. They see the board. They don't see the sausage factory.

The Stakeholder preset gives one person one project: the board, comments, a run's status and its pull request. No Factory area, no prompts, no logs, no agent chatter, no other projects.

No SMTP set up? You get a link to copy. Nobody waits on email config.

Try the whole thing for 30 days.

No card, no automatic charge. Or self-host everything for free, forever.