◲ Ticketing
Coming soon · cloud & on-premise

Ticketing that follows the thread of the work, not tickets in a void.

A project tracker built for how work actually moves — with humans and AI agents in the same loop, and a diagram inside every ticket.

Be first to try it. No spam — one launch email.

What Jira got wrong

Tools should make the work legible. Most make it heavier.

We ran a whole software cluster on ticketing for a year and learned exactly where the flat, form-driven board falls apart. This is what we built instead.

The flat board

  • Tickets float in a list; the story between them is lost
  • Status is a dropdown someone forgot to change
  • Prose blobs — no structure, no diagrams
  • Humans and automation live in different tools
  • "Done" is a click, not evidence

Ticketing

  • Work Threads — the connected line of work stays visible end to end
  • State that reflects reality — readiness is gated, not guessed
  • Rich bodies — diagrams, tables and sequences render inside the ticket
  • Human-in-the-loop as a first-class surface — approvals, decisions, reviews
  • Evidence on close — a ticket ships with proof, not a promise

Built in

The parts you feel from day one.

🧵

Work Threads

Every ticket belongs to a thread that keeps the narrative — what moved, why, and what is next — current at a glance.

📊

Diagrams in the ticket

Flowcharts, sequences, wireframes and architecture render right in the body. Decisions get drawn, not buried in a paragraph.

🤝

Human-in-the-loop

Approvals, feature reviews and decision points are built into the flow — the place where a person signs off is part of the product, not a Slack thread.

🤖

Agent-native

AI agents and people share one board and one API. Agents pick up work, report evidence and hand back — no bolt-on integration.

✅

Evidence & readiness gates

Close requires an observable artifact. "Ready" is mechanically checked, so the board tells the truth.

🔎

Governance & audit

Versioned history and a real approval trail — so you can always answer who changed what, when, and against which rule.

Your infrastructure, your call

Cloud when you want speed. On-premise when you need control.

Cloud

Hosted, zero-ops

Sign up and go. Managed updates, backups and scaling. Ideal for teams that want the value without running the stack.

On-premise

In your own walls

Runs on your servers — regulated data, air-gapped networks, full control. Same product, your perimeter.

Ticketing is designed to compose cleanly with — or stand entirely apart from — the rest of our stack. Buy just the board, or connect it to the authoring and orchestration tools when you are ready.