Every studio has this conversation.
A producer suggests moving production tracking to the cloud. Someone raises the concern immediately: what about our IP?
It is a valid concern. Your data is the production and losing control over it is not an option.
Kitsu was built by people who have worked in production. The goal is not to push you into a system but to give you control without adding friction to your pipeline.
With Kitsu, your data is not part of someone else’s ecosystem.
Everything you create in production lives inside your project space: assets, shots, comments, reviews, schedules, and time logs are all tied to your studio.
If you need to leave, you export your data. No negotiation, no proprietary format that locks you in.
Many studios only realize the cost of lock in when they try to switch tools mid production.
The fear usually comes from not knowing where the data lives or who can access it.
Kitsu Cloud is hosted in France under strict European data protection regulations. Data is encrypted, both in transit and at rest. Access is controlled and monitored.
More importantly, Kitsu lets you define who sees what.
You can restrict access per project, per department, or per role. You can keep a client project fully isolated so only the assigned team can see it.
Some studios cannot use cloud solutions at all. This is common with broadcasters or high profile IP.
Kitsu does not force a compromise here.
You can run it on your own infrastructure. Same tool, same workflow, fully inside your network. The CGWire team can handle deployment and monitoring if needed, or your internal team can manage it.
Because Kitsu is open source, there is no black box. Your technical team can inspect how everything works, integrate it into your pipeline, and adapt it if required. No need to trust what you cannot see.
Security is about how people actually work.
Artists need to publish quickly. Supervisors need to review shots without friction. Production needs real time visibility.
Kitsu is designed so security does not slow any of that down.
Artists can publish previews directly from their DCC tools. Reviews happen inside structured playlists with clear access control. Feedback stays attached to the right version.
At the same time, role-based permissions ensure that only the right people can access sensitive shots or assets.
Rather than adding extra steps, we help you replace risky workflows with proven technology.
Every studio has a backup strategy. Not every studio tests it.
With Kitsu Cloud, backups are automated. If something goes wrong, recovery processes are already in place.
For on premise setups, the same logic applies. You can integrate Kitsu into your existing backup systems and keep full control over how redundancy is handled.
We remove common weak points where production data is scattered across multiple tools without a consistent safety net.
CGWire is not a generic software vendor. It is a small team focused entirely on production workflows for animation, VFX, and games.
That focus shows in how Kitsu is designed.
The platform is a live hub where tasks, assets, reviews, schedules, and communication are connected. The centralization reduces the number of places where sensitive data could be duplicated or lost.
Studios in more than 50 countries use Kitsu in real production environments as a core part of their pipeline.
If your concern is losing control of your IP, avoiding the cloud entirely is not the only solution.
What matters is who owns the data, where it is hosted, how access is controlled, whether you can leave without friction, and whether the tool adapts to your pipeline
Kitsu checks all boxes. You can use it in the cloud with strong safeguards and no infrastructure overhead. Or you can run it fully on premise with complete isolation.
Either way, you'll never have to give up control.
And in production, it makes the difference between a system that slows the team down and one that actually helps the work move forward.