NocoBase
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
A side-by-side editorial comparison of Process Street and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Process Street's public feed is an SEO content engine, not a changelog.
Nothing in this feed reports a product change. It runs a steady daily-ish cadence of evergreen business content — risk management primers, business writing advice, an MBTI personality explainer, a compliance audit walkthrough — interleaved with lead-generation assets built around free Process Playbook checklists and product how-tos like an employee onboarding automation guide. The one item with substance behind it is a customer story on a healthcare practice cutting insurance appeals prep from 15 minutes to under 2, which reads as a compliance-ops proof point rather than a release.
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.
Nothing in this feed reports a product change. It runs a steady daily-ish cadence of evergreen business content — risk management primers, business writing advice, an MBTI personality explainer, a compliance audit walkthrough — interleaved with lead-generation assets built around free Process Playbook checklists and product how-tos like an employee onboarding automation guide. The one item with substance behind it is a customer story on a healthcare practice cutting insurance appeals prep from 15 minutes to under 2, which reads as a compliance-ops proof point rather than a release.
The company positions itself as a compliance operations platform in its own feed signature, and the content is being steered to match: PHI handling, appeals packets, audit readiness, risk assessment and controls now sit alongside the older generic productivity material. Some of that older material is being recirculated rather than retired — a 2021 milestone retrospective carries a current date in this window, so the feed is partly an archive re-dump. Product direction cannot be read here at all.
Expect more compliance and regulated-industry content to displace the generic productivity posts, but this feed will keep carrying no release information, so any actual product movement will have to be observed elsewhere.
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 Process Street or Wakapi.
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.
Apploye's feed is an SEO blog, and its running theme is defending monitoring on privacy grounds.
See all Process Street 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. Process Street 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Process Street 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.
Top Process Street alternatives in PM are ranked by recent ship velocity. Browse the "Process Street alternatives" section above for the current picks, or visit /alternatives/process-st 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.