Let’s address the real concern behind this question.
Adopting a new tool implies protecting a pipeline that your team has built over time. It includes your habits, your tools, your shortcuts, and all the small decisions that kept production moving throughout the years.
Kitsu is not here to replace that.
It is designed to sit at the center of your production as a shared source of truth while letting your existing tools continue to do their job.
Whether you run a lightweight setup or a structured pipeline with automation, you can keep what works. But we'll add what is missing.
In many studios, production data ends up fragmented across spreadsheets, tracking tools, and internal scripts.
Kitsu centralizes that knowledge and makes it fully accessible through a REST API.
Everything you manage in the interface is available programmatically:
Your team can focus on automating real production tasks instead of manually syncing data.
Most animation pipelines already rely heavily on Python.
Kitsu provides a dedicated Python SDK client that allows your technical team to interact with production data in an efficient way.
Instead of writing custom HTTP requests, your TDs can:
This reduces the amount of glue code your team has to maintain and makes integrations easier to scale as your production grows.
Our developer tools are well documented.
One of the biggest risks when introducing a new system is disrupting artists.
Kitsu avoids that by integrating with Digital Content Creation tools instead of replacing them:
Artists stay focused on their work, and your production stays consistent and traceable.
A production tracker should not feel like extra work.
Kitsu is a live collaboration hub:
For a distributed team, it cuts a lot of back and forth between multiple tools.
As productions scale, manual steps become a bottleneck.
Kitsu allows you to automate key events using webhooks and API integrations:
Every studio organizes work differently.
Kitsu reflects that by allowing you to configure:
You are not forced into a rigid structure. You adapt the tool to your production logic.
For studios that need more advanced setups, Kitsu can be extended through its API instead of modifying its core to keep your system maintainable over time.
Kitsu is open-source, which changes the relationship you have with your production software.
You can understand how your data is structured, audit how the system works, host it on your own infrastructure if needed, and avoid being locked into opaque systems.
At the same time, CGWire provides managed cloud hosting and custom infrastructure setups if you prefer a fully supported solution.
Kitsu is used by hundreds of studios across different sizes and production types. Some use it out of the box to organize tasks and reviews. Others build advanced pipelines on top of it using its API and integrations.
In both cases, the approach stays the same. You do not rebuild your pipeline. You connect it to a system that centralizes data, improves visibility, and reduces friction between departments.
That is what makes Kitsu fit.