FAQ

StateBoard 2026.10.0 includes release readiness and agent maintenance through REST and MCP. See Upgrading when moving from an earlier release.

Why only three visual states? I want one for "in review."

The screenshot view keeps shipped / mock / missing so people can quickly distinguish a working production feature, a mock, and something absent. Release assessments use separate calculated states: ready, blocked, and needs_evidence. A review is a human decision supported by checks, rather than another visual state.

The notes field is for nuance ("shipped, but only for new accounts after 2025-01-01"). The state stays blunt.

Do my stakeholders need an account?

Public share links are read-only and need no account. Visual board links show the full board; release links show an explicitly curated recorded decision and selected images. Internal product and assessment views require OIDC sign-in with owner / editor / viewer permissions. A profession view is a presentation preset, not a permission boundary. Only publish content intended for the audience of the link.

Can multiple people edit a board at the same time?

Yes. Multiple editors can work in the workspace. Visual fields save independently. Assessment changes require the reviewed revision; a concurrent change returns a conflict and prompts a reload. Decisions recheck that revision, current owner membership, and fresh evidence in a transaction. Live cursors and automatic merging remain outside the scope.

Can I reuse a board as a starting point?

Yes — click Duplicate on any board's card in the overview. It deep-copies every screen and region into a new "… (copy)" board, with its own image files and share link, and opens it so you can change only what differs. Duplication copies the visual board only; it does not copy capabilities, assessments, evidence, decisions, or private retained media. Reuse a product board and create another assessment for a new candidate.

Why Postgres?

v1 is the team-ready cut — multiple replicas, shared state — so it's Postgres-backed. (The v0 wedge used SQLite for a single-container demo.) Bring your own Postgres, or let the Helm chart run a bundled one. Uploaded screenshots live on a filesystem volume beside it; an S3-compatible adapter remains deferred.

Will my data survive an upgrade?

Yes, as long as your Postgres data and the full data volume survive. Schema changes ship as numbered SQL migrations under migrations/, applied by pnpm migrate — the Docker Compose and Helm deploys run it for you on upgrade. Back up Postgres and both uploads/ and release-assets/ together; see Self-hosting → Backups.

Can I host the screenshots on S3?

Not yet. Uploads go to a local filesystem volume (STATEBOARD_DATA_DIR), separate from Postgres. An S3-compatible storage adapter remains in the deferred backlog; any future adapter must preserve decision media integrity and access boundaries. For multi-replica deploys today, give the uploads volume ReadWriteMany.

Does it phone home?

No. There's no analytics, no telemetry, no license server, no remote font fetching at runtime. At runtime the only outbound call is to your OIDC provider, during sign-in. The docs search runs locally on an Orama index built at compile time. See Self-hosting → Airgap considerations.

Why isn't this a roadmap tool?

StateBoard assesses whether a candidate supports its required outcomes and preserves the evidence behind a release decision. It does not schedule delivery, manage tickets or sprints, execute tests, or deploy releases. Screenshots and declared architecture help explain the assessment.

Can agents, scripts, or CI update boards?

Yes. Members create API keys that expire after 90 days by default and attribute writes to their owner. REST and MCP at /api/mcp support product context, features, dependencies, release scope, versioned checks, and evidence. Agents can maintain those records and visual regions within their key's role. The installable agent skill explains reconciliation and exact-candidate verification. A current human owner records release decisions and publishes or revokes release links in the browser. See Agents & API.

Can I integrate Jira / Linear / Slack?

Turnkey provider integrations remain deferred. Internal tools can push verification evidence through the existing API-key REST surface; evidence links are stored without outbound fetching. The real team pilot will determine the next integration priorities. See the roadmap and evidence submission guide.

Why MIT and not something more protective?

The pitch is explicit on this: no BUSL games, no rug-pull. The teams who need this most run in airgapped environments where they can't trust a vendor to stay in business. MIT lets them fork it, audit it, ship it inside a product they sell. That's the deal.