See the project as files.
The workstation design mounts a repository as a volume. Work with your usual creative applications and fetch file contents as they are needed, rather than downloading the whole production first.
VHS RUSH / COLLABORATION
Keep the work.
Keep how it was made.
File sharing and version control for directors, producers, editors, and artists working together in the generative AI era.
A production accumulates camera footage, generated takes, project files, and the context behind them. Rush is designed to give the team a shared place for that material and its history.
Talk to us about Rush ↗The workstation client is being developed macOS first. Get in touch to discuss access and your team’s requirements.
THE IDEA
Version control
for creative files.
Media and project files need a different approach from source code.
A video, a scene file, or an editing project usually cannot be merged line by line. Teams need to know what changed, which version they are using, and who is working on a shared part of the project.
Rush takes a Perforce-like approach: explicit submissions, version history, and folder locks. It is designed around large binary files and the people who work with them.
Submit a meaningful version.
Save locally as you work. When a group of changes is ready to share, submit it with a description. A submission gives collaborators a point in the history they can understand.
Coordinate shared work.
Lock a folder while you work on its files. Folder locks help a team avoid making competing changes to material that cannot be merged automatically.
PROMPTS & PROVENANCE
A file is part of the record.
For generated media, the context can be as useful as the output.
A producer may want to know which reference informed a shot. A director may want another take from an earlier prompt. An editor may need to understand which version was handed over.
Rush is designed to retain generation metadata with file revisions, so the record follows the work as it changes.
IN A PRODUCTION
Shared work, with context.
A director explores takes.
Generated media and the details behind it belong together. The team can return to a direction without relying on someone finding the right chat message.
An editor shares a cut.
Work on a project locally and submit at a useful milestone. The history captures a deliberate handoff rather than turning every application autosave into a shared version.
A producer follows changes.
Use a submission’s description and file history to understand what the team added or changed. The media and the record of the work stay associated.
A FEW DETAILS
Designed around real constraints.
Does every save upload automatically?
The workstation workflow uses explicit submissions. Files are saved locally as you work, and a submitted changelist records the changes you choose to share.
Does everyone need enough disk space for the whole repository?
The client design uses a local cache and downloads whole files on demand. A file has to fit in the available cache before it can be opened.
Is a Studio project automatically a shared canvas?
Studio is a local, single-user canvas for image and video generation. Rush serves a different role: sharing and versioning files and their records for a team.
How can our team try Rush?
Email us with your team size, the applications you use, and the kinds of files you work with. We’ll discuss the current client and whether it fits your production.