Kanban that closes the loop. From card to invoice.
Most kanban tools stop at the column. Logbook Boards continue — every card knows the project, the client, the timer running on it, the credentials in your vault and the line item it will become on next month's invoice. Drag the cards in the live demo below — they really move.
Sprint 47 — Logbook core
Drag any card to a different column, or watch your simulated teammates push work forward in real time. This is the same engine that runs in production.
Watch your team work — without standing over their shoulder.
Cards move with sub-second latency thanks to a WebSocket pipeline (Laravel Reverb). When Mara starts a card, you see it instantly — the timer, the assignee, the column change. No refresh, no "last synced 2 minutes ago" badge.
- Optimistic UI: your drags feel instant, conflicts auto-resolve
- Live cursors and presence avatars per board
- Branch + PR status pinned to each card
When you start a card you’re assigned to, the timer is already on the right project.
You’re assigned to a card. You hit "Start" in the corner. That single action begins the timer, pauses any other running card, attributes the time to this exact card, project and client, and surfaces it live on your team’s board. No timesheet to fill on Friday.
- One-tap start from the card you’re assigned to
- Auto-pause on context switch — only one timer at a time
- Hours flow into the billable summary and the next invoice draft
A vault entry is one click away from any card.
A card about migrating the staging database? Pin the credentials from the Vault straight onto the card. Anyone assigned (and unlocked) can copy the connection string in a single click — the cleartext never lives on the card, never lands in chat, and every reveal is logged.
- Pin Vault items by reference — ciphertext only on the card
- Access still gated by the vault’s permissions and unlock state
- Every reveal is logged with who, when and which card
Use the columns your team actually has — or invent new ones.
Engineering wants "in review". Content wants "first draft, edit, publish". Sales wants a pipeline. Each board defines its own columns, automations and required fields — without you needing to learn a workflow editor.
- Custom statuses, swimlanes and per-column WIP limits
- Automations: auto-assign, auto-move on PR merge, slack ping on blocked
- Templates: engineering sprint, content calendar, deal pipeline
A board that reaches into the rest of your business.
- Time trackingBolt-on integration. Half your team forgets to start it.Native, on every card. Auto-paused when you switch cards.
- Client visibilityEither invite the client (and watch them get confused) or screenshot weekly.Read-only client portal mirrors the board with friendly statuses, without exposing your internal cards.
- InvoicingExport hours to CSV, paste into invoicing tool, hope nothing got missed.Logged hours appear on the next invoice draft. One click to send.
- Tool surface area3–4 separate subscriptions, each with its own login and bill.One workspace covers boards, time, vault, portal and invoicing.
Less context-switching, more shipped.
0%
fewer tabs open during the day
No more Trello + Toggl + Notion + Stripe
0h
reclaimed per week
Across a 5-person agency
<300ms
card-move sync latency
Reverb-powered WebSockets
0%
of billable hours captured
When timers live on the card
Same board engine. Very different workflows.
Sprint board with PR status, branch and deploy state.
GitHub integration pins PR + CI status to each card. Cards auto-move when PRs are merged. Code review reminders ping the right person.
- PR status (draft, ready, merged) on the card
- CI build pass/fail badge
- Branch name auto-suggested from card slug