Process Street
Process Street's public feed is an SEO content engine, not a changelog.
A side-by-side editorial comparison of Resource Guru and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Resource Guru is teaching its scheduler to place work for you, not just record where you put it
Resource Guru's feed mixes product updates with marketing articles, and the product half has been consistently substantive. Total Hours bookings let a user commit a number of hours across a date range and have the tool fit them around existing commitments, rather than placing each block by hand. Around that sit a run of view-shaping features — colour-coding bookings by custom field, choosing and reordering Projects columns, a daily digest of unassigned placeholder bookings — plus a Trello integration and an MCP server for querying account data from AI tools.
Wakapi is quietly rebuilding itself around the login and container requirements teams ask for.
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 also carried a responsibly disclosed security fix and dropped its relay endpoint. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.
Resource Guru's feed mixes product updates with marketing articles, and the product half has been consistently substantive. Total Hours bookings let a user commit a number of hours across a date range and have the tool fit them around existing commitments, rather than placing each block by hand. Around that sit a run of view-shaping features — colour-coding bookings by custom field, choosing and reordering Projects columns, a daily digest of unassigned placeholder bookings — plus a Trello integration and an MCP server for querying account data from AI tools.
Two threads are running. The scheduler is becoming constraint-aware: the product is moving from a canvas where humans place every block toward one that resolves intent against availability. Separately, the data is being opened up — MCP for natural-language querying, Trello for booking creation from cards — which treats the schedule as something other systems read and write rather than a destination app. The view customisation work is the connective tissue, letting teams shape what they see as the underlying data grows richer.
Expect the automatic-fitting logic behind Total Hours to extend to other booking types, since the hard part is the placement engine rather than the entry form. More integrations in the Trello mould look likely given the MCP groundwork already laid.
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 also carried a responsibly disclosed security fix and dropped its relay endpoint. 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 with no shell are the requirements that come from someone else's security review, not from a hobbyist's wishlist. The corresponding cost is visible too: dropped MSSQL support and a Docker base change that forces SQLite users to fix directory permissions by hand.
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 Resource Guru 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 Resource Guru 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. Resource Guru 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. Resource Guru 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 Resource Guru alternatives in PM are ranked by recent ship velocity. Browse the "Resource Guru alternatives" section above for the current picks, or visit /alternatives/resource-guru 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.