A proposed deploymenton your premisesor in the cloudin phases
How Cyan would be deployed: the work travels to your footage, the record travels everywhere.
Two ways to run Cyan, and we favor the first. On your premises, the way we have built it twice: a rack beside your storage, a heavy room, a regional room. Or in the cloud, the way Cyan runs today: you edit, color or observe from anywhere, and the floor keeps the beat. Either way raw media stays where you keep it, the seats share one record, and only small things travel between rooms.
Your footage stays putEngines run where the media root lives, your floor or your cloud storage. Conform, grade and render happen beside it.
The record is yoursBoards, notes, approvals and the cut's history sync between your seats, on your rack or in your cloud account, never on ours.
Only small things crossProxies, looks, comments, approvals and workflow definitions move between rooms. Masters are delivered from the site that made them.
On your premises the way we favor — the two-site build we have run
Your siteHalf rack: the engine by your storageYour storage: originals and mastersThe chairs and their tools, at the deskOriginals and masters never leave the floor
- The recordboth ways
- Looks and proxiesback to your site
The heavy roomFull rack: models, render, the recordMetered per outlet
- The recordboth ways
- Render overflowfrom the regional room
A regional roomSeats: editors in another cityIf the link drops, the floor keeps working
In the cloud how Cyan runs today — edit, color or observe from anywhere; the floor keeps the beat
The cloud · four things, and nothing of yoursCyan's own models: read the day, judge the lookThe relay: seats reach each other, anywhereThe bootstrap: the first hello, a seat finds its floorYour super peer: keeps the studio's record
- A sentence, a frameup to the models
- The beat, a judgmentback to the floor
The floor · everyone knows their part and dances to the beatOne shared record; roles say who acts; the workflow ticks on its ownThe editor cuts, the colorist grades, the assistant stages the day, the post supervisor observes, each from anywhereThe rack by the storage renders; originals stay
A phased build-out, as proposed
A second studio is the same playbook beside its own media. A rack grows when sustained GPU use passes seventy percent; a cloud room grows by the hour. Either way, every step carries its time and its cost.
What we need from you to start- Where the media root lives, and how it is shared.
- A rack slot with power, or a cloud account, for the first room.
- The seats' machines and their DCC licenses: Premiere, Resolve, Pro Tools.
- Who sits in which chair on day one.
What you get in the first week- A show set up from one sentence, on your floor.
- One shoot day run end to end: arrival, dailies, rough cut, lock, hand-offs.
- Every step receipted and metered on your own record.
- A walk-through with each chair at their own screen.
