Version control for creative work.
Kumiho is like Git for artists and studios. It tracks every revision, prompt, and dependency so you can reproduce, share, and automate - without moving your files.
What is Kumiho? Version control for creative files. It records what changed, when, and why across your assets.
Technical: It stores revision metadata + relationships in a history database, not your files.
No upload required. Connect a folder, see history instantly.
Search revisions, compare versions, trace lineage in one view.
What you get
The three things that make Kumiho different
Revision History (immutable)
Every output becomes a revision. Restore any point in time. Published revisions cannot be silently changed.
Lineage & Dependencies
Know what created what. Know what breaks if you change something. See upstream and downstream at a glance.
Automation & Events
Every change emits events. Plug into n8n or agents. Trigger downstream work automatically.
How it works
Your files stay put. Kumiho tracks the rest.
Your Storage
Local / NAS / S3
Files stay here
MCP / Plugins / SDK
Register revisions
Clients capture context
Kumiho Graph
Relationships + metadata
We store the history
UI / Search / Events
Browse, trace, automate
You get visibility
Before → After
Before: folder chaos
📁 project_final/
├── hero_v1.png
├── hero_v2_final.png
├── hero_v2_final_REAL.png
├── hero_v3_approved.png
└── hero_v3_approved_v2.png
After: addressable history
kref://project/characters/hero.image
5 revisions · tags: latest, approved, published
Provenance: 3 inputs and dependencies
Metadata: prompt, model, seed, any custom key-values
↔ Two-way lookup
Find any file → trace to its kref, revisions, lineage Have a kref → resolve to artifact location on your storage
Real workflow example
Generate 200 AI variations
Each registered with prompt, model, seed
Compare and filter
Search by metadata, not filenames
Pick and publish
Published revision becomes immutable
Trace provenance anytime
Show exactly how this was created
See it in 60 seconds
Register → Revise → Relate → Retrieve
Built for scale, designed for trust
Multi-tenant isolation
Each tenant's data is fully isolated. Your history, your access controls, your audit trail.
Data residency
Your metadata stays in your chosen region. Files never leave your storage.
Real-time events
Every change emits an event. Subscribe to what matters, automate what you need.
Three ways to start
Pick your entry point based on how you work
Create
ComfyUI
Version every generation. Prompts, seeds, and lineage captured as you work.
Set up ComfyUI nodesAutomate
n8n
Trigger downstream work when an asset changes. Build complex pipelines visually.
Explore n8n workflowsBuild
SDK
Embed asset history into your app or pipeline. Python, C++, Dart SDKs available.
Read SDK docsCommon questions
Do I have to migrate storage?
No. Your files stay exactly where they are — local drives, NAS, or cloud. Kumiho stores metadata and relationships, not your files.
Does this replace my DAM?
Kumiho complements your DAM. It adds revision history and lineage tracking — the things DAMs typically do not do well.
Can I start small?
Yes. Start with one folder or one workflow. Expand as you see value. No all-or-nothing commitment required.
Is it safe for studios?
Published revisions are immutable. Access is controlled. Multi-tenant isolation is built in. Designed for production pipelines.
Ready to make your work traceable?
Join creators and studios building a history layer for their creative work.
No credit card required. No upload required.