← Back to home
Comparison · PM

Productboard vs Wakapi

A side-by-side editorial comparison of Productboard and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.

Productboard vs Wakapi: at a glance

FeatureProductboardWakapi
SectorPMPM
Velocity score5.02.5
Sparks · 30d00
Top themesapi, developer-platform, product-management, integrationstime-tracking, self-hosted, oidc, auth-bypass
Last editorial update29d ago3h ago
WebsiteVisit →Visit →

What is Productboard?

Productboard is methodically making its customer-insight data programmable through a v2 API build-out.

Productboard's public activity is a steady stream of v2 REST API additions. The recent window closes v1 parity gaps (fulltext note search, team and note-type filters, custom-field filtering with an isSet presence check, source metadata for CRM matching) and adds net-new surface — a beta endpoint returning an aggregated customer score for any product-hierarchy entity. The work is developer-platform, not end-user UI.

Read the full Productboard trajectory →

What is Wakapi?

A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.

Wakapi's recent releases cluster around identity and deployment rather than time tracking itself: OpenID Connect login, then an OIDC-only mode, multiple API keys per user, and a switch from Alpine to a distroless nonroot container image. The 2.17.x line has carried two security fixes now — a responsibly disclosed issue in 2.17.3, and a critical authentication bypass in 2.17.6 caused by a shared cache key namespace. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.

Read the full Wakapi trajectory →

Productboard vs Wakapi: editorial side-by-side

P5.0

Productboard is methodically making its customer-insight data programmable through a v2 API build-out.

◆ Current state

Productboard's public activity is a steady stream of v2 REST API additions. The recent window closes v1 parity gaps (fulltext note search, team and note-type filters, custom-field filtering with an isSet presence check, source metadata for CRM matching) and adds net-new surface — a beta endpoint returning an aggregated customer score for any product-hierarchy entity. The work is developer-platform, not end-user UI.

◆ Where it's heading

The throughline is making Productboard's prioritization and customer-insight data fully queryable and integrable via API. Reaching and exceeding v1 parity, then exposing scoring data, points toward Productboard positioning its data as a programmable layer other systems build on, not just a UI to visit. This deepens an integration strategy rather than changing product direction.

◆ Prediction

Expect continued v2 endpoint expansion toward eventual v1 deprecation, with more prioritization and scoring signals exposed for CRM, analytics, and internal tooling integrations.

W2.5

A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.

◆ Current state

Wakapi's recent releases cluster around identity and deployment rather than time tracking itself: OpenID Connect login, then an OIDC-only mode, multiple API keys per user, and a switch from Alpine to a distroless nonroot container image. The 2.17.x line has carried two security fixes now — a responsibly disclosed issue in 2.17.3, and a critical authentication bypass in 2.17.6 caused by a shared cache key namespace. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.

◆ Where it's heading

The direction is a self-hosted tool making itself deployable somewhere other than one developer's server. External identity providers, an option to disable local login entirely, per-key credentials and a container that runs as a nonroot user are the requirements that come from someone else's security review. The 2.17.6 bypass sits awkwardly against that: a cache keyed without proper namespacing is exactly the class of bug that multi-tenant deployment surfaces, which suggests the auth work is now being exercised harder than the code was written for. Releases have also thinned to roughly one a month from a much faster earlier cadence.

◆ Prediction

The identity and packaging thread is the only sustained one in this feed, so further hardening in that area is the most likely continuation; the sparse release notes make anything more specific guesswork.

Alternatives to Productboard and Wakapi

Other PM products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Productboard or Wakapi.

See all Productboard alternatives → · See all Wakapi alternatives →

Recent activity from Productboard and Wakapi

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 9h agoWakapiCritical auth bypass from a shared cache key namespace
  2. 1mo agoProductboardv2 - 2026-07-20 - Customer score for entities (Beta)
  3. 1mo agoWakapiRelease 2.17.5
  4. 1mo agoProductboardv2 - 2026-07-02 - Fulltext search for notes
  5. 1mo agoProductboardv2 - 2026-06-29 - Company source metadata available
  6. 2mo agoProductboardv2 - 2026-06-18 - Custom field presence filter
  7. 2mo agoProductboardv2 - 2026-06-15 - Filter entities by team
  8. 2mo agoProductboardv2 - 2026-06-09 - Filter notes by type
  9. 2mo agoWakapiRelease 2.17.4
  10. 4mo agoWakapiSecurity fix, relay endpoint dropped, summaries may need regenerating
  11. 5mo agoWakapiDistroless nonroot container image; SQLite permissions need fixing
  12. 6mo agoWakapiOIDC-only login mode disables local accounts

Frequently asked questions

What is the difference between Productboard and Wakapi?

They serve adjacent needs but don't currently overlap on shipped themes. Productboard is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Productboard better than Wakapi?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Productboard is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other PM products to evaluate alongside.

What are the best alternatives to Productboard?

Top Productboard alternatives in PM are ranked by recent ship velocity. Browse the "Productboard alternatives" section above for the current picks, or visit /alternatives/productboard for the full list with editorial commentary on each.

What are the best alternatives to Wakapi?

Top Wakapi alternatives in PM are ranked by recent ship velocity. Browse the "Wakapi alternatives" section above for the current picks, or visit /alternatives/wakapi for the full list with editorial commentary on each.