Kitsu (production collaboration platform)
Source: https://github.com/cgwire/kitsu
Id reused from research/2026-10-16/seed-catalog.json. Backend is cgwire--zou. L07 2026-10-17: merged duplicate records from x03:cgwire--kitsu (same canonical URL).
Structured fields
{
"archived": false,
"checked_at": "2026-10-17T00:00:00.000Z",
"usefulness": "Web front end for collaborative production management in animation, VFX and game studios: task assignment, status, asset/shot breakdown, review and delivery tracking, with a hosted option and docs site.",
"source_type": "repository",
"availability": "available",
"source_owner": "CG Wire (France)",
"next_check_at": "2026-10-18T00:00:00.000Z",
"upstream_updated_at": "2026-10-16T14:07:36.000Z"
}Evidence claims
- [sourced_fact] README: Kitsu is a web application for collaboration on creative productions and managing deliveries; titled 'Collaboration Platform for Animation, VFX, and Video Game Studios'. · locator: README intro source
- [sourced_fact] AGPL-3.0 license; last push 2026-10-16; homepage kitsu.cg-wire.com. · locator: LICENSE file source
- [sourced_fact] The Kitsu documentation site is live and describes Kitsu as the collaboration platform for creative teams. · locator: docs site metadata source
- [sourced_fact] 'Collaboration Platform for Animation and VFX Productions'; web app for collaborating on creative productions and managing deliveries; 'improves the communication between all stakeholders'. · locator: description and README source
- [sourced_fact] License AGPL-3.0; 10,692 commits. · locator: sidebar source
- [upstream_claim] Research review verdict at export: reviewed (as of 2026-10-17). Recorded by the research pipeline, not a hub review outcome; evidence.review stays unreviewed until an independent reviewer records one.
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| code | AGPL-3.0 | restricted | restricted | permitted | unknown | AGPL-3.0 network copyleft. Hosted Kitsu service terms are separate and were not read. |
Linked records
- How should per-take generative metadata (model version, seed, prompt, cost) be recorded in a production tracker so reviews and rights can be audited? discusses → this
- Two repositories met the bar of a real license file, readable documentation and visible activity: UniversalScheduleStandard (a JSON interchange format, licence conflict, see F07) and OpenShotDesigner (GPL-3.0-or-later; stripboard, DOOD, call sheets, schedule-derived budget; created 2026-08-17, one … cites → this