What the team is doing, on one board everybody can edit.
Not a project tool that somebody has to administer. A page that shows the six things this team actually cares about this week, made by the team, changed by the team, open on a screen in the corner of the room.
Ready to open
Eight boards your team will fight over
Each one opens as a real, working design. Put one on the wall screen and watch the standup get shorter.
The board that answers the question before anyone asks it: what's moving, what's stuck, what shipped.
Open this board Standup in one glanceYesterday, today, blocked — the whole standup, readable before the coffee's poured.
Open this board Who's on whatFaces next to work: who's on it, who's off, who's drowning.
Open this board On-call & statusUptime, incidents and the pager — the screen you glance at instead of holding your breath.
Open this board Release runwayRepos, versions and end-of-life dates — everything between here and shipped.
Open this board The numbers wallThe metrics the team actually moves, big enough to read from any desk.
Open this board Hiring pipelineFrom application to offer — where every candidate is, at a glance.
Open this board Field team mapWho's where, out in the world — pins, people and today's agenda.
Open this boardType it, and see it take shape
Say what the team needs on it
Pick one of these, or type what the team actually tracks — and watch the board build itself. The shapes are the real widgets; the numbers are missing because they are not yours yet.
The wall the standup happens in front of
Real numbers from the systems you already run, next to the things a human typed this morning. Two people can move a tile at the same time and see each other do it.
Tired of asking is it done yet?One board the team keeps, instead of four people keeping four.
Two people on one board, in the same second
Shared cursors, live edits, chat attached to the board rather than to a separate window, and drawing straight on the canvas when it is faster to circle the number than to describe it. Nobody has to say "refresh" and nobody has to say "are you in it?"
It is the difference between a wall the team keeps and a document somebody owns.
Point it at the database you already have
A tile can read from PostgreSQL, MySQL or MongoDB and draw whatever the query returns. The connection is read-only — not as a policy anybody has to enforce, but as the only thing the path can do — so pointing a dashboard at production is a decision you can make on a Tuesday without a meeting.
No warehouse to build first. If the answer is one query away, it is one tile away.
The thing everybody has to do at 09:15 becomes a button
A tile can carry an action, not just a reading — re-run the import, post the summary, open the right page of the runbook. The team stops remembering the incantation and starts pressing the tile, which means the newest person can do it on their first morning.
Anything that changes something asks before it does it. A dashboard that can act is only useful if it cannot act by accident.
From six euro a seat, and the VPN comes with it
Two seats is twelve euro a month paid yearly, or twenty paid monthly, and seats come and go as the team does. Every seat includes castomo VPN — self-hosted WireGuard on our own nodes — which is also what lets a board be locked to your team's address and refuse everything else.
Designing is still free for everybody, including people who never take a seat. You are paying for keeping and sharing the work, not for the right to do it.
Nothing to adopt, and nothing to undo if it does not stick
There is no workspace to create, no projects to model, no fields to define. You open the designer, take a board that already exists, and change it until it looks like your week. If the team hates it, close the tab; nothing was migrated into it.
Which is exactly why it tends to stick: the cost of trying is one afternoon, and the board that survives is the one the team actually built.