← Back to home
Comparison · PM

Super Productivity vs Wakapi

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

Super Productivity vs Wakapi: at a glance

FeatureSuper ProductivityWakapi
SectorPMPM
Velocity score5.02.5
Sparks · 30d00
Top themessync-reliability, e2e-encryption, plugin-platform, local-firsttime-tracking, self-hosted, oidc, auth-bypass
Last editorial update3d ago42m ago
WebsiteVisit →Visit →

What is Super Productivity?

A local-first task manager quietly rebuilding itself into a sync engine with a plugin platform on top.

Super Productivity ships minor releases every week or two where the visible feature work is thin and the real effort sits in sync. Across the last six releases the operation-log sync layer picked up field-level merging of concurrent edits, queued background requests, conflict replay, and encrypted-only enforcement for SuperSync. The plugin system absorbed the Azure DevOps and Trello issue providers and gained OAuth hooks plus local secret storage. Since v18.19.0 in early August the repository has published only working branch tags, so the numbered release stream has been quiet for over a week.

Read the full Super Productivity 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 →

Super Productivity vs Wakapi: editorial side-by-side

S5.0

A local-first task manager quietly rebuilding itself into a sync engine with a plugin platform on top.

◆ Current state

Super Productivity ships minor releases every week or two where the visible feature work is thin and the real effort sits in sync. Across the last six releases the operation-log sync layer picked up field-level merging of concurrent edits, queued background requests, conflict replay, and encrypted-only enforcement for SuperSync. The plugin system absorbed the Azure DevOps and Trello issue providers and gained OAuth hooks plus local secret storage. Since v18.19.0 in early August the repository has published only working branch tags, so the numbered release stream has been quiet for over a week.

◆ Where it's heading

The arc is a single-user local app growing the two things multi-device users demand — sync they can trust and third-party integrations — without standing up a server the project has to operate. Sync is being pushed toward fail-closed defaults: encryption is enforced rather than offered, plaintext downloads are refused, stale-key uploads are blocked, and the local REST API now demands a bearer token. Integrations are moving the other way, out of core and into plugins that can authenticate on their own. The one visible thread since then is design-system work — dialogs being moved off hardcoded fills onto theme tokens — which suggests a theming pass running between releases.

◆ Prediction

Expect the opt-in split-file delta sync format to become the default once conflict replay settles, and more built-in issue providers to follow Azure DevOps and Trello out of core into plugins. The current styling commits point to a theme-token cleanup landing in the next numbered release, though the branch tags alone do not say how large it is.

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 Super Productivity 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 Super Productivity or Wakapi.

See all Super Productivity alternatives → · See all Wakapi alternatives →

Recent activity from Super Productivity and Wakapi

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

  1. 6h agoWakapiCritical auth bypass from a shared cache key namespace
  2. 3d agoSuper ProductivityDialog fills move to theme tokens; callout markup corrected
  3. 11d agoSuper ProductivityEncrypted-only sync enforced; local REST API now needs a token
  4. 25d agoSuper ProductivityRecurring task settings fold into the planner's schedule dialog
  5. 1mo agoSuper ProductivityConcurrent edits to the same task now merge field by field
  6. 1mo agoWakapiRelease 2.17.5
  7. 1mo agoSuper ProductivitySync fix: project move replays now converge
  8. 1mo agoSuper ProductivityTodoist import, Android widget, opt-in split-file delta sync
  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 Super Productivity and Wakapi?

They serve adjacent needs but don't currently overlap on shipped themes. Super Productivity 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 Super Productivity better than Wakapi?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Super Productivity 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 Super Productivity?

Top Super Productivity alternatives in PM are ranked by recent ship velocity. Browse the "Super Productivity alternatives" section above for the current picks, or visit /alternatives/super-productivity 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.