PulseBoard collects daily updates, detects blockers, and writes the team digest before you've finished your coffee. Sign in with Google → your org provisions in 60 seconds.
Today
3 of 4
submitted
Open blockers
1
auto-detected
Mood avg
4.0
last 7 days
Today's digest · Backend
Team shipped two infra wins yesterday — refresh-token rotation and a partition-strategy RFC. Today's focus is the outbox-relay merge and rolling out the partition fix behind a flag. One blocker surfaced: a staging migration stuck for 30+ minutes. Mood steady at 4.0.
One application, one database, and no setup ritual before it tells you anything.
A configurable form your team fills out in under a minute. Auto-reminders if they forget. Reply by email if they prefer.
Each morning, a Markdown-rendered summary of who shipped what, what is blocked, and the team mood — generated, not written.
Departments, teams and members in one tree. Every query is scoped to your organisation, and a record from another one simply does not exist to you.
Per-team submission rate, task throughput, overdue counts. Exportable to CSV. Email a weekly digest.
One Next.js application over one Postgres database. Permission-level RBAC, structured logging, and no moving parts that exist only to look impressive.
OpenAI today, with the provider chosen per capability. A hard daily spend cap per organisation, and a deterministic fallback so a missing key degrades the output instead of breaking the page.
Each task is routed to the model that fits it, behind a hard daily spend cap per organisation. Remove the API key and every agent falls back to deterministic text rather than breaking the page.
Ada shipped OAuth refresh-token rotation; Linus drafted a sticky-partitioning RFC after Friday's lag spike. Grace closed three medium-priority auth tickets. Today: outbox relay merge + partition rollout behind a flag.
What happens between someone typing an update and a client reading a report.
Google, Microsoft, or a password set from an invitation. Organisations are invite-only, so nobody joins by sharing your email domain.
Validated against the organisation’s template and written with its team and date, so it can only ever be read by people entitled to see it.
Blocker text is detected and a tagged ticket opens on the board, assigned to nobody until a developer picks it up.
A single card per team per day, generated by the scheduled job and capped by the organisation’s daily AI budget.
Once a week, the closed and blocked work for each client becomes a report on a revocable link, built from ticket titles only.
Sign in with Google. Your team gets the form. Your leaders get the AI digest.