Compare
Pealboard and GitHub Projects
Pealboard is built on GitHub Projects. Every issue and project field you see is the same object your developers see, read through the same API. GitHub Projects comes with every GitHub plan, and Pealboard does not replace it.
Which one fits your team?
GitHub Projects is a better fit if…
- Everyone who needs to see or change the work already has a GitHub account.
- One project, set up once, covers the people who use it.
- You are happy to build the view across repositories by hand, per organization.
- You do not need a named saved filter you can share outside a project.
Pealboard is a better fit if…
- Customers, partners and staff without a GitHub account can send requests and follow them.
- The people who plan and triage get a screen made for them instead of a developer tool.
- One list, board or table covers every repository you connect, with no project to maintain.
- Saved views have names and URLs, so a colleague opens exactly what you were looking at.
What GitHub Projects offers
Every line below comes from GitHub Projects’s own pages. Each footnote names the page and the date we read it.
- GitHub Issues and GitHub Projects come with every GitHub plan — Free at $0, Team at $4 per user per month, and Enterprise from $21 per user per month — in identical wording across the tiers. There is nothing extra to buy.[1]
- Projects has table, board and roadmap layouts, and views can be ranked, grouped, sorted, sliced and filtered.[1]
- Custom fields cover iterations, priority, story points, dates, notes and links, and can be edited from the issue sidebar.[1]
- The Iteration field plans work over repeating blocks of time, with customizable lengths and the ability to insert breaks.[2]
- Built-in automation is four rules: closing an issue or pull request sets Status to Done, merging a pull request sets Status to Done, auto-add adds items matching a filter, and auto-archive archives items matching a filter.[3]
- Insights — the current-iteration stacked column chart and the historical burn-up chart — lives in GitHub’s own interface and has no API behind it.[4]
- No page we fetched — documentation, marketing or pricing — describes a way for a person without a GitHub account to view, submit or comment on a project item. That is an absence across every page that loaded, not a stated rule that an account is required.[5]
- An issue still belongs to exactly one repository. A project is a cross-repository view over items, not a change to where an issue lives.[5]
- GitHub’s cross-repository search is a query you retype or bookmark. There is no named saved filter you can share, outside a project.[5]
Side by side
| Pealboard | GitHub Projects |
|---|---|
| One list, board or table covers every repository you connect, from the first day. There is no project to set up first. | A project is a cross-repository view you build and maintain, and an issue still belongs to one repository.[5] |
| A view has a name, a URL and a sharing setting. It holds the filter, sort, grouping and layout. | A cross-repository search is a query you retype or bookmark. There is no saved filter outside a project.[5] |
| People with no GitHub account send requests in a portal and follow them. Each request becomes a GitHub issue. | No page we fetched describes a way for a person without a GitHub account to take part.[5] |
| The board is a layout over a project’s own Status field. Pealboard adds no workflow engine, because GitHub offers no way to author one. | Four built-in automations, and the only workflow mutation GitHub exposes is deleteProjectV2Workflow. There is no API to create, update or enable one.[6] |
| Free is $0 for up to three members. After that it is $10 per member per month, and engineers are never counted. | Included at every GitHub plan tier, with nothing extra to buy.[1] |
What we could not check
We could not confirm these details on GitHub Projects’s own pages, so we make no claim about them either way.
- Whether GitHub holds back any advanced Projects capability by tier — an item-count ceiling, a field-count ceiling, or Insights availability. No breakdown by tier was found on github.com/pricing, and a deeper comparison page may exist that we did not find.
- Whether people without GitHub accounts can take part in some way we did not see. Nothing on any page that loaded describes one, several guessed access and privacy documentation URLs returned 404, and no evidence to the contrary was found either.
The setup GitHub leaves to you
Pealboard arrives having done what a careful organization does by hand. One scope across every repository, a set of named views, status words a non-engineer can read, and a front door for people outside your organization.
Nothing is taken away from GitHub along the way. Your projects keep their four built-in automations, and Pealboard does not touch them. Insights keeps working in GitHub’s own interface, which is the only place it exists. Engineers work exactly as they did, and are never asked to sign into anything.
Turn Pealboard off and GitHub Projects is exactly as it was.
Try it on your own repositories
The Free plan connects three repositories and needs no card. Nothing is imported. Nothing in GitHub changes.
More comparisons
- Pealboard and Jira Software
- Pealboard and Linear
- Pealboard and Trello
- Pealboard and ClickUp
- Pealboard and ZenHub
- Pealboard and Canny
Sources
github.com/pricing and github.com/features/issues— that Issues and Projects are included, with identical wording, at every GitHub plan — Free $0, Team $4 per user per month, Enterprise from $21 per user per month — and the confirmed views and custom fields. Fetched 2026-09-09.docs.github.com/en/issues/planning-and-tracking-with-projects— the field types, including the Iteration field: "plan and track your work over repeating blocks of time... customizable lengths and the ability to insert breaks". Fetched 2026-09-09.docs.github.com/en/issues/planning-and-tracking-with-projects/automating-your-project— the four built-in automations: issue or pull request closed sets Status to Done, pull request merged sets Status to Done, auto-add of items matching a filter, auto-archive of items matching a filter. Fetched 2026-09-09.docs.github.com/en/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project— the current-iteration stacked column chart and the historical burn-up chart, and that Insights has no API — confirmed by its absence across the GraphQL schema and the REST documentation. Fetched 2026-09-09.platform/research/category-and-table-stakes.md §2.7— the three gaps: no participation path for anyone without a GitHub account across every page that loaded, issues remaining repository-scoped, and no cross-repository saved-filter object outside a project. Fetched 2026-09-09.platform/research/github-platform.md §2.4— that the only project workflow mutation GitHub exposes is deleteProjectV2Workflow; there is no API to create, update or enable one. Fetched 2026-09-09.
Our notes are in platform/research/category-and-table-stakes.md and platform/research/portals-and-feedback-tools.md. GitHub Projects is a trademark of its owner. Pealboard is not affiliated with it.