This needs the hosted vfrey service, which is not live yet. Everything on this page describes how it will work. Nothing here changes how vfrey works on your machine: local projects, rendering, and the dashboard stay free and need no account.
A cloud project is your local project, synced. The local project stays the real thing: you can keep working offline and on your own machine. A hosted copy lets a team see runs, watch videos, and edit scenes in a browser.
Every one takes --api URL (the default is VFREY_API_URL).

​
What syncs

  • Always: scenes (scenes/) and scripts (scripts/), and run details.
  • Only with --videos: finished videos and their transcripts (videos/). They are large and count against your storage.
  • Nothing else. Your keys and secrets stay on your machine. Only paths under scenes/, scripts/, and videos/ sync, and hidden files and paths that climb out of the project are refused.
There are size limits per file and per push. A push that goes over one says which.

​
Conflicts

If a file changed in both places since your last sync, the newest copy wins and the other is kept next to it as FILE.conflict-TIME. Push stops on a conflict and tells you to pull first, so nothing in the cloud is overwritten by accident. Open the .conflict file, copy what you want, and delete it.

​
Storage and quotas

Each organization has a private storage space. Videos are played through links that expire after a few minutes. The space is set per plan, and the console’s Billing page shows yours. Usage is measured as GB-month and shows in npx vfrey whoami as storage.gb_month. A push that would go over the limit stops with a limit_reached error. See Troubleshooting.

​
The hosted dashboard

The console lists your cloud projects, their runs, checks, and videos. It looks like the local desk, but it is a separate page that shows what you pushed.