← Back to home
Comparison · PM

Kitsu vs Aha!

Side-by-side trajectory, velocity, and editorial themes.

K2.5

Kitsu is turning its studio pipeline tool into a client-facing review platform.

◆ Current state

Kitsu, the open-source animation and VFX production tracker, is investing heavily in the review loop: onion skinning and shape annotations, an annotation eraser, public playlist links that let external reviewers comment without accounts, and client-visible comment toggles. In parallel it added OpenID Connect for studio SSO and production-setup tooling (project templates, retake-count and cross-task-type filters).

◆ Where it's heading

The clear direction is external collaboration — pulling clients, supervisors, and vendors into Kitsu's review player rather than exporting frames elsewhere. Enterprise auth (OIDC) and richer annotation tools reinforce a move from internal tracker toward a shared review-and-approval hub.

◆ Prediction

Expect the guest-review surface to deepen — more annotation fidelity and approval-workflow controls — and further identity/permissions work following OIDC. The cadence points to continued review-platform build-out.

A6.3

Aha! extends from roadmapping into AI app-building, wrapping Builder in the access controls enterprises require

◆ Current state

Aha! is layering an AI app-building surface, Aha! Builder, on top of its roadmapping core, letting teams turn planned features into working prototypes and applications. The most recent releases harden Builder for real use: role-based permissions and user management, plus built-in security and privacy reviews. Alongside the product posts, the feed carries the usual founder thought-leadership, which dilutes but doesn't change the signal.

◆ Where it's heading

The direction is clear: close the loop from strategy to shipped software inside one tool, and make Builder governable enough for larger teams. Supporting moves, required fields by status, AI-assisted idea-to-feature promotion, and live spreadsheets, keep tightening the roadmapping workflow that feeds Builder.

◆ Prediction

Expect continued enterprise-readiness work on Builder (deeper permissions, deployment, compliance) and tighter handoff from Aha! Roadmaps into generated applications, positioning Builder as the destination for roadmap items rather than a side experiment.

See more alternatives to Kitsu
See more alternatives to Aha!