Tracecat
Tracecat's 1.3 alphas keep reworking agent plumbing: tunnels, multi-org MCP, pluggable runners.
A side-by-side editorial comparison of Fibery and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Fibery's MCP server can now upload local files, so AI assistants can attach screenshots and images.
Fibery's October 22 release is small: rich text accepts multiple files at once, with new upload and upload-by-link options, and the MCP server lets an AI assistant upload files from the user's computer into file fields or rich text. It follows three heavier releases: AI-built custom integrations, Custom Apps as entity views, and a rebuilt AI agent.
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.
Fibery's October 22 release is small: rich text accepts multiple files at once, with new upload and upload-by-link options, and the MCP server lets an AI assistant upload files from the user's computer into file fields or rich text. It follows three heavier releases: AI-built custom integrations, Custom Apps as entity views, and a rebuilt AI agent.
Fibery is making AI the main builder and operator of the workspace: the agent, Custom Apps, AI-generated integrations and an MCP server that now handles code execution and files. The weekly cadence alternates big AI releases with quality-of-life updates like this one.
Expect the custom-integration preview to widen and the MCP server to gain more write actions; another large AI release is likely within a few weeks given the pattern.
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.
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.
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.
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 Fibery or Wakapi.
Tracecat's 1.3 alphas keep reworking agent plumbing: tunnels, multi-org MCP, pluggable runners.
NocoBase's Runner Agent gets conversation management, task links and agent switching mid-thread.
Camunda opens the 8.11 cycle with job-worker fixes and variable metadata across gRPC, REST and MCP.
Todoist's 2026 bets are on capture: voice via Ramble, photos and files via Task Capture.
Atarim's AI experts now propose changes to live pages as drafts, and the app runs on phones.
SmartSuite adds a scheduled JavaScript runtime with secrets and run history.
See all Fibery alternatives → · See all Wakapi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fibery is currently shipping more aggressively (velocity 7.5 vs 2.5), with 2 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fibery is currently shipping more aggressively (velocity 7.5 vs 2.5), with 2 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.
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.
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.