Your material, under your control.
Scoped roles, your own storage, and a record of who did what.
Book a demoSecurity at a glance
TPN Blue Shield
Origami holds a TPN Blue Shield.
Read the answer: TPN Blue ShieldMedia stays on your storage
At rest, your camera originals stay on your own storage, and files move only for a job or a transfer, over encrypted connections.
Read the answer: Media stays on your storageOutbound only
Origami Link connects out from your building, so nothing inbound needs opening.
Read the answer: Outbound onlyYour own bucket
Keep camera originals, project files and cache in your own cloud account, and Origami keeps only the index.
See how: Your own bucketPartners see their show
Invite a vendor onto a show and it reaches that show and nothing else.
See how: Partners see their showWho did what
Every job records who submitted it, when, and where it went, and exports as a PDF or a CSV.
See how: Who did whatSecure sign-in
Sign-in requires multi-factor authentication, with your own single sign-on on request.
Read the answer: Secure sign-inLeaks traced
Playback carries visible and forensic watermarking, so a leaked frame can be traced back to the person who watched it.
Read the answer: Leaks traced
So you know who did what
Every show is a promise about who can see what.
A facility’s whole business is other people’s material. Hand any of it to a platform and two questions come before any feature: who can reach this, and what happened to it. Origami answers both, for the whole company and for each show on its own, and gives you the tools to change the answer.
Full control, at the company and at the show
Organisations, teams, roles and policies, set once for the whole company or differently for one production. Invite another company onto a single show and it reaches that show and nothing else.
Full visibility of who did what
Every task on the platform is a job, and every job records who submitted it, when, and where it went. Pull the record for a production as a PDF or a CSV whenever you need it.
And who can do what, explained
Ask why a person can reach a show and the answer comes back as the chain of grants that gives it to them, most direct first. Revoke one and it is gone immediately.
Why does this person have access?
Priya Raman
On the roster for Kestrel S2
Three sources of access
Their own role on this project
MemberSubmits, views and cancels jobs on Kestrel S2.
Their organisation, which owns the project
Projects memberGranted across the organisation, not for this show alone.
A seat taken through their company’s participation
ContributorSees the work shared with their organisation here.
Take one of those away and the answer changes in front of you. Remove the person and every route is cut at once, keyed on their Origami record rather than on whichever login they arrived through.
The record itself is tamper-evident: every entry carries the fingerprint of the one before it, and once a day a fingerprint of the whole is written to storage the writing system has no permission to delete, and kept for three years.
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
Questions about security
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.