Your own studio, in about five minutes
We set up a complete Vivijure studio for you: you write a storyboard, and it renders to video on real GPUs. You never install anything.
The GPUs are yours, not ours. We create four render endpoints on your own RunPod account. You pay RunPod for the seconds you render, directly. We take no cut, and there is no vivijure bill in this tier.
What gets created on your RunPod account
Nothing is created until you say go. You will see this exact list again, with your real numbers, before anything happens.
Idle costs you $0. Every endpoint is scale-to-zero: when nothing is rendering, nothing is running, and nothing is billed. Not "a few cents." Zero.
loading a real example...
Hosted and self-host ship the same studio. Features never gate on payment.
You are not signing up for a limited edition. There is no paid tier with more features, because there is no paid tier. The hosted door itself is open source, so you can read exactly what we run, or run it yourself. Install it yourself instead.
The rules
Short version: make films, do not make the things on the list.
Name your studio
This becomes your studio's web address. Pick something you will not mind typing.
Lowercase letters, numbers, and dashes. A few names are reserved for us.
Your RunPod key
We need one key, once, to build your four endpoints. Then we are done with it and you can delete it.
Make the key
In your RunPod console, create an API key with the Restricted setting:
This is the invoke surface. Setup does not need it.
Open your RunPod key settings -- that is the smallest key that can still create endpoints. We checked it against the real API rather than trusting the docs.
Being straight with you: this key is powerful while it exists. RunPod has no "may only create endpoints" permission, so a key that can create your four endpoints can also create pods anywhere on your account. RunPod calls this level of access "extremely powerful" themselves. There is no smaller key that does the job.
So: we use it once, we hold it in memory only while we build, we never store it, and the last screen walks you through deleting it. What your studio keeps afterwards is a much weaker key that can only run jobs on your four endpoints (a 403 on anything else, and it cannot change your settings at all).
Your account's real capacity
RunPod caps how many workers you can run at once, across your whole account. We read your real number from RunPod instead of guessing it from their published balance chart, because we have seen that chart be wrong.
Review, then we build
This is everything we will create on your RunPod account. Last stop before anything happens.
We pin the worker count on each endpoint ourselves rather than taking RunPod's default of 3 each. Four endpoints at that default would ask for 12 workers and fail on most accounts.
Building your studio
This takes a few minutes. If a step fails you get the real error, not a shrug.
One more key, and this is the last one
Your four endpoints exist now. This second key is the one your studio keeps, and it can only do one thing: run jobs on these four endpoints. Nothing else on your account.
Why twice? RunPod only lets you create keys in their console, and a key can only be locked to endpoints that already exist. So the first key had to come first to build them, and this one can only be made now. We would have merged these two screens if RunPod let us.
These are the four we just created
Tick exactly these in the console, and set each to Read/Write. The names are here so you can match them instead of guessing.
The click path
- Open your RunPod key settings and create a new API key.
- Choose Restricted.
- Set api.runpod.io/graphql to None. This is the part that matters: it is what stops this key from touching the rest of your account.
- Set api.runpod.ai to Restricted, then give Read/Write to the four endpoints listed above, and nothing else.
- Create it, and paste it below.
We check this key before we keep it. We try your four endpoints with it, and we try an account-level call that should fail. If it turns out to be more powerful than it needs to be, we tell you and we do not store it.
Your studio is live
Go make something.
One last thing: delete the setup key. That is the first key you pasted, the powerful one. We never stored it, and we are done with it. Delete it or rotate it whenever you like; nothing here breaks, because your studio does not have it.
What we keep, in full: your render key, and nothing else. It can start and check jobs on your four endpoints. It cannot create anything, cannot touch the rest of your RunPod account, and cannot even change those four endpoints' settings. If it leaked tomorrow, the worst anyone could do is render films on your four endpoints.
If you ever want out. Your storyboards and render history live in your own database, and your films live in your own storage bucket. Delete your studio and we offer you the export first: a SQL file and your files, yours to take. Your RunPod endpoints were always yours.
If you do not render for a week, RunPod puts your endpoints to sleep. After 7 idle days it sets them to 0 max workers and leaves them there. Nothing is lost; the number just needs raising. Your studio will spot this and tell you how to fix it rather than failing a render with a confusing error.