Changelog · Pealboard

2026-09-09

First release

Pealboard is available. This entry is a list of what exists on the day it shipped, so that a later entry can be read against it.

Issues across every connected repository, in a list, a board or a table.
Board columns grouped by a project’s single-select field, a label group, assignee, milestone or state. Dragging a card writes the field to GitHub.
Table adds project fields as columns and edits them in place.
Saved views: a named filter, sort, grouping and layout, with a URL, shared with the workspace or kept private.
Search across every connected repository, over titles, bodies, label names and issue numbers.
Create and edit issues, comment, close as Completed or Not planned.
Bulk edit of status, assignee, labels and project fields from the list and table layouts.
Projects and their fields, read and written as GitHub holds them.
Import of existing issues, comments, labels, milestones and projects on connection. No from-scratch setup.
Four workspace roles: owner, admin, member and viewer. Viewers are not billed.
Command palette and keyboard navigation.
Inbox, email notifications, a daily digest, and one outgoing Slack webhook per workspace.

A portal per workspace at a subdomain of pealboard.com, with its own customers and companies.
Request types with typed forms, each pointing at a repository, labels, an optional project and initial field values, and an optional issue type.
Per-request visibility: private, company or public.
Seven customer-facing status words, derived from the issue and never stored.
Public comments synced with GitHub. Internal comments are never shown.
Email to customers on a status change and on a new public comment, with an unsubscribe per request.
Voting on public requests, one vote per customer.
Passwordless sign-in: a 6-digit email code or a sign-in link.
Three access modes per portal: invite only, domain allowlist, open.
Branding: logo, accent color, welcome text, portal name.
An attribution line and a hidden marker on every issue and comment Pealboard writes.
A hold queue for a new customer’s first request on an open portal, and Turnstile on every form.
Per-customer export as JSON, and deletion that pseudonymizes the attribution Pealboard wrote.
A manager role for a customer-side lead.
Unlimited portal customers on every plan, never billed.
Reply to portal, share an existing issue to a portal, and merge duplicate requests.
Attachments stored by Pealboard and linked from the issue body through signed URLs.

A versioned REST API for workspace callers and a second for portal callers, published as OpenAPI 3.1.
API keys with the prefix pb_, stored as digests and shown once.
Idempotent, paginated reads and writes, with ETags on reads and a request id on every response.
A stateless remote MCP server with twelve task-shaped tools, authenticated with an API key.
A native iOS and Android app: inbox, issues with filters, issue detail with comments and a quick status change, portal requests needing a reply, and push notifications.

Three plans: Free, Team and Business. Prices are on the pricing page.
Billing counts the owner, admin and member roles. Viewers, portal customers and engineers are never counted.
A 14-day trial of Team, with no payment card.
On a lapse, writes are refused and reads continue.

Portal JWT single sign-on, audit log export and custom portal domains, all named for v1.1 and included in the Business plan when they ship.
SAML for the workspace.
A roadmap view, a changelog board inside a portal, outgoing webhooks, a Slack app with slash commands, and a rule builder.
The generated API reference. The developer documentation pages that will carry it say so.