Zou, the Kitsu API is the memory of your animation production
The Kitsu API allows to store and manage the data of your animation/VFX production. Through it, you can link all the tools of your pipeline and make sure they are all synchronized.
A dedicated Python client, Gazu, allows users to integrate Zou into the tools.
Features
Zou can:
Store production data, such as projects, shots, assets, tasks, and file metadata.
Track the progress of your artists
Store preview files and version them
Provide folder and file paths for any task
Import and Export data to CSV files
Publish an event stream of changes
Installation and Documentation
Installation of Zou requires the setup of third-party tools such as a database instance, so it is recommended to follow the documentation:
Specification: - https://api-docs.kitsu.cloud/
Contributing
Contributions are welcomed so long as the C4 contract is respected.
Zou is based on Python and the Flask framework.
You can use the pre-commit hook for Black (a Python code formatter) before committing:
pip install pre-commit
pre-commit installIf you use Claude Code (or another AI assistant that reads CLAUDE.md), copy CLAUDE.local.md.example to CLAUDE.local.md and adapt it to your local environment (virtualenv path, test database name, etc.). The CLAUDE.local.md file is gitignored and holds your local-only commands (test execution, migrations), while CLAUDE.md only documents code conventions shared by the whole team.
cp CLAUDE.local.md.example CLAUDE.local.mdInstructions for setting up a development environment are available in the documentation
Contributors
@aboellinger (Xilam/Spa)
@BigRoy (Colorbleed)
@EvanBldy (CGWire) - maintainer
@ex5 (Blender Studio)
@flablog (Les Fées Spéciales)
@frankrousseau (CGWire) - maintainer
@kaamaurice (Tchak)
@g-Lul (TNZPV)
@pilou (Freelancer)
@LedruRollin (Cube-Xilam)
@mathbou (Zag)
@manuelrais (TNZPV)
@NehmatH (CGWire)
@pcharmoille (Unit Image)
@Tilix4 (Normaal)
About authors
Kitsu is written by CGWire, a company based in France. We help with animation and VFX studios to collaborate better through efficient tooling. We already work with more than 70 studios around the world.
Visit cg-wire.com for more information.
1 maintainer
Release files for zou 1.0.64
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zou-1.0.64.tar.gz | 695.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zou-1.0.64-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 MB
Release files / zou-1.0.64.tar.gz
| Download URL | zou-1.0.64.tar.gz |
|---|---|
| Size | 695.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d4ed1850f06a72b20940fcb16ae688d503f8f2ba5d4447ad1b9a4bc29950148
|
|
BLAKE2b-256 checksum How to use checksums |
2df6e1feb069ef4f93db08cbfc1d608547f8c4001fbb7041a105ce863e94c8bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logRelease files / zou-1.0.64-py3-none-any.whl
| Download URL | zou-1.0.64-py3-none-any.whl |
|---|---|
| Size | 974.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
440faf25f17b1d0ebaeed238095517a7fd06727bb9170414f0f97283529485ae
|
|
BLAKE2b-256 checksum How to use checksums |
d9a2e2c81c106bf373fe40cca3c9cbbf71c18b585f01a8d49474a3eee27cff24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency log
