StateBoard
Assess product capabilities, dependencies, and verification evidence through views for each role.
StateBoard shows what works, what it depends on, and why a team believes a release is ready. Capabilities connect the outcomes a product must support to implementation dependencies and verification evidence. Product, frontend, backend, QA, operations, and release owners inspect the same assessment through views relevant to their work.
These docs explain how to use it.
Why this exists
An annotated screenshot makes a visible feature easy to judge. Backend developers also need its services, API operations, events, and data dependencies; QA needs acceptance claims and results; a release owner needs the complete scope and unresolved gates.
StateBoard keeps that context connected. Capabilities can span several screens or have no UI. Evidence supports specific claims in an identified candidate, environment, audience, and configuration, and a human records the release decision.
The visual editor remains available: mark screen regions as shipped, mock, or missing, then share the visual board. Release assessments add verification and preserved review artifacts without changing those visual delivery labels.
What you'll find here
Getting started
Create your first board, upload a screen, mark a region.
Release readiness
Define capabilities and dependencies, collect evidence, and record a decision through six views.
Annotating
The three states, region drawing, labels, and notes.
Sharing & Present mode
Share links, the fullscreen Present mode, keyboard shortcuts.
Agents & API
API keys, the REST API, the built-in MCP server, and the installable agent skill.
Self-hosting
Docker, Helm, persistent volumes, airgap deployment.
FAQ
Answers to the questions that come up most.
Roadmap
The adopted direction toward release readiness, and what remains planned.
Release-readiness MVP plan
The data model, readiness rules, and delivery contract behind the release-readiness workflow.
Changelog
What shipped in each release, and what's intentionally not here yet.
The current release
2026.10.0: release readiness connects the product's features, screens, dependencies, and verification results. See the changelog for the full release notes.
- Product workspaces with a screen gallery, reusable features, and candidate-specific release reviews.
- Versioned checks and append-only results, with calculated readiness and preserved human decisions.
- Agent maintenance through REST and MCP, including product context, dependencies, checks, and evidence.
- English and German interfaces, with saved language preference and unchanged authored content.
- OIDC roles, audit history, annotated visual sharing, and curated public release reviews.
Follow the release readiness guide or explore the example review. Existing deployments must apply migrations 0008–0010 and update the OIDC callback before using this release. See Upgrading. The roadmap retains the planned team pilot and remaining backlog.
License
MIT. Use it, fork it, ship it inside your product, sell consulting around it.