Process Street
Process Street's public feed is an SEO content engine, not a changelog.
A side-by-side editorial comparison of SmartSuite and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | SmartSuite | Wakapi |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 5.0 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | work-management, mobile-parity, ai-agents, forms | time-tracking, self-hosted, oidc, auth-bypass |
| Last editorial update | 3d ago | 48m ago |
| Website | — | Visit → |
SmartSuite is closing the gap between its mobile app and its desktop product, screen by screen.
SmartSuite is a work management platform combining databases, forms, automation and dashboards. Two systematic campaigns dominate recent releases. Mobile is being brought to parity — shared forms, internal forms and the chart widget all now run natively in the iOS and Android apps rather than falling back to a browser. Separately, AI Field Agents are being extended one target field type at a time, adding Address and Date to the existing Text and Single Select outputs.
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.
SmartSuite is a work management platform combining databases, forms, automation and dashboards. Two systematic campaigns dominate recent releases. Mobile is being brought to parity — shared forms, internal forms and the chart widget all now run natively in the iOS and Android apps rather than falling back to a browser. Separately, AI Field Agents are being extended one target field type at a time, adding Address and Date to the existing Text and Single Select outputs.
Both campaigns are additive rather than exploratory, and both look close to complete. The mobile releases explicitly describe features as previously desktop-only, which reads as a checklist being worked through. The AI Field Agent releases are near-identical in structure, each reusing the same governance, manual and automatic run controls, and audit logging — the agent framework is settled and only its output types are being enumerated. The Teams work follows the same instinct, extending existing Teams Field infrastructure into comments and checklists rather than building something new.
Expect the remaining desktop-only surfaces to land on mobile and further field types to be added as AI Field Agent outputs, since both series have shipped in near-identical batches. Number and Link fields are the obvious unclaimed agent targets.
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 SmartSuite 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 SmartSuite 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. SmartSuite 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. SmartSuite 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 SmartSuite alternatives in PM are ranked by recent ship velocity. Browse the "SmartSuite alternatives" section above for the current picks, or visit /alternatives/smartsuite 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.