An open-source alternative to Ftrack
Who Kitsu is for
Kitsu is used by animation and VFX studios from 10 to 500 users, on TV series, feature films, shorts, and video game productions. Productions often run with distributed teams or with several studios collaborating on the same show.
Ftrack also targets animation and VFX studios, with a stronger footprint on mid-to-large facilities running customized pipelines. The two tools overlap on the core mission of production tracking, with different bets on how to get there.
What Kitsu covers
A production tracker covers a well-known set of needs: sequences, shots, assets, tasks, statuses, schedules, time tracking, reviews, casting, permissions, a documented API, and DCC integrations. Kitsu covers this scope, the same as Ftrack does. The difference is in how the pieces are presented and how the studio interacts with them.
One area where Ftrack pushes further is its DCC integration footprint via Ftrack Connect. Kitsu's integration story is leaner and relies on the open-source ecosystem: dedicated tools like Prism or Ayon integrate with Kitsu and cover the deep DCC pipeline work, while Kitsu stays focused on the tracking and review workflow.
Approach to configuration
Ftrack is highly configurable: entities, workflow, fields, and UI can be tailored to each studio's pipeline. That depth fits teams with dedicated pipeline engineers who can model and maintain a custom setup.
Kitsu takes the opposite bet. A production tracker is most useful when the whole studio shares one reading of the work, not when each team adapts the tool to its preferences. Standardization is the feature: the workflow model (sequences, shots, assets, tasks, statuses) is fixed, the UI is the same for every role, and the standard configuration works out of the box. Artists, supervisors, production, and IT all use the same interface from day one.
Variations between productions are handled at the project level: task types, statuses, asset categories, custom metadata, schedules. No UI rebuild, no consultants between the studio and the work.
Onboarding reflects this difference. With Kitsu, new artists are productive within a day. With Ftrack, the customization phase typically precedes the productivity phase.
Support and roadmap shaped by the people who use it
Support is handled by industry professionals (former pipeline and production roles), based in Paris. Bugs and questions get answered in hours, not days.
The roadmap lives on a public Canny board where studios vote on what we build next. Current priorities (the permissions system, software integrations) come from there. Decisions are visible, and they can be discussed in the open before they ship.
An active Discord runs alongside, where the CGWire team participates daily. It is the same channel the team uses for incident heads-up, release notes, and discussion of upcoming work.
Ftrack support is handled through the editor's channels. Roadmap and product decisions are internal to the company.
Open source and transparency
Kitsu is open source (AGPL, repository at github.com/cgwire/kitsu). The code can be read, audited, forked, and deployed by anyone. The changelog and the roadmap are public, so studios can see what is coming, what is in progress, and what is being decided.
For teams that want long-term visibility on the tools they depend on, this matters: no surprise pivot, no surprise pricing, no closed-door product decision.
CGWire is an independent company, five people based in Paris, with no external investors. The choices we make on Kitsu (open source, public roadmap, pricing) are ours to keep.
Ftrack is proprietary software, owned by Backbone. The roadmap and codebase stay inside the editor.
Self-hosted, real and free
Around 200 studios run their own Kitsu instance today. Deployment is a Docker compose against a standard PostgreSQL database, which pipeline TDs and IT teams can query and back up with their usual tools.
Ftrack offers an on-premise deployment option as a paid add-on, separate from the standard subscription. With Kitsu, the self-hosted path is free, documented, and at the same feature level as the cloud build.
For studios subject to GDPR, IP protection clauses, or data residency requirements (common on European or Japanese productions), keeping the full stack inside your own infrastructure is a regular deployment, not a special tier.
Where the two tools differ
A few areas where the two tools differ, item by item:
- Casting and breakdown: native and integrated in Kitsu, with dedicated views. Ftrack handles breakdown through asset relationships, which gives flexibility but requires more setup.
- Quotas and timesheets: Kitsu ties them directly to schedules and task types, useful for studios planning charges per artist. Ftrack offers time tracking; quota planning typically requires additional configuration.
- API and integrations: Kitsu exposes a REST API with a documented Python client (gazu). Ftrack uses an event-driven API with its own SDK. Both work, the learning curve differs.
- Review engine: Kitsu offers full playlists with quick access to all versions or shareable playlist links (send a single URL, the reviewer can comment without an account). Ftrack Review is a strong tool with its own ecosystem (cineSync), oriented toward higher-end remote review.
Ftrack's broader DCC integration footprint (Maya, Nuke, Houdini, etc.) is a recognized strength. Kitsu's integration story is leaner and focused on the everyday tracking workflow rather than deep DCC plumbing.
Cost
License pricing sits in the same range. The differences sit around hosting, source code, and how the roadmap is governed.
Kitsu vs Ftrack, at a glance
| Item | Kitsu | Ftrack |
|---|---|---|
| User license | €30 per user per month | ~€25 to €35 per user per month, depending on plan |
| Self-hosted | Free, open source, ~200 active installations | Available, as a paid add-on |
| Source code | Open (AGPL, github.com/cgwire/kitsu) | Proprietary |
| Public roadmap | Yes (Canny board and GitHub issues) | Internal |
| Support channel | Discord, email, by industry professionals | Editor support |
Ftrack pricing varies by plan and region, so the numbers above are an order of magnitude. Studios doing a serious comparison should pull a current quote from ftrack.com.
Common questions
Ftrack is very configurable. Isn't a fixed workflow limiting?
Configurability has a cost: it postpones the moment when the team becomes productive. Standardization also pays off in everyday collaboration: a fixed structure means no 'where do I post the retake?' moments, the same shape applies everywhere, and a new artist or coordinator picks up where the last one left off. Kitsu's standard workflow is the result of years of iteration with studios and is flexible enough to cover 2D, 3D, shorts, feature films, series, video games, VR, AR, and stop motion. Most productions fit it without modification. Studios that need a deeply custom pipeline are usually better served by Ftrack or by combining Kitsu with a pipeline-specific tool like Prism or Ayon.
Ftrack Review is a strong tool. Does Kitsu cover the same ground?
Kitsu has a built-in review engine with version comparison, drawing tools, and shareable playlist links that let external reviewers comment without an account. Ftrack Review remains a recognized tool with its own ecosystem (cineSync) for higher-end remote review.
What about DCC integrations? Ftrack Connect is comprehensive.
Kitsu exposes a REST API with a documented Python client (gazu). For deep DCC pipeline work, Prism and Ayon integrate with Kitsu and cover the territory Ftrack Connect addresses. Many studios run that combination today.
Open source sounds risky for a production-critical tool.
Kitsu has been in active development since 2016, used in production by hundreds of studios. Cloud customers get direct support from the CGWire team. Studios on self-hosted can subscribe to the Partners program for a direct line to the team. The codebase being open means you can audit it, fork it, and you are not locked into a single vendor.
Migration during an active production is too risky.
We support studios on running both tools in parallel during the transition. The data export and schema mapping are well understood, and we can adapt the pace to your production calendar.
Migrating from Ftrack
Moving from Ftrack to Kitsu is a path we know well. We can support you on data export, schema mapping, history preservation, and running both tools in parallel during the transition. Get in touch and we'll walk through what your migration would look like.
Interested in using Kitsu?