← Back to home
Comparison · PM

SmartSuite vs Wakapi

A side-by-side editorial comparison of SmartSuite and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.

SmartSuite vs Wakapi: at a glance

FeatureSmartSuiteWakapi
SectorPMPM
Velocity score5.02.5
Sparks · 30d00
Top themeswork-management, mobile-parity, ai-agents, formstime-tracking, self-hosted, oidc, auth-bypass
Last editorial update3d ago48m ago
WebsiteVisit →

What is SmartSuite?

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.

Read the full SmartSuite trajectory →

What is Wakapi?

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.

Read the full Wakapi trajectory →

SmartSuite vs Wakapi: editorial side-by-side

S5.0

SmartSuite is closing the gap between its mobile app and its desktop product, screen by screen.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

W2.5

A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to SmartSuite and Wakapi

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.

See all SmartSuite alternatives → · See all Wakapi alternatives →

Recent activity from SmartSuite and Wakapi

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 6h agoWakapiCritical auth bypass from a shared cache key namespace
  2. 4d agoSmartSuiteAssign and @-Mention Teams in Comments and Checklists
  3. 4d agoSmartSuiteMobile: Internal Forms Support
  4. 4d agoSmartSuiteMobile: Shared Forms Support
  5. 12d agoSmartSuiteAI Field Agent: Address Field Support
  6. 12d agoSmartSuiteAI Field Agent: Date Field Support
  7. 12d agoSmartSuiteMobile: Chart Widget Support
  8. 1mo agoWakapiRelease 2.17.5
  9. 2mo agoWakapiRelease 2.17.4
  10. 4mo agoWakapiSecurity fix, relay endpoint dropped, summaries may need regenerating
  11. 5mo agoWakapiDistroless nonroot container image; SQLite permissions need fixing
  12. 6mo agoWakapiOIDC-only login mode disables local accounts

Frequently asked questions

What is the difference between SmartSuite and Wakapi?

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.

Is SmartSuite better than Wakapi?

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.

What are the best alternatives to SmartSuite?

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.

What are the best alternatives to Wakapi?

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.