Atlassian
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
Comparison · PM
Phorge vs NocoBase
A side-by-side editorial comparison of Phorge and NocoBase — release velocity, themes, recent moves, and the top alternatives to consider.
Phorge vs NocoBase: at a glance
What is Phorge?
Phorge tags a release per fix, and years pass between the ones that reach this feed.
Phorge, the community continuation of Phabricator, tags releases named for the week they land and for the single change they carry. The entries visible here span three years and are all small defensive fixes: query errors instead of raw exceptions on malformed task IDs, a readable error screen when configuration fails to load, an empty authored date on Subversion commits, a crash in a commit hook when getenv returns false.
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.
Phorge vs NocoBase: editorial side-by-side
Phorge
0.0PM
Phorge tags a release per fix, and years pass between the ones that reach this feed.
◆ Current state
Phorge, the community continuation of Phabricator, tags releases named for the week they land and for the single change they carry. The entries visible here span three years and are all small defensive fixes: query errors instead of raw exceptions on malformed task IDs, a readable error screen when configuration fails to load, an empty authored date on Subversion commits, a crash in a commit hook when getenv returns false.
◆ Where it's heading
This is a project in stewardship rather than development. The work concentrates on the places an inherited codebase breaks — Subversion paths that upstream barely exercised, error handling that assumed configuration always loads, exception types leaking to users — and each fix is documented with a reproduction and test plan in the old Phabricator review style. Nothing in this window suggests new capability; the goal visible in the changelog is that the software keeps running for the installs that already depend on it.
◆ Prediction
The pattern points to more individually tagged small fixes in legacy code paths and error handling; there is no signal here of a larger release being assembled.
NocoBase
6.3PM
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 Phorge 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 Phorge or NocoBase.
Everhour
The time-tracking product is invisible behind a steady run of comparison roundups.
Wakapi
Wakapi is quietly rebuilding itself around the login and container requirements teams ask for.
Zoho Projects
Zoho Projects makes time tracking the product's center of gravity, and lets Zia build the schema.
Jira
Jira is being pushed upward — from tracking the work to judging its cost, risk and business health.
Basecamp
Steady small-surface polish across Basecamp and HEY, with no directional move.
See all Phorge alternatives → · See all NocoBase alternatives →
Recent activity from Phorge and NocoBase
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoNocoBasev3.0.0-alpha.6: CSRF, sequence and workflow worker fixes
- 3d agoNocoBasev3.0.0-alpha.5: AI portal backups and fixed portal layouts
- 5d agoNocoBasev3.0.0-alpha.4: default Portal, LLM and vector DB UI
- 5d agoNocoBaseEmbeddable AI chat block lands for apps built on NocoBase ⚡
- 6d agoNocoBasev3.0.0-alpha.3: version publish, no notes
- 6d agoNocoBasev3.0.0-alpha.2: version publish, no notes
- 1mo agoPhorge2026.27: Maniphest search: Throw a Query Error when passing non-digit task IDs
- 7mo agoPhorge2025.51: Don't crash when failed to load configuration
- 1y agoPhorge2024.35: Subversion: fix empty "Authored on" date on commit pages
- 3y agoPhorge2023.23: Mobile: hide unuseful "Persistent Chat" checkbox
- 3y agoPhorge2023.17: Fix InvalidArgumentException on commit hook
Frequently asked questions
What is the difference between Phorge and NocoBase?
They serve adjacent needs but don't currently overlap on shipped themes. NocoBase is currently shipping more aggressively (velocity 6.3 vs 0.0), 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 Phorge 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 0.0), 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 Phorge?
Top Phorge alternatives in PM are ranked by recent ship velocity. Browse the "Phorge alternatives" section above for the current picks, or visit /alternatives/phorge 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.