Process Street
Process Street's public feed is an SEO content engine, not a changelog.
A side-by-side editorial comparison of Nimbus and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
FuseBase is pivoting into AI app building while its marketing still sells the old portal category.
The feed tracked here is thefusebase.com — the product trades as FuseBase now — and it carries two unrelated streams. The recent half is competitor-alternative SEO (Quip, Google Docs, Notion Sites, Clinked, Moxo) selling the collaboration and client-portal positioning. The product half, all from May and June, is about something else: FuseBase Flow, FuseBase AI Apps, and an AI Coding module for turning ideas into shippable applications.
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.
The feed tracked here is thefusebase.com — the product trades as FuseBase now — and it carries two unrelated streams. The recent half is competitor-alternative SEO (Quip, Google Docs, Notion Sites, Clinked, Moxo) selling the collaboration and client-portal positioning. The product half, all from May and June, is about something else: FuseBase Flow, FuseBase AI Apps, and an AI Coding module for turning ideas into shippable applications.
The company is moving from a place to store documents and client files toward a place where agents build software, and the Flow launch states it most plainly — phases, slices, reviews and gates imposed on AI-generated projects instead of one overloaded chat. The target is client-facing businesses that want to ship applications without an engineering team. Marketing has not followed the product: every recent post still chases buyers shopping for a Notion or Quip replacement.
Expect the next real releases to keep hardening the AI Coding path — more structure around review, stability and deployment — since that is where every product post in this window concentrates. Whether the listicle engine ever repoints at the AI positioning is unresolved; right now the two halves of this feed address different buyers.
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 Nimbus 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 Nimbus 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. Nimbus 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. Nimbus 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 Nimbus alternatives in PM are ranked by recent ship velocity. Browse the "Nimbus alternatives" section above for the current picks, or visit /alternatives/nimbusweb 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.