← 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.56.3
Sparks · 30d01
Top themestime-tracking, self-hosted, oidc, container-hardeningno-code-platform, ai-employees, portal-manager, dual-release-train
Last editorial update2h ago1d ago
WebsiteVisit →Visit →

What is Wakapi?

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.

Read the full Wakapi trajectory →

What is NocoBase?

NocoBase is running two release trains at once and putting AI employees inside the apps you build.

NocoBase is publishing 2.2 and 3.0 pre-releases in parallel, often hours apart, and the same pull request frequently appears in both — the AI chat box block shows up in a 2.2 alpha and a 2.2 beta on consecutive days. The 3.0 line is dominated by Portal manager work: fixed layouts, an application-wide default portal, AI-mode portals with their own backup and restore path. The 2.2 line is where the AI employees feature is landing, alongside client v2 and approval workflow refinements.

Read the full NocoBase trajectory →

Wakapi vs NocoBase: editorial side-by-side

W2.5

Wakapi is quietly rebuilding itself around the login and container requirements teams ask for.

◆ 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 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.

◆ 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 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.

◆ 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.

N6.3

NocoBase is running two release trains at once and putting AI employees inside the apps you build.

◆ Current state

NocoBase is publishing 2.2 and 3.0 pre-releases in parallel, often hours apart, and the same pull request frequently appears in both — the AI chat box block shows up in a 2.2 alpha and a 2.2 beta on consecutive days. The 3.0 line is dominated by Portal manager work: fixed layouts, an application-wide default portal, AI-mode portals with their own backup and restore path. The 2.2 line is where the AI employees feature is landing, alongside client v2 and approval workflow refinements.

◆ Where it's heading

The direction is AI as a building block rather than an assistant bolted to the admin UI. An embeddable chat box block with scoped conversations, frontend AI tools callable from JS blocks, a knowledge base with configurable vector databases, and a plugin development guide for defining AI employee tools and skills all point the same way: NocoBase wants the apps its users assemble to contain AI employees, not just be administered by one. The parallel trains are the cost of doing that while a 3.0 platform rework is in flight.

◆ Prediction

Expect 3.0 to stabilise the Portal manager as the shell that AI-mode applications run inside, with the AI employee work merging forward from 2.2 rather than being rebuilt. The alpha releases carrying no notes at all make the actual 3.0 scope hard to read from the changelog.

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. 2d agoNocoBasev3.0.0-alpha.6: CSRF, sequence and workflow worker fixes
  2. 3d agoNocoBasev3.0.0-alpha.5: AI portal backups and fixed portal layouts
  3. 5d agoNocoBasev3.0.0-alpha.4: default Portal, LLM and vector DB UI
  4. 5d agoNocoBaseEmbeddable AI chat block lands for apps built on NocoBase
  5. 6d agoNocoBasev3.0.0-alpha.3: version publish, no notes
  6. 6d agoNocoBasev3.0.0-alpha.2: version publish, no notes
  7. 19d agoWakapiRelease 2.17.5
  8. 2mo agoWakapiRelease 2.17.4
  9. 4mo agoWakapiRelease 2.17.3
  10. 5mo agoWakapiRelease 2.17.2
  11. 6mo agoWakapiRelease 2.17.1
  12. 7mo agoWakapiRelease 2.17.0

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 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 Wakapi better than NocoBase?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NocoBase 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 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.