Mokuji is built to slot into the workflow you already have, feeding your editors, your storage and your other systems in formats they already speak. There is no rip-and-replace, and no year of migration before anybody sees a result.
Search from inside the timeline.
A panel inside Premiere Pro: search the whole library, preview a result, and drop the clip onto the timeline at the detected in and out points, with the logging markers already attached.
What goes in and out
- Premiere Pro panel
- Search, preview, and import clips or sub-clips at their detected timecodes, carrying markers onto the imported clip.
- Timeline export
- Sequence XML your assistant already knows how to open.
- Pull lists
- CSV, for the people who live in a spreadsheet and are not going to stop.
- Sidecars
- XMP and IPTC sidecars on request: the people and places Mokuji found, plus the descriptions and keywords your team has entered, written next to the asset in standard fields.
- Everything else
- A documented REST API. If a workflow is not in this list, tell us what it is and we will tell you how close it is.
Replace, or reinforce.
Mokuji separates its asset layer from its intelligence layer, so it can hold the library itself, or leave your system of record where it is and make it far smarter.
Mokuji as your library.
Upload or watch a folder into a managed store, with its own library, collections and rated selects. Archiving masters to cold storage and bringing them back without relinking is on the roadmap.
Alongside the one you have.
Point it at your existing storage and let it index in place. Results reach your edit through the panel and exports, and sidecars in standard fields are available on request. Nothing moves.
Want it wired into your stack?
Tell us what is already in the room: the editor, the storage, the asset manager, and we will tell you how well this fits.