← Back to home
Comparison · PM

Tracecat vs Wakapi

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

Tracecat vs Wakapi: at a glance

FeatureTracecatWakapi
SectorPMPM
Velocity score6.35.0
Sparks · 30d00
Top themessecurity-automation, ai-agents, multi-tenancy, case-managementtime-tracking, self-hosted, api-security, ai-coding
Last editorial update19h ago12d ago
WebsiteVisit →Visit →

What is Tracecat?

Tracecat 1.5 alpha patches add sub-cases and lock down agent sandboxes.

Tracecat 1.4.0 went stable with MCP variable tools and case task actions, and 1.5.0-alpha.2 hardened multi-tenant installs with row-level security, database roles and cloud IAM logins. Four alpha.2 patches followed within a day: sub-cases close with their parent and can be used to deduplicate cases, sandboxes start isolated and cannot read loader variables, agents can use more than 50 tools, and several API errors now return proper status codes.

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

Tracecat vs Wakapi: editorial side-by-side

T6.3

Tracecat 1.5 alpha patches add sub-cases and lock down agent sandboxes.

◆ Current state

Tracecat 1.4.0 went stable with MCP variable tools and case task actions, and 1.5.0-alpha.2 hardened multi-tenant installs with row-level security, database roles and cloud IAM logins. Four alpha.2 patches followed within a day: sub-cases close with their parent and can be used to deduplicate cases, sandboxes start isolated and cannot read loader variables, agents can use more than 50 tools, and several API errors now return proper status codes.

◆ Where it's heading

The 1.5 line is about making Tracecat safe to run for many tenants and many agents at once. The patch run splits between tenant isolation fixes and case management features for handling duplicate alerts.

◆ Prediction

Expect more alpha.2.x patches and then a 1.5.0 release candidate that bundles the tenant isolation work with sub-case handling.

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

See all Tracecat alternatives → · See all Wakapi alternatives →

Recent activity from Tracecat and Wakapi

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

  1. 1d agoTracecat1.5 alpha.2.4: sub-case actions to merge duplicate cases
  2. 1d agoTracecat1.5 alpha.2.3: sub-cases close with their parent
  3. 1d agoTracecat1.5 alpha.2.2: agent sandboxes start isolated
  4. 1d agoTracecat1.5 alpha.2.1: tenant-scoped reads, 50+ agent tools
  5. 3d agoTracecat1.5 alpha.2: row-level security, IAM logins, agent session feed
  6. 8d agoTracecatNightly: workflow agent actions run on the selected backend
  7. 1mo agoWakapiHeartbeats index that can take hours to build
  8. 1mo agoWakapiSQLite chart and aggregation fixes; MariaDB migration warning
  9. 2mo agoWakapiAPI keys limited to /api; AI agent time no longer double-counted
  10. 2mo agoWakapiCritical auth bypass from a shared cache key namespace
  11. 3mo agoWakapiRelease 2.17.5
  12. 5mo agoWakapiRelease 2.17.4

Frequently asked questions

What is the difference between Tracecat and Wakapi?

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

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

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