case study · pantts · project boards
every shape
of plan
Pantts is realtime, multi-tenant project boards with one idea at the centre: a card is a single row in Postgres, and that same row renders as a kanban card, a table row, a gantt bar or a node on a graph canvas — with an insights pane over the top. Every change lands in every open browser in well under a second.
the brief
every view of the plan, one live source of truth
Five lenses, zero copies.
Planning tools multiply copies of the truth: the board says one thing, the timeline another, the spreadsheet a third — and someone spends their week reconciling them. Every "view" is usually an export wearing a costume.
Pantts refuses the copies. One card model in one database is projected into five lenses, so dragging a bar on the gantt is the same write as moving a card on the board — there is nothing to reconcile, because there is only one thing.
And because collaboration tools die when half the team is locked out, members, submitters and clients are all included — Pantts never charges per seat.
the model
one row, five projections
A card is a row. Everything else is a lens.
Rank, dates, assignees, labels and data channels live on the row; each lens is just a different way of drawing it. That is what keeps five views honest where other tools keep five databases.
the live board — the landing art from pantts.com, animations and all.
the same rows through the other lenses — gantt with a rippling dependency, the grid with a live sweep, insights redrawing as the work moves, and the cursors of everyone else on the board.
the platform
realtime by default · security per row
The database tells everyone.
Realtime isn't a feature bolted onto Pantts — it is how writes propagate. Database triggers broadcast every committed change to every open browser, and the same row-level security that gates a person's requests gates their AI agents through the built-in MCP server.
two tabs, one row — the change lands everywhere because postgres announces it.
a github project becomes a live board in seconds; the sync runs both ways.
how it was delivered
repo init 21 july · live from the first week
Ten days to a product.
846 commits in the first ten days took an empty repository to a working product, and it never stopped: every change is gated by the test battery and deployed to pantts.com as it lands. There was no launch day — just shipping.
fig 02 · the delivery timeline.
fig 03 · commits per month, from the repository history.
measured from the pantts repository, aug 2026.
the stack
fast where it shows, strict where it counts
Boring where it matters.
The interesting parts — the card model, the realtime layer, the lens engine — sit on deliberately unexciting foundations, with every mutation flowing through one optimistic write path that carries the undo stack.
project · specification
Planning something ambitious?
hello@envlpr.com. We'll tell you honestly whether we're the right team for it.