Storage, solved.
Every location, every kind of storage and every copy, as one place to work. Origami handles the rest underneath, and your media stays where it is.
Book a demoFiles all over the world. One place to work on them.
A SAN in London, a NAS in Los Angeles, shoot drives in Toronto, a facility in Sydney, and buckets in two clouds, one of them holding backups. Origami reads each of them where it is, and shows every file and every copy in one place. Where a file lives stops being your problem.
One place7 files, 11 copies, 6 storages- A001C001.ari
SANBackup bucket - A001C002.ariSANS3 bucket
- A002C004.movNAS
- B001C005.ariShoot drivesBackup bucket
- Sound roll 03.wavShoot drives
- VFX_0410 plates.exrFacility
- Reel 4 offline.movNASS3 bucket
Origami Link · on-premCloud bucket- Every kind of storageA SAN, a NAS, loose drives or any S3 bucket. On your own kit, point Link at a folder.How it works
- Your own bucketKeep camera originals, project files and cache in your own cloud account.How it works
- Copies in more than one placeBackups and duplicates are known copies, and each job reads the best one.How it works
- Teams around the worldEach job runs where it makes sense, and moves only the frames the cut names.How it works
S3 providers
- AWS
- Backblaze
- Wasabi
- Storj
- Lyve Cloud
- MinIO
Origami Link
Install it once. Your own storage joins Origami.
Link is a small app for the machine next to your storage. It reads your media where it is, sends only what each job needs, and receives deliveries straight onto your storage. Mac, Windows and Linux.
- Connect
- Point Link at each storage you want in Origami: the SAN, the NAS, the shoot drives. One Link serves them all, across many projects, runs quietly in the background and updates itself between jobs.
- Read in place
- Link indexes each volume where it sits and reads the camera and audio metadata off the files, with the ALE, OMC and ScriptE files beside them. Scheduled scans keep the index current. Your media stays put.
- Send
- When a job needs a shot, Link trims it on your machine and sends only those frames, with handles. The rest of the clip stays on your storage.
- Receive
- Send a delivery to a Link and it lands straight on that storage, in your folder structure and named to your rules. Files already there are skipped, and nothing half-written ever appears.
Secure by design
Link only ever connects out, over an encrypted connection, so nothing inbound needs opening in your firewall. Your originals stay on your storage, and each job takes only what it needs.
Connecting a storage takes three steps.
Enter this code into the Link application running on your server.
Storage code
Copied to clipboard
Origami LinkStorage Code
Volume Path
Cache Directory
Volume Path
Last scan finished just now, 3,880 assets
Metadata files read
Your own bucket
Your files, in your own account.
Camera originals, project files and cache, all in your own cloud account. Origami reads them through access you grant, and keeps only the index. A project can move into your bucket, and back.
Your account
- Camera originalsConnected as a source storage and read in place.
- Project filesUploads, proxies, thumbnails, LUTs and clip lists.
- CacheRenders and files on their way to a delivery.
- AWS
- Backblaze
- Wasabi
- Storj
- Lyve Cloud
- MinIO
Storage priority
Three copies of one file. Origami reads the right one.
Backups and duplicates stop being a headache. Rank your storages once, and every job reads each file from the best copy: first in your priority order, or the cheapest or fastest to move. If a storage is offline when the job runs, the next copy is read.
Origami reads the copy on your highest-ranked storage that is online when the job runs.
Priority order, left first
- 1SANSANLondon
- 2NASNASCardiff
- 3DrivesDrivesCutting room
- 4S3AWS S3London
- 5WasabiWasabiBucket
A001C001
A001C002
A001C003
A002C001
A002C004
A002C007
B001C002
B001C005
B002C001
B002C003
C001C001
C001C006
5 read
3 read
2 read
1 read
1 read
Drag a storage to re-rank it, switch one off, or click a copy to pin its file there.
- Read
- Copied locally
- Pinned
- Waiting
- Copy held here
When a conform is delivered to a Link that already holds a copy, that copy is used first in every mode: the Link copies it locally, so it is never uploaded. Every copy shows where it is, Link or bucket, and its path.
And the conform runs where it makes sense.
Not every job should go to the cloud and back. Origami picks the route per job, moves only the frames the cut names, and when both ends are on the same Link machine the media never leaves the building.
Four stores, one grading volume
OrigamiFour stores of rushes, two of them at other sites. Only the frames the cut names move to the grading storage; the rest stays on the shelf. The remote shares arrive through Origami, because separate Link machines never count as one.
Copying locally covers conform and transfer jobs, when it is switched on for the project. A VFX pull renders in the cloud, and so does any job going out to more than one recipient.
Questions about storage
Take Origami for a spin with your own material.
A twenty-minute demo on a call, then a demo account on your own footage: pulls, conforms, deliveries, colour carried with the frames, and your AI assistant driving it.