Skip to content
Fluxx

Cloud-Side Operations

Retired 2026-09-24 (ledger A12, the second pass). This page described a cloud compute layer under a name since retired, with a vault, a VM lifecycle and per-tenant cost attribution that are no longer in the plan; its prior body is kept whole at 02_Working/Archive/Wiki_pre_second_pass_2026_09/process/cloud-side-operations.md. What follows is the current chain, from 02_Working/Strategy/Company_Overview/FLUXX_DESCRIPTION_2026_09.md and 02_Working/CLI_Briefs/THE_ANSWER_3.md.

Where each render runs

The floor postvis does not go to the cloud. It renders on the stage’s own render node within minutes of cut, at half or quarter resolution, so the director decides on the floor. The cloud does the rest: a 2K postvis and the full-quality deliverable, per selected take, with no time constraint.

Fluxx Automate runs it. One hub on the stage, one in the studio, and the cloud is the studio’s farm, nothing replicated. The hubs talk to service agents, small containerised workers on the storage and render machines, and to bridge services that launch and supervise the animation and compositing applications from outside them. When a take closes on the cart, the watcher on the stage store indexes it, Automate pairs it to its scene package by the production’s own identifier, renders the floor version on the stage node, and, once a take is selected, makes the full-quality footage, sends the 2K version and the finished render to the cloud farm, and pulls the results back into the take’s own directory.

Files are truth, databases are views

Every take is one immutable directory closed by one rename, with its manifest and checksums, its identity, its verdict, camera.usd in centimetres, lens.nk, and every device’s native bytes beside the common format. Automate’s database is an index that can be dropped and rebuilt from the files at any time. Storage on the stage is a NAS on 10 GbE, and the watcher on it is keyed on the manifest rename; the collector makes no call toward post.

Verification without a gate

An agent reads every take’s verdict, the raises, the pairing and the render’s own log, looks at frames when the production’s security terms allow it, and writes a flag and a reason. A message goes out for the flagged ones and nothing blocks. There is no human gate on the production path, by decision. The agent’s reach is set by what the record can prove; where the data cannot carry a decision the step is a raise on the panel, not a guess.

What is not in the plan

The content-addressed vault, the pipeline-owned VM lifecycle, the artist virtual workstation, per-tenant cost attribution and the multi-tenant topology described on the archived page are not in the current plan. Artists working from virtual machines, finishing shots as they wrap on set, is the horizon beyond Phase E, stated as a direction and not dated. No cloud provider is chosen.

Cross-references

Audience visibility

industry, vendor, investor, counsel.