Render a scene on vfrey’s servers in an isolated container, paid in render-minutes and credits.
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.
Rendering on your machine is free and stays that way. Cloud rendering is for teams that do not want to render on their own machines. A render job runs in its own container on vfrey’s servers, and the finished video lands in your cloud project.
A member sends the script, the scene, and the voice. The voice is made before the job by the paid voice provider, because the macOS say voice does not exist in the cloud.
The job waits in a queue, then starts in a fresh container.
The container renders the video, runs the quality checks, and returns the MP4 and the transcript.
The video and transcript are copied into the project’s storage, where the hosted dashboard plays them. The console’s Render page lists your jobs: status, render-minutes, credits, and a link to the video.
A job ends as succeeded, rejected (a failed quality check), failed, or timeout.
Scenes written by an agent are code, so they run in a locked box:
No internet. The container has no route out. A scene that tries to fetch anything from the web fails, and the render path also blocks every outside request inside the browser.
No standing permission. The container holds no access to your storage. It gets one link to read its inputs and one link per output, each for one file and good only for the job’s length. Even a scene that stole those could not read another organization’s files.
A fresh box each time. Every job gets its own container, run as an ordinary user with no extra rights, with limits on CPU, memory, and time. Nothing carries over to the next job.
Cloud rendering is open to every plan. It needs enough free credits: 10 credits per output minute, billed per started 15 seconds.
Before the job: vfrey estimates the render-minutes and holds the credits for them. Held credits are not charged yet. The price is on Plans and credits.
After the job: the real render-minutes are recorded once and charged in credits. A scene that fails or times out is charged, because it used the machine. A failure on vfrey’s side is not charged and is retried once.
npx vfrey whoami shows render.minutes and your balance.
If you are short, the call stops with credits_required and a link to buy a top-up. See Plans and credits.
