Creative history should be automatic.
Creative work outgrew folders.
What slows teams down is not making new work — it is losing context: which version is correct, how it was made, and what depends on it.
Kumiho records every revision and lets you define relationships — while your files stay on your own storage.
What Kumiho does
Keep files where they are
Local drives, NAS, or S3. No migration required.
Track what changes
Revisions, dependencies, and lineage — all connected.
Trigger automation
Events fire when assets change. Plug in your workflows.
Think "version control for creative work" — but designed for images, video, workflows, datasets, and studios.
Who we are
We are a small team of creators and pipeline engineers.
We have spent years watching great work get lost in filename chaos — and watching studios rebuild the same internal tooling to track revisions and dependencies.
Kumiho is our attempt to make that capability available without the infrastructure burden.
Why we can execute
- Built creative pipeline tooling at scale (VFX / animation / AI workflows)
- Shipped production software used by teams (plugins, SDKs, automation)
- Deep experience with asset lineage, revisioning, and distributed systems
Why now
AI output explosion
Revisions and variants scale dramatically. Manual tracking breaks down.
Reproducibility matters
Governance and provenance become requirements, not nice-to-haves.
Automation needs context
Events need reliable asset context. Pipelines need to know what changed.
When your work becomes more automated, your asset system must become more operational.
Why BYO storage matters
Keep your files, skip the cloud storage bill
Storage Cost Comparison
Traditional DAM duplicates your files. Kumiho stores only metadata.
Files must be uploaded to their cloud
Files stay on your local/NAS/S3
That's 100% less than a traditional DAM
Based on AWS S3 Standard pricing (~$23/TB/mo). Your actual costs may vary.
DAM vs Kumiho
Different tools for different jobs
| What you need | Traditional DAM | Kumiho (AOS) |
|---|---|---|
| Where the file is | ✓ Primary focus | — Not the focus |
| What changed over time | Limited | ✓ First-class (revisions) |
| What depends on what | Usually implicit | ✓ First-class (lineage) |
| Automation triggers | Limited | ✓ Built-in (events) |
| Works with existing storage | Sometimes | ✓ Yes (BYO storage) |
If you love your DAM, keep it. Kumiho complements it by tracking change + relationships + automation.
What is real today
Not just ideas — shipping software
Our approach to growth
Wedge: Creator plugins + desktop
Start where the revision explosion is worst (AI outputs). Plugins capture structured context automatically. Low friction entry for individual creators.
Expansion: Studio workflows + SDK ecosystem
Once assets are structured, studios adopt for impact analysis, governance, and automation. SDK enables custom integrations into existing pipelines.
Moat: Graph + event layer + adoption gravity
The system compounds: more revisions → richer lineage → better automation → higher switching cost. Network effects from shared asset references across teams and tools.
Business model aligns with operational complexity: usage-based pricing scales with value delivered.
Ready to preserve your creative history?
Join creators and studios who are tired of losing context.
No uploads. No lock-in. Works with your storage.