← Back to home
Comparison · PM

Float vs Wakapi

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

Float vs Wakapi: at a glance

FeatureFloatWakapi
SectorPMPM
Velocity score6.32.5
Sparks · 30d10
Top themesresource-management, scheduling, ai-matching, rate-cardstime-tracking, self-hosted, oidc, auth-bypass
Last editorial update13h ago1mo ago
WebsiteVisit →Visit →

What is Float?

Float adds AI experience profiles and multi-currency rate cards — expanding from scheduling into project economics.

Float is a resource scheduling and time-tracking platform for agencies and professional services teams, shipping roughly every 2–3 weeks. The last 90 days show two substantive sparks: AI-powered experience profiles that surface who on the team has done similar work before, and multi-currency rate cards that bring consistent billing across clients and regions. Supporting releases added a dedicated Rates tab, Zapier project templates, people codes, and new API endpoints for project templates and rate cards.

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

Float vs Wakapi: editorial side-by-side

F6.3

Float adds AI experience profiles and multi-currency rate cards — expanding from scheduling into project economics.

◆ Current state

Float is a resource scheduling and time-tracking platform for agencies and professional services teams, shipping roughly every 2–3 weeks. The last 90 days show two substantive sparks: AI-powered experience profiles that surface who on the team has done similar work before, and multi-currency rate cards that bring consistent billing across clients and regions. Supporting releases added a dedicated Rates tab, Zapier project templates, people codes, and new API endpoints for project templates and rate cards.

◆ Where it's heading

Float is building the financial layer of resource management — rate cards, multi-currency support, and a Rates tab form a coherent billing workflow that didn't exist six months ago. In parallel, AI experience profiles signal entry into talent-matching territory: the product can now answer 'who has done this type of work before' rather than just 'who is available.' These two vectors together position Float as a project economics tool, not just a scheduling view. The API expansion follows the financial features, suggesting partner and integration investment.

◆ Prediction

The most likely next move is connecting AI experience profiles directly into project assignment — auto-suggesting matches during scheduling based on past work. On the billing side, rate card data likely feeds a revenue or margin reporting view as the next logical release.

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 Float 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 Float or Wakapi.

See all Float alternatives → · See all Wakapi alternatives →

Recent activity from Float and Wakapi

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

  1. 23d agoFloatFloat is the #1 resource management software, 8 seasons running
  2. 26d agoFloatRates tab, Zapier project templates, and people code
  3. 29d agoFloatSmart insights: know who’s done this work before, with AI experience profiles
  4. 1mo agoWakapiCritical auth bypass from a shared cache key namespace
  5. 1mo agoFloatNew API endpoints: project templates and rate cards, and Zapier project updates
  6. 2mo agoWakapiRelease 2.17.5
  7. 2mo agoFloatRate cards and multi-currency: consistent billing across every client and region
  8. 2mo agoFloatA new look: updates to the sidebar navigation
  9. 3mo agoWakapiRelease 2.17.4
  10. 5mo agoWakapiSecurity fix, relay endpoint dropped, summaries may need regenerating
  11. 6mo agoWakapiDistroless nonroot container image; SQLite permissions need fixing
  12. 8mo agoWakapiOIDC-only login mode disables local accounts

Frequently asked questions

What is the difference between Float and Wakapi?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Float is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 Float?

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