Process Street
Process Street's public feed is an SEO content engine, not a changelog.
A side-by-side editorial comparison of Planify and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
A GNOME task app that has turned CalDAV interoperability into the product.
Planify is a GTK task manager for GNOME on a fast release train — six releases in the window shown, most of them sync work. The 4.19 line spent nearly all its effort making CalDAV survive real servers: Mailbox.org, Open-Xchange, Posteo, Nextcloud Deck, and DAVx5 on Android each got a named fix. Feature work still lands, but alongside the sync repairs rather than instead of them.
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.
Planify is a GTK task manager for GNOME on a fast release train — six releases in the window shown, most of them sync work. The 4.19 line spent nearly all its effort making CalDAV survive real servers: Mailbox.org, Open-Xchange, Posteo, Nextcloud Deck, and DAVx5 on Android each got a named fix. Feature work still lands, but alongside the sync repairs rather than instead of them.
The direction shows in what gets fixed. Planify is positioning as the GNOME client that works against whatever CalDAV server you already run, not a client for one service — sync-token fallbacks, ETag retries, and CDATA parsing are all compatibility debt paid down per-server. The second thread is pushing into the desktop itself: a Shell search provider, system accent color, a CLI. Both are the same bet, that the app's value is behaving well inside an existing setup.
Expect another CalDAV compatibility pass naming a specific server next, since four of the last six releases took that shape. Feature work will most likely extend the backup and section support added in 4.19.2 rather than open a new area.
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 Planify or Wakapi.
Process Street's public feed is an SEO content engine, not a changelog.
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
Hive ships in batches, and this one is all planning accuracy and admin control.
Plane ships a fortnightly digest, and the AI layer is where the real work is going.
Ever Teams shipped ten tags in twelve hours and one of them touched the product
Asana's agent left the app — it now answers work questions inside Slack threads.
See all Planify 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. Planify and Wakapi are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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. Planify and Wakapi are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Planify alternatives in PM are ranked by recent ship velocity. Browse the "Planify alternatives" section above for the current picks, or visit /alternatives/planify 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.