StateBoard
Status reporting for visual products. Show, don't tell.
StateBoard turns screenshots of your webapp into a living status board. You mark regions on the screens, tag each one as shipped, mock, or missing, and share one read-only link your stakeholders can read in 30 seconds.
These docs explain how to use it.
Why this exists
Every product team building a visual webapp eventually hits the same wall: the more carefully you write user-value stories, the worse they perform as status updates for non-technical leadership.
"What's actually working right now? What's still mock data? What hasn't been built yet?" Every executive, in every quarterly review, ever
Roadmap tools answer "when will it ship." Demo tools answer "how does it work." Neither answers "what state is it in right now, screen by screen." StateBoard is the missing artifact.
What you'll find here
Getting started
Create your first board, upload a screen, mark a region.
Annotating
The three states, region drawing, labels, and notes.
Sharing & Present mode
Share links, the fullscreen Present mode, keyboard shortcuts.
Self-hosting
Docker, Helm, persistent volumes, airgap deployment.
FAQ
Answers to the questions that come up most.
Roadmap
Where each upcoming feature sits on the v1.x / v2 / v3 timeline.
Changelog
What shipped in each release, and what's intentionally not here yet.
The current release
You're looking at 2026.6.0: team-ready. The full feature list and what's intentionally not here yet lives in the changelog. Highlights:
- Manual screenshot upload, region tagging, three states (
shipped/mock/missing) - Read-only public share links: revocable, multiple per board
- Multi-user via Keycloak / OIDC, with
owner/editor/viewerroles - Postgres-backed, multi-replica safe, append-only audit log
Headless capture, scheduled re-capture, diff view, and integrations (Jira / Slack / Notion) are explicitly on the roadmap. See the roadmap for where each one sits.
License
MIT. Use it, fork it, ship it inside your product, sell consulting around it.