Know what breaks
before it breaks.
Kumiho records revisions + dependencies across tools so you can answer:
“If we change this, what downstream work is affected?”
Start with one workflow. Expand when you see value.
Production failures we prevent
Hidden dependencies
A texture update triggers rerender storms across 40 shots. Nobody knew it was connected.
→ Consequence: Days of unexpected work
Missing provenance
Client asks for changes. The original settings are lost. The shot cannot be reproduced.
→ Consequence: Non-reproducible work
Manual handoffs
Asset updates happen but downstream teams are not notified. Work proceeds on stale versions.
→ Consequence: Missed updates, rework
Governance gaps
Published assets get silently overwritten. No audit trail. No accountability.
→ Consequence: Accidental overwrites
What Kumiho enables
Outcomes, not features
Impact analysis
Traverse upstream and downstream dependencies before making changes.
Repro closure
Track exactly what created what. Reproduce results months later.
Immutable publishing
Published revisions cannot be silently changed. Trust your deliveries.
Event-driven ops
Pipeline reacts to change. MCP client and AI agent integrations enable intelligent automation.
Stop surprise downstream failures. Reproduce results months later. Automate with n8n, MCP clients, or AI agents.
Adopt without rebuild
No big-bang migration. No workflow overhaul.
Start small
Begin with one department or tool. Expand when ready.
Keep storage on-prem
Files stay where they are. No uploads. No new silos.
Add integrations gradually
Plugins and SDK integrate with your existing tools at your pace.
Security & governance
Procurement-ready from day one
Tenant isolation
Each organization is isolated. No cross-tenant data access.
Roles & guardrails
Fine-grained permissions. Control who can publish, edit, or view.
Published immutability
Once published, revisions are immutable. No silent overwrites.
Audit trail
Every revision is attributed and timestamped. Full history always.
Built by pipeline engineers
We have built asset tracking systems for VFX, animation, and AI-native pipelines. Kumiho is the system we wished existed.
- Design principles from large-scale production pipelines
- Graph-native architecture, not file-centric retrofit
- SDK-first: Python, C++, Rust, Dart for real integrations
Multi-region architecture
Control Plane (Global) + Data Plane (Regional)
Your files stay in your region
See the blast radius
Before changing an asset, see exactly what depends on it — upstream and downstream. No more surprise rerender storms.
- ✓ Traverse dependencies before changes
- ✓ Identify affected shots and deliveries
- ✓ Notify downstream teams automatically
3 shots affected by this change
Bring structure to your pipeline — without slowing it down.
Start tracking revisions and dependencies today. Scale when you are ready.
No uploads. No workflow overhaul. Works with your existing storage.