← Back to home
Comparison · PM

Clockwise vs Wakapi

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

Clockwise vs Wakapi: at a glance

FeatureClockwiseWakapi
SectorPMPM
Velocity score0.05.0
Sparks · 30d00
Top themesshutdown, calendar-optimization, ai-scheduling, end-of-lifetime-tracking, self-hosted, api-security, ai-coding
Last editorial update1mo ago2d ago
WebsiteVisit →Visit →

What is Clockwise?

Clockwise shut down on March 27, 2026—data deleted, Reclaim.ai designated as the migration path.

Clockwise has closed. All services ended March 27, 2026; prepaid subscribers receive pro-rated refunds and all user data is scheduled for deletion shortly after that date. The company has formally partnered with Reclaim.ai as the recommended successor for users seeking AI-powered calendar optimization.

Read the full Clockwise trajectory →

What is Wakapi?

Wakapi tightens API key scope and fixes double-counted AI agent time.

Wakapi's 2.18 line opened with security and data fixes: API keys now authorize only /api endpoints (a breaking change), permission checks on the filtered stats endpoint were fixed, and AI agent thinking time was being counted twice, which needs summary regeneration to correct. 2.18.1 fixed slow SQLite charts and an unresponsive server during aggregation, and 2.18.2 adds a heartbeats index that can take hours to build on large tables.

Read the full Wakapi trajectory →

Clockwise vs Wakapi: editorial side-by-side

C0.0

Clockwise shut down on March 27, 2026—data deleted, Reclaim.ai designated as the migration path.

◆ Current state

Clockwise has closed. All services ended March 27, 2026; prepaid subscribers receive pro-rated refunds and all user data is scheduled for deletion shortly after that date. The company has formally partnered with Reclaim.ai as the recommended successor for users seeking AI-powered calendar optimization.

◆ Where it's heading

There is no trajectory—the product is in wind-down. The recent changelog entries are shutdown FAQs covering refunds, data deletion, scheduling link deprecation, and the Reclaim migration guide. The formal Reclaim partnership suggests a structured handoff rather than an abrupt closure.

◆ Prediction

The product no longer exists. Reclaim.ai is the designated successor. Any remaining Clockwise calendar events (Focus Time, Smart Holds) were removed from user calendars at shutdown.

W5.0

Wakapi tightens API key scope and fixes double-counted AI agent time.

◆ Current state

Wakapi's 2.18 line opened with security and data fixes: API keys now authorize only /api endpoints (a breaking change), permission checks on the filtered stats endpoint were fixed, and AI agent thinking time was being counted twice, which needs summary regeneration to correct. 2.18.1 fixed slow SQLite charts and an unresponsive server during aggregation, and 2.18.2 adds a heartbeats index that can take hours to build on large tables.

◆ Where it's heading

Identity and access remain the theme: OIDC login, OIDC-only mode, multiple API keys, the critical auth bypass fix in 2.17.6, and now narrower key scope. Performance work for large heartbeat tables is emerging alongside it. Release notes are still often bare issue numbers.

◆ Prediction

Expect 2.18.x patches addressing database migrations, given the MariaDB failure noted in 2.18.1; the notes don't show what a 2.19 would contain.

Alternatives to Clockwise 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 Clockwise or Wakapi.

See all Clockwise alternatives → · See all Wakapi alternatives →

Recent activity from Clockwise and Wakapi

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

  1. 20d agoWakapiHeartbeats index that can take hours to build
  2. 1mo agoWakapiSQLite chart and aggregation fixes; MariaDB migration warning
  3. 1mo agoWakapiAPI keys limited to /api; AI agent time no longer double-counted
  4. 2mo agoWakapiCritical auth bypass from a shared cache key namespace
  5. 3mo agoWakapiRelease 2.17.5
  6. 5mo agoWakapiRelease 2.17.4
  7. 7mo agoClockwiseWhat happens to all my data — my calendar preferences, Scheduling Links, and Focus Time settings?
  8. 7mo agoClockwiseWill I get a refund for unused subscription time?
  9. 7mo agoClockwiseHow long will customer support be available?
  10. 7mo agoClockwiseHow long will Clockwise retain my data after shutdown and when will it be deleted?

Frequently asked questions

What is the difference between Clockwise and Wakapi?

They serve adjacent needs but don't currently overlap on shipped themes. Wakapi is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 Clockwise better than Wakapi?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Wakapi is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 Clockwise?

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