← Back to home
Comparison · PM

Wakapi vs Fibery

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

Wakapi vs Fibery: at a glance

FeatureWakapiFibery
SectorPMPM
Velocity score2.56.3
Sparks · 30d00
Top themestime-tracking, self-hosted, oidc, auth-bypasswork-management, custom-apps, mcp, ai-automation
Last editorial update28d ago5d ago
WebsiteVisit →Visit →

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 →

What is Fibery?

Fibery's Custom Apps go GA, completing its turn from work tracker to embedded app platform

Fibery spent the past quarter building and shipping Custom Apps — AI-generated mini-apps buildable inside the platform via Claude, ChatGPT, or MCP. Custom Apps launched publicly in mid-August after two months of experimental iteration. In the same period, Fibery added AI-driven automation creation, a usage dashboard tracking AI and integration consumption, and expanded MCP coverage to rich text editing and direct Custom Apps authoring. The platform is shipping weekly with a mix of headliner features and steady bug fixing.

Read the full Fibery trajectory →

Wakapi vs Fibery: editorial side-by-side

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.

F6.3

Fibery's Custom Apps go GA, completing its turn from work tracker to embedded app platform

◆ Current state

Fibery spent the past quarter building and shipping Custom Apps — AI-generated mini-apps buildable inside the platform via Claude, ChatGPT, or MCP. Custom Apps launched publicly in mid-August after two months of experimental iteration. In the same period, Fibery added AI-driven automation creation, a usage dashboard tracking AI and integration consumption, and expanded MCP coverage to rich text editing and direct Custom Apps authoring. The platform is shipping weekly with a mix of headliner features and steady bug fixing.

◆ Where it's heading

Fibery is repositioning from a flexible project tracker into a platform where teams build custom tooling on top of their own data, without leaving the workspace. The Custom Apps launch — AI-generated, embeddable in documents, now on a versioned platform — is the clearest statement of that direction. MCP integration at multiple layers (rich text, apps, automations) shows Fibery making itself a first-class target in AI-native workflows rather than bolting on a chat widget.

◆ Prediction

The next likely move is tying Custom Apps directly into Fibery's automation engine — AI-built apps that trigger and respond to automations — which would close the loop between the platform's two main new capability axes. The breaking platform update to Custom Apps in September signals further architectural changes are coming before the feature stabilizes.

Alternatives to Wakapi and Fibery

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 Wakapi or Fibery.

See all Wakapi alternatives → · See all Fibery alternatives →

Recent activity from Wakapi and Fibery

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

  1. 6d agoFiberyHierarchical filter improvements and whiteboard color coding
  2. 13d agoFiberySeptember 3, 2026 / Custom Apps updates, Set a load limit for Lists and Tables on Entity View, Multi-window support in the desktop app
  3. 20d agoFiberyAugust 27, 2026 / Usage dashboard, manually edit custom apps
  4. 27d agoFiberyAugust 20, 2026 / Batch undo, create automations with AI, Views history
  5. 28d agoWakapiCritical auth bypass from a shared cache key namespace
  6. 1mo agoFiberyAugust 13, 2026 / Custom Apps, See how each change was made (UI, API, automation, AI)
  7. 1mo agoFiberyAugust 6, 2026 / Custom Apps improvements, Convert Select field to Database, Update small part of rich text and add comments via MCP
  8. 2mo agoWakapiRelease 2.17.5
  9. 3mo agoWakapiRelease 2.17.4
  10. 5mo agoWakapiSecurity fix, relay endpoint dropped, summaries may need regenerating
  11. 6mo agoWakapiDistroless nonroot container image; SQLite permissions need fixing
  12. 7mo agoWakapiOIDC-only login mode disables local accounts

Frequently asked questions

What is the difference between Wakapi and Fibery?

They serve adjacent needs but don't currently overlap on shipped themes. Fibery is currently shipping more aggressively (velocity 6.3 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 Wakapi better than Fibery?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fibery is currently shipping more aggressively (velocity 6.3 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 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.

What are the best alternatives to Fibery?

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