Project Management & Collaboration
ZenHub
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by ZenHub · www.zenhub.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
ZenHub at a glance
- Vendor
- ZenHub
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 3 Nov 2026
- Panel verdict
- The AI panel rates ZenHub 3/5, the mean of 6 judges. ZenHub is a project management and collaboration product built around GitHub, scoring highest on collaboration depth — a flat 8 — on company-wide timelines, directional dependencies across hierarchy levels, and custom roles and permissions. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
ZenHub is a project management and collaboration product built around GitHub, scoring highest on collaboration depth — a flat 8 — on company-wide timelines, directional dependencies across hierarchy levels, and custom roles and permissions. Integrations scores 6-7 on the strength of the developer surface: a GraphQL API with read and write, signature-validated webhooks and an MCP server for AI clients, though the documented native integrations are GitHub and Slack. Reporting scores 6-7 on a fixed catalogue — Release Report, Lead & Cycle Time, Team Velocity, velocity-based forecast end dates — and we found no public information on budget or utilization reporting, dashboards or scheduled delivery. Sovereignty is the one flagged split, spanning 2 to 6 — the widest range of any criterion: on-premise and private cloud deployment behind your firewall is documented, but we found no public information on legal jurisdiction, data residency, a DPA or subprocessors, and the judges weigh that control differently. Support documentation scores 6-7; we found no public information on support channels, response times or SLAs. Pricing transparency scores 2-3; we found no public information on any paid-tier figure.
Speaks for it
- Collaboration depth holds at 8, on company-wide timelines spanning every workspace and directional dependencies drawn across hierarchy levels.
- A GraphQL API with read and write, signature-validated webhooks, published rate limits and an MCP server exposes the product's data to AI clients.
- Teammates without a ZenHub account can create issues and comment on synced Slack threads.
- A free tier, an interactive demo and default pipelines get a GitHub-native team started without a sales call.
- The help center is current and detailed, with a changelog entry dated 8 September 2026 and enterprise release notes listing supported GitHub Enterprise versions.
Held against it
- A shared Timeline link requires a ZenHub account to view, so outside collaborators are routed through Slack.
- We found no public information on support channels, response times or SLAs, by plan or otherwise.
- We found no public information on budget or utilization reporting, dashboards or scheduled delivery beyond the three named reports.
- Beyond GitHub and Slack, we found no public information on native connectors for calendar, Teams, file storage or automation platforms.
- We found no public information on legal jurisdiction, data residency, a DPA or subprocessors, though on-premise and private cloud deployment is documented.
Best for
- Your engineering team already works in GitHub and wants planning boards, timelines and reporting layered onto existing repositories and issues.
- You want to build custom automations or AI tooling on a documented GraphQL API, webhooks and an MCP server.
- You need to deploy on-premise or in a private cloud behind your own firewall, in Kubernetes or virtual-machine form.
- You plan across many teams and need a company-wide view of projects and epics from every workspace.
Avoid if
- You must clear a procurement or data-protection review with a documented DPA, legal jurisdiction and subprocessor list in hand.
- You need to share timeline views with outside stakeholders who will not hold ZenHub accounts.
- Your stack depends on native connectors beyond GitHub and Slack, the only deep integrations the pages document.
- Your reporting needs run to budget, utilization or scheduled delivery rather than the three named reports.
The scores
| Criterion | Panel median |
|---|---|
| Collaboration depth | 4 of 5 |
| Reporting | 3.5 of 5 |
| Integrations | 3.5 of 5 |
| Onboarding effort | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Support & documentation | 3 of 5 |
Collaboration depth
Show reasoningHide reasoning
How this is scored
How much real multi-person project work the tool carries: shared planning, assignments, dependencies, workload, comments, guest access.
0 — A personal task list; a second user has no defined place in it.
3 — Tasks can be shared and assigned, but planning stays per-person — no shared timeline, workload or dependency view.
5 — Solid shared projects with assignments, comments and at least one team-level planning view; gaps appear in cross-project or capacity planning.
8 — Team-level planning is first-class: cross-project views, workload/capacity, dependencies, guest or client access with sane permissions.
10 — Handles the full span from two freelancers to a structured department in one model — planning, capacity, permissions and client involvement all without workarounds.
The Data Protection Officer
Team-level planning is first-class: a company-wide timeline shows projects and epics across every workspace in the GitHub organization, dependencies draw as directional lines across hierarchy levels, and enterprise capacity planning and sprint automation are documented. Assignment, bulk actions, shareable saved views and role-based permissions are all evidenced. Slack synced threads let teammates without a Zenhub account take part, though a timeline share link still requires an account — client access is narrow but sane. 2 3 4 7
The Bootstrapper
Company-wide cross-workspace timelines, directional dependencies across hierarchy levels, custom roles, bulk reassignment and shareable saved views make team-level planning first-class, and Slack lets people without a Zenhub account participate. I stop short of the top because capacity planning is positioned as an enterprise-grade practice and outside involvement runs through Slack rather than client-facing guest permissions. 1 2 3 4 7
The Enterprise Architect
Team-level planning is first-class: a company-wide tab shows projects and epics across every workspace, dependencies draw as directional blocking lines across hierarchy levels, and capacity planning plus multi-project workspaces arrive as enterprise-grade features, with custom roles keeping sensitive work restricted. The soft spot is external sharing — a Timeline share link requires a Zenhub account — though Slack thread sync does let account-less teammates comment on issues. 1 2 3 4 7
The UX Purist
Team-level planning is documented as the core of the product: a company-wide timeline spanning every workspace in the GitHub organization, cross-level dependencies drawn as directional lines, capacity planning and sprint automation on the enterprise tier, plus custom roles, audit logs and multi-project workspaces. Assignments, story points, bulk multi-select edits and saved shareable views are all in the board docs, and Slack teammates can comment into issues without a Zenhub account. We found no public information on a guest or client seat with its own permissions inside a workspace, which is what separates this from the very top. 1 2 3 4 7
The Integrator
Team-level planning is first-class: dependencies render as directional lines across hierarchy levels, a company-wide tab shows projects and epics from every workspace in the organization, capacity planning and sprint automation ship in the enterprise tier, and custom roles plus SSO/SAML/LDAP gate who sees what. Slack teammates without a Zenhub account can create issues and comment on synced threads, though a shared Timeline link still requires a login. 2 3 4 7
The Skeptic
Here the product docs, not the marketing, carry the weight: dependencies draw directional blocking lines on the timeline, a company-wide tab aggregates every workspace's projects in one view, and custom roles and permissions gate sensitive work. Capacity planning, though, appears only as a homepage bullet promising enterprise-grade practice, and the shared timeline link requires a Zenhub account to view — outside collaborators get a Slack side door, not a front door. 1 2 3 4 7
Reporting
Show reasoningHide reasoning
How this is scored
Whether the tool can answer questions about the work: progress, time, budgets, utilization — and export the answer.
0 — No reporting beyond looking at the board.
3 — Fixed per-project status views only; nothing aggregates across projects and nothing exports cleanly.
5 — Useful standard reports (progress, tracked time) with basic filters and CSV export, but limited customization and no budget/utilization depth.
8 — Configurable cross-project reporting incl. time, budgets and utilization, with dashboards and reliable exports.
10 — Reporting is a product in itself: custom report builder, scheduled delivery, API access to every metric the UI shows.
The Data Protection Officer
Reports run on live GitHub data — Release Report, Lead & Cycle Time and Team Velocity, now filterable and combinable by issue type with exclusions — and the timeline computes completion percentages and velocity-based predicted end dates that update automatically, with PNG, SVG and CSV exports. I found no public information on budget or utilization reporting or a custom report builder, which keeps this under the top band. 1 4 5
The Bootstrapper
Release Report, Lead & Cycle Time and Team Velocity with combinable and exclusionary filters, CSV/PNG/SVG export, and velocity-based predicted end dates put this above standard status reporting. We found no public information on budgets, utilization, a custom report builder or scheduled delivery, so it does not reach fully configurable cross-project reporting. 1 4 5
The Enterprise Architect
Release Report, Lead & Cycle Time and Team Velocity take multi-select and exclusion filters, Timeline offers four progress calculation modes plus velocity-based forecast end dates, and PNG/SVG/CSV export with a read/write API gets the numbers out — including an Engineering Investment Report for strategic analysis. We found no public information on budget, utilization or time reporting, nor on dashboards or scheduled delivery, which caps it below the top anchors. 1 4 5 6
The UX Purist
Named reports — Release Report, Lead & Cycle Time, Team Velocity — take combinable multi-select filters including exclusions, and Timeline turns live GitHub activity into progress percentages with four calculation modes, velocity-based predicted end dates, and PNG, SVG and CSV exports scoped by date, project or epic. An Engineering Investment Report extends this into resource-allocation analysis. We found no public information on budget or utilization reporting, a custom report builder, or scheduled delivery. 1 4 5
The Integrator
Standard reports (Release Report, Lead & Cycle Time, Team Velocity) gained multi-select issue-type filters with exclusions, and Timeline offers progress calculation modes with PNG, SVG and CSV exports filtered by date range, project or epic. We found no public information on budget or utilization reporting, dashboards or scheduled delivery; the GraphQL API is a data pipe, not a report builder. 1 4 5
The Skeptic
Three named reports — Release Report, Lead & Cycle Time, Team Velocity — take issue-type filters with exclusions, the timeline computes progress four ways from live GitHub activity and forecasts end dates from historical velocity, and views export to PNG, SVG or CSV. It stays a fixed catalogue: we found no public information on budget or utilization reporting, dashboards, or scheduled delivery, and the Engineering Investment Report is a one-line promise with no documented shape — even time tracking is framed as an outside tool teams sync via the API. 1 4 5 6
Integrations
Show reasoningHide reasoning
How this is scored
How well the tool connects to the rest of the stack: native integrations, calendar/comms hooks, API and webhooks, import/export paths.
0 — A closed box — no API, no integrations, CSV out if anything.
3 — A handful of marquee integrations, no public API or an API that covers a fraction of the product.
5 — The common set (calendar, Slack/Teams, file storage) plus a documented public API; automation platforms partially covered.
8 — Broad native catalogue, well-documented API and webhooks, first-class automation-platform support and real import paths from competitors.
10 — Ecosystem-grade: everything in 8 plus the tool is itself extensible (apps/plugins, AI/MCP surfaces) and exit via API export is complete.
The Data Protection Officer
The connection surface is strong where documented: native operation inside GitHub, a deep Slack integration with two-way thread sync and issue creation, and a GraphQL API with read and write operations, an API explorer, signature-validated webhooks and an MCP server for AI clients. I found no public information on a broader native catalogue such as calendar, Teams or file storage, nor on automation-platform support or import paths from competitors. 2 6 7
The Bootstrapper
The developer surface is strong: documented GraphQL with read and write, webhooks with signature validation, an API explorer, an MCP server for AI clients, plus deep native GitHub and Slack integrations. The visible native catalogue is narrow — we found no public information on calendar, Teams, file storage, automation platforms, or import paths from competitors. 1 6 7
The Enterprise Architect
GitHub is native to the point of the product living inside it, Slack syncs two-way with issue threads, and the GraphQL API ships with real operational polish — webhooks with signature validation, rate limiting, service-account tokens, an API explorer and even an MCP server for AI clients. The documented native catalogue stops at those two connectors, and we found no public information on calendar, Teams, file-storage connectors or import paths from competing tools. 1 2 6 7
The UX Purist
The developer surface is first-rate: a documented GraphQL API with read and write, an API Explorer, documented rate limiting and token management, webhooks with signature validation, and an MCP server exposing the data to AI clients like Claude Code, Cursor and Gemini CLI. Native connections documented are GitHub (the product is built inside it), Slack with real-time two-way thread sync, and Linear and meeting activity ingested through Thor. The native catalogue documented is narrow, and we found no public information on calendar, Teams, file storage or automation-platform connectors. 1 2 6 7
The Integrator
This is where the stack story holds up: a documented GraphQL API with read and write operations, an API Explorer, published rate limits, and webhooks firing on issue creation, modification and pipeline moves with signature validation — plus an MCP server wrapping the API for Claude Code, Cursor, Windsurf and Gemini CLI, which is ahead of most of the field. Slack syncs two-way between issues and threads, but the evidenced native catalogue is otherwise GitHub-plus-Slack, and we found no public information on automation platforms or import paths from competing tools. 1 6 7
The Skeptic
The developer surface is the strongest thing here: a documented GraphQL API with read and write, an API explorer, webhooks with signature validation, disclosed rate limiting, and an MCP server exposing the data to AI clients. Native breadth is what I cannot verify — the captured pages name exactly two integrations, GitHub and Slack (deep ones, with two-way thread sync), and we found no public information on calendar or storage hooks, named automation platforms, or import paths from competing trackers. 1 2 6 7
Onboarding effort
Show reasoningHide reasoning
How this is scored
Time and friction from signup to first real value for a small team, without paid services.
0 — No self-serve path — onboarding starts with a sales call and an implementation project.
3 — Self-serve exists but the first project requires configuration a newcomer cannot judge yet (workflows, custom fields, permissions) before anything works.
5 — A team gets a first project running within a day; trial requires payment details or key steps live behind docs.
8 — Signup to working project inside an hour: guided setup, sensible defaults, templates, trial without payment details.
10 — Minutes to value even for non-tool-people, importers pull existing work in, and the tool teaches its own advanced features as the team grows into them.
The Data Protection Officer
A team can start for free without payment details, try an interactive demo, and work natively inside GitHub where developers already are; the board ships with a sensible default pipeline structure and invited teammates see their organization invitations during registration. Getting Started and Troubleshooting areas exist. I found no public information on templates or guided setup flows, which holds this under the fastest tier. 1 3 8
The Bootstrapper
A free self-serve start, an interactive demo, sensible default pipelines and an invite flow where new members join during registration mean a GitHub-based team can plausibly be working within the hour. We found no public information on in-product guided setup or templates, which is what minutes-to-value would require. 1 3 8
The Enterprise Architect
A free tier, an interactive demo, sensible default pipelines a newcomer can work with immediately, and an invite flow that surfaces the invited organizations during registration get a small team started without a sales call. We found no public information on guided setup, project templates or importers that would shorten the path further. 1 3 8
The UX Purist
A GitHub team gets value fast: a "Start for free" entry point, an interactive demo before signup, default pipelines from New Issues through Closed ready without configuration, and an invite flow that surfaces pending organization invitations during registration. The board manages GitHub issues natively, so existing repo work is in the product from the start rather than imported, and Thor converts Slack, meeting and Linear activity into tracked work. We found no public information on guided setup wizards or project templates. 1 2 3 8
The Integrator
A free tier, an interactive demo, and sensible default pipelines mean a GitHub-native team gets a populated board from existing issues almost immediately, and invitees see their organization invitations during registration. We found no public information on guided setup flows, templates, or trial mechanics beyond the free tier, so I cannot place it higher. 1 3 8
The Skeptic
Self-serve demonstrably exists: a free tier, an interactive demo, an out-of-the-box pipeline set, and an invite flow that surfaces pending organizations during registration. But we found no public information on how fast a team reaches a working project, whether the trial asks for payment details, or whether templates or importers exist — and the only onboarding-specific help article captured is dated December 2022, the oldest page in the set. 1 3 8
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Where the company and the data actually sit: legal entity, ownership control, data residency, and subprocessor exposure to non-EU jurisdictions.
0 — Non-European vendor, data on US infrastructure under US law, no DPA worth the name.
3 — DPA and GDPR language present, but hosting defaults to the US or ownership sits outside Europe — compliance paperwork over substance.
5 — EU data residency is available and contractually fixed, but the vendor or its controlling owner is non-European, or core subprocessors put data within CLOUD Act reach.
8 — European company under European control with EU-resident data and a public DPA; remaining exposure is limited to identifiable subprocessors (e.g. a US hyperscaler's EU region) and is documented.
10 — European company, European control, EU-only data residency on European infrastructure, subprocessor list free of extraterritorial reach — verifiable, not asserted.
The Data Protection Officer
Self-hosting is documented and real: the enterprise pages state the product can be fully deployed behind your firewall or in your preferred private cloud for complete data sovereignty, with Kubernetes and virtual-machine deployment types. Beyond that I found no public information on the vendor's legal seat, a data processing agreement, cloud data residency or the subprocessor list — for the hosted offering the captured pages leave the question of where the data lives unanswered. 1 2
The Bootstrapper
The enterprise page documents on-premise and private-cloud deployment "behind your firewall or in your preferred private cloud for complete data sovereignty", a real control mechanism and the only thing the captured pages prove. Legal jurisdiction, cloud data residency, a DPA and subprocessor exposure are all unknown to me, so I cannot place this vendor as European or otherwise and score only the self-hosted path. 1 2
The Enterprise Architect
On-premise and private-cloud deployment — Kubernetes or virtual machines, fully behind our firewall — hands data residency and infrastructure control entirely to the buyer, which is the strongest data-position control available. But the captured pages give no DPA, no legal-entity jurisdiction and no subprocessor list, so the contractual side of a European sovereignty assessment is unverified and would not clear procurement as documented. 1 2
The UX Purist
The enterprise pages document genuine deployment control — on-premise or private cloud behind your own firewall, with Kubernetes and virtual-machine deployment types — so self-hosting customers decide where their data sits. We found no public information on the vendor's legal jurisdiction, ownership, a data-processing agreement, or subprocessors, so the standard cloud offering cannot be assessed from the captured pages, and deployment control is all the evidence carries. 1 2
The Integrator
On-premise and private-cloud deployment behind your own firewall is documented, with Kubernetes and virtual-machine deployment types and an upgrade path from VM to Kubernetes, which puts data residency in the customer's hands. We found no public information on the vendor's legal jurisdiction, ownership, DPA, TIA or subprocessor exposure on the captured pages, so the corporate side of sovereignty rests unproven. 1 2
The Skeptic
The one verifiable claim is deployment control: on-premise or private cloud behind your own firewall, in Kubernetes or virtual-machine flavors, which genuinely moves the data into your hands. For everything else a sovereignty assessment needs we found no public information — company jurisdiction, ownership, a DPA, a subprocessor list, where the standard cloud service stores data — so "complete data sovereignty" on the enterprise page is an assertion I cannot check. 1 2
Support & documentation
Show reasoningHide reasoning
How this is scored
Whether a stuck user gets unstuck: docs quality, support channels and their availability per plan, and the health of the learning surface.
0 — No docs beyond marketing pages; support is a contact form that may answer.
3 — Docs exist but are thin or stale; support on entry plans is effectively email-only with slow turnaround.
5 — Searchable help center covering the core product; chat or email support on all plans with reasonable response times.
8 — Deep, current docs incl. onboarding guides and templates; fast chat support not gated to top tiers; visible changelog.
10 — Docs, academy, community and support so good they are a reason to buy; SLAs published, support quality independent of plan.
The Data Protection Officer
The help center is demonstrably alive: deep articles on the board, timeline planning, reporting, the API and Slack, a product changelog updated in September 2026, and enterprise release notes listing supported GitHub Enterprise versions, plus developer-facing API documentation with an explorer. I found no public information on support channels, response times or service-level commitments per plan, so a stuck user's path to a human is undocumented. 1 2 5 6
The Bootstrapper
The help articles are deep and current — a filter changelog updated 8 Sep 2026, a visible product changelog, enterprise release notes, and API documentation with an explorer. We found no public information on support channels, response times or SLAs per plan, which caps this below the strong tier. 1 2 5 6
The Enterprise Architect
The help center runs deep and current — detailed Timeline, board, API and Slack guides, a changelog updated this month, and enterprise release notes that even pin supported GitHub Enterprise versions — plus a dedicated developer site. We found no public information on support channels, response times or SLAs, which is what I would need documented before committing two hundred seats. 1 2 5 6
The UX Purist
The help center is deep and visibly maintained: substantive articles on the board, timeline, API and Slack integration; a product changelog with an entry dated 8 September 2026; enterprise release notes tracking supported GitHub Enterprise versions; a Getting Started section; and full API documentation at developers.zenhub.com. We found no public information on support channels, response times, or how support availability differs by plan, which the captured pages leave unanswered. 1 2 5 6
The Integrator
The help center is granular and demonstrably current — the September 2026 issue-type filter change was documented as it shipped, and enterprise release notes track GitHub Enterprise version compatibility. We found no public information on support channels, response times or SLAs per plan, which keeps this below the top tier. 1 2 5
The Skeptic
The documentation is alive and detailed: how-to articles with Q&A and tips across the board, API docs with an explorer, enterprise release notes, and a product changelog with a September 2026 update two months before capture. We found no public information on support channels — no chat, no response times, no SLAs, nothing broken down by plan — so the help center earns this score alone. 1 5 6
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Can a buyer determine the real, payable cost of the tool for their team before talking to anyone?
0 — No public pricing at all — every number sits behind "contact sales".
3 — Some tiers are public, but a deciding factor (seat minimums, mandatory add-ons, billing-period surcharge, tax treatment) only surfaces at checkout or in fine print.
5 — Self-serve tiers are publicly priced and the billing-period difference is stated, but the headline number still needs qualifying — e.g. annual-only headline, taxes excluded without saying so, or an opaque enterprise tier doing real work.
8 — Every self-serve tier is fully priced with billing periods and tax treatment plain on the page; only genuinely custom enterprise work lacks a number.
10 — Every tier including enterprise has a public price or published price formula, and the headline number is the number on the invoice.
The Data Protection Officer
The captured pages show only that a team can "Start for free" and that an Enterprise plan exists under Pricing; I found no public information on any price figures for paid plans, seat minimums or billing-period differences. A buyer cannot determine the payable cost for their team from these pages and would need to talk to sales. 1
The Bootstrapper
The only price visible on the captured pages is "Start for free"; we found no public information on paid seat prices, billing periods, seat minimums or an enterprise number. I cannot determine what three seats or thirty cost before talking to someone, which fails my basic test. 1
The Enterprise Architect
The captured pages state a free tier exists and name an Enterprise plan, but carry no price, billing period or tax treatment for any paid tier — "Start for free" is the only cost statement published. For a two-hundred-seat purchase I would be entering negotiation entirely blind, which fails my first procurement gate. 1
The UX Purist
The captured pages confirm a "Start for free" entry point, an Enterprise plan, and a Pricing page in the navigation, but give no figures for any paid tier, billing period, or tax treatment. A buyer cannot determine a payable cost for their team from the captured pages. 1
The Integrator
A free tier is public and a pricing page exists in the navigation, but the captured pages carry no figures for any paid tier and the enterprise tier has no number attached. A buyer cannot determine the payable cost for their team from the pages we read. 1
The Skeptic
Everything the captured pricing material shows is a "Start for free" button and navigation links labeled Pricing and Enterprise; not one paid tier carries a figure. We found no public information on seat prices, billing periods, seat minimums, or tax treatment — a buyer cannot determine what a ten-person team pays without asking the vendor. 1
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about ZenHub
Is ZenHub European?
Not determined: the vendor’s pages as captured do not say where ZenHub is based.
Where does ZenHub store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does ZenHub have a free plan?
Yes. ZenHub has a free plan, per the vendor’s page captured 3 Nov 2026.
What are the best alternatives to ZenHub?
As of 3 Nov 2026, the panel rates awork (4/5), InLoox (4/5) and Kantree (4/5) highest among the other 64 Project Management & Collaboration products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is awork (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: ZenHub alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.zenhub.com Checked 3 Nov 2026 Details →
- 2 Self-hosting / on-premises installation docs — found from the homepage www.zenhub.com Checked 3 Nov 2026 Details →
- 3 Collaboration depth — found from sitemap support.zenhub.com Checked 3 Nov 2026 Details →
- 4 Reporting — found from sitemap support.zenhub.com Checked 3 Nov 2026 Details →
- 5 Reporting — found from sitemap support.zenhub.com Checked 3 Nov 2026 Details →
- 6 Integrations — found from sitemap support.zenhub.com Checked 3 Nov 2026 Details →
- 7 Integrations — found from sitemap support.zenhub.com Checked 3 Nov 2026 Details →
- 8 Onboarding effort — found from sitemap support.zenhub.com Checked 3 Nov 2026 Details →