Drowning in final_final_v12.psd files?
Version control for creative work.
Kumiho is like Git for artists and studios. It tracks every version and the why behind it - without moving your files.
Find any version in seconds, keep prompts attached, and stop guessing what changed.
Browse revisions, compare versions, and trace lineage without leaving your folder structure.
How it works
- 1Connect your storage: local disk, NAS, or S3
- 2Register revisions with plugins or SDKs - capture prompts, metadata, and links between versions
- 3Search history, see what depends on what, and trigger automations when things change
- No uploads - files stay on your storage
- Export metadata anytime - no lock-in
- Start with one folder on local, NAS, or S3
Designed by pipeline engineers who have shipped production creative workflows.
The problem isn't storage. It's losing context.
The pain
Versions explode
final_final_v12.psd anyone?
Metadata disappears
Prompts, models, seeds - gone.
Dependencies are invisible
What created what? Nobody knows.
The fix
Every output becomes a revision
With prompts and metadata attached.
Relationships are visible
See what depends on what.
Automations trigger on change
Get alerts or kick off workflows.
Files stay on your storage. Kumiho keeps the history and the why.
How it works
Three steps to make every output traceable — without changing your workflow.
Connect your storage
Local disk, NAS, or S3. Your files stay where they are - Kumiho stores the history.
Register revisions
Use plugins or SDKs to register outputs. Capture prompts, metadata, and links between versions.
Query & automate
Search history, see what depends on what, and automate follow-up work.
Product preview
See history at a glance
Every revision stays attached to the prompt, model, and settings that created it. Search by context, not filenames.
Your Storage
Files stay here
Kumiho History Layer
Stores the context
You
Search, trace, automate
Find your path
See how Kumiho fits your workflow
For Creators
Turn messy output folders into a searchable library
- Never lose prompts, models, or seeds
- Find the exact version in seconds
- Share a clean version without losing history
For Studios
Know what changes will break before they do
- See what is connected at a glance
- Lock published revisions
- Keep everyone aligned on the latest
For Developers
Build on stable APIs for creative history
- SDKs for Python, C++, and Dart
- Permanent asset links (kref)
- Webhooks and events for automation
Frequently asked questions
Do I need to upload files?
Nope. Files stay where they are - local disk, NAS, or S3. Kumiho stores references and metadata, not your actual files.
Can I start small?
Yes. Start with one folder or one workflow. Expand when it proves value. No all-or-nothing commitment.
Is it safe?
Published revisions are immutable (once locked, nobody can mess them up). Access is controlled through your workspace permissions.
How is this different from a DAM?
Kumiho complements your DAM - it tracks history and relationships, not storage. Think of it as version control for creative outputs.
What kinds of assets does Kumiho support?
Images, video, workflows, datasets, and any file type you want to register. If you can point to a file, Kumiho can track it.
Is Kumiho for individuals or teams?
Both. Solo creators use it to remember their work. Teams use it for collaboration, governance, and shared visibility.
Ready to stop losing revision history?
Join creators and studios turning file chaos into a searchable history.
No credit card required. Start with one folder.