Process Street
Process Street's public feed is an SEO content engine, not a changelog.
A side-by-side editorial comparison of MeisterTask and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
MeisterTask is wiring itself into AI assistants while filling in the admin features enterprises expect
MeisterTask ships small, clearly-labelled changes every few weeks — NEW or IMPROVED, one feature at a time. The spring run covered two distinct fronts: an MCP server that exposes projects, tasks and notes to AI assistants, and team workload plus capacity planning tools gated to Business and Enterprise plans. Everything since has been consolidation, including tables in Note, watcher automation, checklist item copying, and universal search reaching the mobile app.
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.
MeisterTask ships small, clearly-labelled changes every few weeks — NEW or IMPROVED, one feature at a time. The spring run covered two distinct fronts: an MCP server that exposes projects, tasks and notes to AI assistants, and team workload plus capacity planning tools gated to Business and Enterprise plans. Everything since has been consolidation, including tables in Note, watcher automation, checklist item copying, and universal search reaching the mobile app.
The product is being extended at both ends of its user base. Upward, workload widgets and a cross-project capacity planner are the features that let it be sold to teams currently choosing heavier tools, and the plan gating makes that intent explicit. Outward, the MCP server treats AI assistants as a new client surface alongside web and mobile. The remaining work reads as parity-closing — mobile catching up to desktop search, Note gaining tables, automations reaching one more field — which is the shape of a product tidying its edges rather than opening a new one.
Automation coverage has expanded one trigger and one field at a time, so the next additions will most likely follow that pattern rather than arrive as a redesign. With the MCP server shipped, the open question the entries do not answer is whether it stays read-and-write across all plan tiers or becomes another Business-and-above feature.
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 MeisterTask 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 MeisterTask 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. MeisterTask 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. MeisterTask 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 MeisterTask alternatives in PM are ranked by recent ship velocity. Browse the "MeisterTask alternatives" section above for the current picks, or visit /alternatives/meistertask 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.