← Back to home
Comparison · PM

Wakapi vs NocoBase

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

Wakapi vs NocoBase: at a glance

FeatureWakapiNocoBase
SectorPMPM
Velocity score2.58.8
Sparks · 30d02
Top themestime-tracking, self-hosted, oidc, auth-bypassno-code, ai-workflows, knowledge-base, open-source
Last editorial update28d ago13h ago
WebsiteVisit →Visit →

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 →

What is NocoBase?

NocoBase adds an AI knowledge base retrieval API, connecting no-code workflows to external knowledge sources.

NocoBase is an open-source no-code/low-code platform shipping on two parallel tracks: a stable beta (2.3.x) and an alpha preview (2.4.x). Both tracks are active—the same features land in alpha first, then backport to beta within days. The most significant recent addition is an authenticated knowledge base retrieval API with a built-in provider for remote NocoBase knowledge bases, giving AI employees in workflows access to structured external content for RAG-style lookups. Security improvements are also landing: blocking server-side requests to literal IP addresses and preventing secret env var exposure in custom request URLs.

Read the full NocoBase trajectory →

Wakapi vs NocoBase: editorial side-by-side

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.

N8.8

NocoBase adds an AI knowledge base retrieval API, connecting no-code workflows to external knowledge sources.

◆ Current state

NocoBase is an open-source no-code/low-code platform shipping on two parallel tracks: a stable beta (2.3.x) and an alpha preview (2.4.x). Both tracks are active—the same features land in alpha first, then backport to beta within days. The most significant recent addition is an authenticated knowledge base retrieval API with a built-in provider for remote NocoBase knowledge bases, giving AI employees in workflows access to structured external content for RAG-style lookups. Security improvements are also landing: blocking server-side requests to literal IP addresses and preventing secret env var exposure in custom request URLs.

◆ Where it's heading

NocoBase is building out its AI employee and workflow AI layer systematically: context data source settings were simplified in alpha.3, and now the knowledge base retrieval API adds a retrieval-augmented generation primitive that no-code users can wire into workflows without writing code. The WeCom and DingTalk integrations continue to mature, signaling a Chinese enterprise market focus alongside international adoption. Security hardening (XSS prevention, SSRF mitigations) is getting attention across releases, suggesting enterprise deployments with compliance requirements.

◆ Prediction

NocoBase will expand the AI knowledge base surface—likely adding vector search providers, fine-grained access control for knowledge bases, and richer AI employee configuration tied to specific knowledge domains. Expect the 2.4.0 release line to formalize AI employees as a stable feature alongside the knowledge base API.

Alternatives to Wakapi and NocoBase

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

See all Wakapi alternatives → · See all NocoBase alternatives →

Recent activity from Wakapi and NocoBase

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

  1. 1d agoNocoBasev2.4.0-alpha.6: SSRF protection and secret exposure fix
  2. 1d agoNocoBasev2.3.0-beta.10
  3. 6d agoNocoBasev2.3.0-beta.9
  4. 7d agoNocoBasev2.4.0-alpha.5
  5. 9d agoNocoBasev2.3.0-beta.8
  6. 10d agoNocoBasev2.4.0-alpha.4
  7. 28d agoWakapiCritical auth bypass from a shared cache key namespace
  8. 2mo agoWakapiRelease 2.17.5
  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. 7mo agoWakapiOIDC-only login mode disables local accounts

Frequently asked questions

What is the difference between Wakapi and NocoBase?

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

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

What are the best alternatives to NocoBase?

Top NocoBase alternatives in PM are ranked by recent ship velocity. Browse the "NocoBase alternatives" section above for the current picks, or visit /alternatives/nocobase for the full list with editorial commentary on each.