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/
Release notes: each version is published on GitHub Releases; the repository itself keeps no changelog, the commit history is the record.
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)
@CoralieGold (Unit Image)
@EvanBldy (CGWire)
@ex5 (Blender Studio)
@FabianSantiago
@flablog (Les Fées Spéciales)
@frankrousseau (CGWire) - maintainer
@Fuitad
@kaamaurice (Tchak)
@LedruRollin (Cube-Xilam)
@level-antoine
@manuelrais (TNZPV)
@mathbou (Zag)
@mxatmx
@NehmatH (CGWire)
@NicoPennec (CGWire)
@nledez
@pchar2 (Unit Image)
@pilou- (Freelancer)
@robin-vagner (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
Metadata
1 maintainer
Release files for zou 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zou-1.1.1.tar.gz | 872.6 kB | With provenance | Details for zou-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zou-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for zou-1.1.1-py3-none-any.whl |
Total release size: 2.1 MB
Release files / zou-1.1.1.tar.gz
| Download URL | zou-1.1.1.tar.gz |
|---|---|
| Size | 872.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf58ec3df3ebf777ae4879877c69e4de00d7c290d067b8ccdde5a38babb34b3e
|
|
BLAKE2b-256 checksum How to use checksums |
a266dcc610e0485befab1f976d9f2a344124f89a048a7a026a60a71b8929d7d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 3, 2026.
Transparency logRelease files / zou-1.1.1-py3-none-any.whl
| Download URL | zou-1.1.1-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f753a130dde563da7ef48d5ec4b403630740738a9451226e3d0687041a72455
|
|
BLAKE2b-256 checksum How to use checksums |
304c75bf8b8c1570efb65f4d3672984c2a04447b7ee414d4c1fdec1a49c3bc10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 3, 2026.
Transparency logSecurity for zou 1.1.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for zou-1.1.1.tar.gz
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 Nov 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
