There is no price list yet, on purpose: the hardware a library needs is the biggest variable, so we size it with you rather than guess. The way to start is a demo, on our footage or on a sample of yours.
Sized to the deployment, not to the month.
Team
Single node.
One machine, one library, a handful of people. The right shape for a production company or a department proving the idea on real footage.
Studio
Multi-user.
Several editors and researchers working the same archive, with teams, collections and permissions that mean something.
Enterprise & secure
Multi-node.
More than one node, larger libraries, and sites that have to run with no internet connection once installed. Where the compliance conversation happens.
The important parts are in every shape.
Included, always
- Self-hosted
- Every deployment runs on your own hardware, so privacy is never an upgrade.
- The full index
- Everything Mokuji reads, in every deployment. Not a feature matrix. It is one index, and it either works or it does not.
- The API
- Documented, in every deployment. Your data is not held hostage by an integration fee.
- Export
- Timeline XML, CSV and metadata sidecars. Leaving stays possible, by design.
- No meters
- No per-minute processing charge and no egress fee from us. You run it, so there is nothing to meter. If you turn on cloud processing, your GPU provider bills you directly.
Talk to us about an early deployment.
Tell us roughly how much footage you have and how many people need it. We will show you Mokuji on a sample of it, then size a deployment to fit.