Compare
Pealboard and GitHub Projects
This is the one comparison that is not a competition. Every issue and project field Pealboard shows is the same object a developer sees in GitHub, read through the same API, and GitHub Projects is included at every GitHub plan with nothing extra to buy.
Which of these is you
Choose GitHub Projects
- Everyone who needs to see or change the work already has a GitHub account.
- One project, configured once, is enough scope for the people who use it.
- You are content to set the cross-repository view up by hand, per organization.
- You do not need a named, shareable saved filter outside a project.
Choose Pealboard
- Customers, partners or internal staff without a GitHub account need to submit requests and follow them.
- The people who plan and triage are not engineers, and a developer tool is the wrong interface for them.
- You want cross-repository scope as the default rather than a project you maintain.
- You want saved views as objects with names and URLs, shared across a team.
What was confirmed about GitHub Projects
Each line was read on GitHub Projects's own pages on the date in its source. Nothing about GitHub Projects appears on this page without one.
- GitHub Issues and GitHub Projects are included at every GitHub plan tier — Free at $0, Team at $4 per user per month, and Enterprise from $21 per user per month — with 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 — exists in GitHub’s own interface and has no API behind it.[4]
- No page fetched — documentation, marketing or pricing — describes any way for a person without a GitHub account to view, submit or comment on a project item. This is an absence across every page that loaded, not a quoted statement 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, shareable saved-filter object independent of a project.[5]
The difference, line by line
| Pealboard | GitHub Projects |
|---|---|
| Cross-repository scope is the starting point: one list, board or table over every repository the workspace connected, with 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 is a named object with a URL and a sharing setting: a saved filter, sort, grouping and layout. | A cross-repository search is a query you retype or bookmark. There is no saved-filter object outside a project.[5] |
| Portals: people with no GitHub account submit and follow requests that become GitHub issues. | No page fetched describes any participation path for a person without a GitHub account.[5] |
| The board is a layout over a project’s own Status field. Pealboard adds no workflow engine, because GitHub exposes 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 at $0 for up to three members, then $10 per member per month. Engineers are never counted. | Included at every GitHub plan tier, with nothing extra to buy.[1] |
What was not verified
These are gaps in the research, not findings about GitHub Projects. They are here because a comparison that prints only what was confirmed reads as though the rest was checked and found wanting.
- Whether GitHub gates any advanced Projects capability by tier — an item-count ceiling, a field-count ceiling, or Insights availability. No tier-specific breakdown was found on github.com/pricing, and a deeper comparison page may exist that this research did not locate.
- The absence of a participation path for people without GitHub accounts is an absence of evidence across every page that loaded, and several guessed access and privacy documentation URLs returned 404. No contrary evidence was found either.
Pealboard is the setup GitHub leaves to you
What Pealboard does with GitHub Projects is what a careful organization does by hand: one cross-repository scope, a set of named views, a status vocabulary a non-engineer can read, and a front door for people outside the organization. Done once, and multi-tenant.
Nothing is taken away from GitHub in the process. Your projects keep their four built-in automations and Pealboard does not touch them. Insights keeps working in GitHub's own interface, where it is the only place it exists. Engineers keep working exactly as they did, and are never asked to sign into anything.
If you turn Pealboard off, GitHub Projects is exactly as it was. That is the test this comparison should be read against.
Look at your own repositories
The Free plan connects three repositories and needs no card. Nothing is imported, and nothing in GitHub changes.
Other 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.rohan-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.rohan-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.
Recorded in rohan-platform/research/category-and-table-stakes.md and rohan-platform/research/portals-and-feedback-tools.md. GitHub Projects is a trademark of its owner; Pealboard is not affiliated with it.