Tracecat
Tracecat's 1.3 alphas keep reworking agent plumbing: tunnels, multi-org MCP, pluggable runners.
A side-by-side editorial comparison of Fibery and Phorge — release velocity, themes, recent moves, and the top alternatives to consider.
Fibery's MCP server can now upload local files, so AI assistants can attach screenshots and images.
Fibery's October 22 release is small: rich text accepts multiple files at once, with new upload and upload-by-link options, and the MCP server lets an AI assistant upload files from the user's computer into file fields or rich text. It follows three heavier releases: AI-built custom integrations, Custom Apps as entity views, and a rebuilt AI agent.
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.
Fibery's October 22 release is small: rich text accepts multiple files at once, with new upload and upload-by-link options, and the MCP server lets an AI assistant upload files from the user's computer into file fields or rich text. It follows three heavier releases: AI-built custom integrations, Custom Apps as entity views, and a rebuilt AI agent.
Fibery is making AI the main builder and operator of the workspace: the agent, Custom Apps, AI-generated integrations and an MCP server that now handles code execution and files. The weekly cadence alternates big AI releases with quality-of-life updates like this one.
Expect the custom-integration preview to widen and the MCP server to gain more write actions; another large AI release is likely within a few weeks given the pattern.
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.
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.
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.
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 Fibery or Phorge.
Tracecat's 1.3 alphas keep reworking agent plumbing: tunnels, multi-org MCP, pluggable runners.
NocoBase's Runner Agent gets conversation management, task links and agent switching mid-thread.
Camunda opens the 8.11 cycle with job-worker fixes and variable metadata across gRPC, REST and MCP.
Todoist's 2026 bets are on capture: voice via Ramble, photos and files via Task Capture.
Atarim's AI experts now propose changes to live pages as drafts, and the app runs on phones.
SmartSuite adds a scheduled JavaScript runtime with secrets and run history.
See all Fibery alternatives → · See all Phorge alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fibery is currently shipping more aggressively (velocity 7.5 vs 0.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fibery is currently shipping more aggressively (velocity 7.5 vs 0.0), 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.
Top Fibery alternatives in PM are ranked by recent ship velocity. Browse the "Fibery alternatives" section above for the current picks, or visit /alternatives/fibery for the full list with editorial commentary on each.
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.