Atlassian
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
A side-by-side editorial comparison of Sugar Calendar and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Sugar Calendar pushes deeper into ticketing while versioned releases go quiet
The two recent posts are feature announcements written as guides: multiple ticket types per event, letting organizers price early buyers and premium seating differently, and native Zoom meeting creation attached to an event. Behind them the feed jumps back to 2025 and 2024, where the entries are conventional numbered releases covering RSVPs, speakers and tags in 3.7, recurring-event editing and expanded Stripe in 3.6, venue management in 3.5, and migration tooling in 3.3.
Wakapi is quietly rebuilding itself around the login and container requirements teams ask for.
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 also carried a responsibly disclosed security fix and dropped its relay endpoint. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.
The two recent posts are feature announcements written as guides: multiple ticket types per event, letting organizers price early buyers and premium seating differently, and native Zoom meeting creation attached to an event. Behind them the feed jumps back to 2025 and 2024, where the entries are conventional numbered releases covering RSVPs, speakers and tags in 3.7, recurring-event editing and expanded Stripe in 3.6, venue management in 3.5, and migration tooling in 3.3.
Two shifts are visible at once. The product keeps moving from calendar display toward event commerce and operations, with ticket pricing tiers now sitting on top of the payment and RSVP work of the previous cycle. At the same time the announcement style has changed: the 2026 posts describe capabilities without attaching them to a version, and no numbered release appears in the past twelve months of this feed. Whether that reflects continuous shipping or a slower release cycle is not visible here.
Ticketing looks like the active area, so attendee-side capabilities such as check-in or per-tier availability limits are the plausible next additions. The absence of numbered releases since 3.7 makes version-level prediction unreliable from this source.
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 also carried a responsibly disclosed security fix and dropped its relay endpoint. 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 with no shell are the requirements that come from someone else's security review, not from a hobbyist's wishlist. The corresponding cost is visible too: dropped MSSQL support and a Docker base change that forces SQLite users to fix directory permissions by hand.
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 Sugar Calendar or Wakapi.
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
The time-tracking product is invisible behind a steady run of comparison roundups.
Phorge tags a release per fix, and years pass between the ones that reach this feed.
Zoho Projects makes time tracking the product's center of gravity, and lets Zia build the schema.
Jira is being pushed upward — from tracking the work to judging its cost, risk and business health.
Steady small-surface polish across Basecamp and HEY, with no directional move.
See all Sugar Calendar 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. Sugar Calendar 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. Sugar Calendar 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 Sugar Calendar alternatives in PM are ranked by recent ship velocity. Browse the "Sugar Calendar alternatives" section above for the current picks, or visit /alternatives/sugar-calendar 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.