← Back to home
Comparison · PM

Kitsu vs Phorge

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

Kitsu vs Phorge: at a glance

FeatureKitsuPhorge
SectorPMPM
Velocity score5.00.0
Sparks · 30d00
Top themesanimation, vfx, production-tracking, studio-permissionsphabricator-fork, code-review, legacy-maintenance, subversion
Last editorial update1d ago3mo ago
WebsiteVisit →Visit →

What is Kitsu?

Kitsu ships weekly production-management updates, from per-show roles to a new Kanban board.

Kitsu, the open-source animation and VFX production tracker, has posted a feature update most weeks since late September: per-production roles, metadata per task type, episode-based schedules for TV series, team schedule filters, mention replies, a redesigned Kanban board, and player trim handles. Earlier in the year the focus was the review loop, with onion skinning, an annotation eraser, public playlist links, and OpenID Connect sign-in.

Read the full Kitsu trajectory →

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.

Read the full Phorge trajectory →

Kitsu vs Phorge: editorial side-by-side

K5.0

Kitsu ships weekly production-management updates, from per-show roles to a new Kanban board.

◆ Current state

Kitsu, the open-source animation and VFX production tracker, has posted a feature update most weeks since late September: per-production roles, metadata per task type, episode-based schedules for TV series, team schedule filters, mention replies, a redesigned Kanban board, and player trim handles. Earlier in the year the focus was the review loop, with onion skinning, an annotation eraser, public playlist links, and OpenID Connect sign-in.

◆ Where it's heading

The emphasis has moved from client-facing review toward running multi-show studios: permissions per production, department-specific data and episodic planning. The weekly cadence makes each entry small.

◆ Prediction

More weekly updates on scheduling and studio permissions are likely; a larger release is not signalled in the feed.

P0.0

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.

Alternatives to Kitsu and Phorge

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 Kitsu or Phorge.

See all Kitsu alternatives → · See all Phorge alternatives →

Recent activity from Kitsu and Phorge

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

  1. 7d agoKitsuPlayer Upgrades
  2. 14d agoKitsuRedesigned Kanban Boards
  3. 21d agoKitsuTeam Schedule Improvements
  4. 21d agoKitsuDirect Mention Replies
  5. 28d agoKitsuEpisode-Based Schedule for TV Series
  6. 1mo agoKitsuTask Metadata per Task Type
  7. 4mo agoPhorge2026.27: Maniphest search: Throw a Query Error when passing non-digit task IDs
  8. 10mo agoPhorge2025.51: Don't crash when failed to load configuration
  9. 2y agoPhorge2024.35: Subversion: fix empty "Authored on" date on commit pages
  10. 3y agoPhorge2023.23: Mobile: hide unuseful "Persistent Chat" checkbox
  11. 3y agoPhorge2023.17: Fix InvalidArgumentException on commit hook

Frequently asked questions

What is the difference between Kitsu and Phorge?

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

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

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

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.