A render farm that shows its work.
Upload a scene, get a quote you can check to the credit, watch every frame land. Rented GPUs on a secure tier, priced by measured Blender performance.
If your render manager just went quiet.
Deadline 10 entered maintenance mode on 7 November 2025: security fixes only, and a steer toward a cloud service the studio did not choose. AnIso is a small, honest farm you can point a pipeline at in an afternoon, and we will do the afternoon with you.
How a render moves.
Four steps, each one visible in the console and the CLI. Nothing happens to your money or your frames off the record.
Upload
Scenes go straight to storage on a presigned URL. The server checks size and checksum before a file is called ready.
Quote
Rate × machines × frames × seconds ÷ 3600. You see the whole line before you submit, and the reservation equals the quote.
Render
One secure-tier GPU per job. Frames land in your studio's storage as they finish, each one visible the moment it does.
Settle
The ledger holds credits at submit and settles against measured seconds. The difference comes back as its own line.
Priced by what the card actually does.
Every rate is derived from the Blender Open Data median for that GPU, anchored on the RTX 4090 at 400 credits an hour. Faster cards cost more and finish sooner, so the price of a frame is roughly flat across the shelf. Pick for VRAM and turnaround.
1 credit = $0.01, always. credits / hour = Blender median × 400 ÷ 11,680, rounded to the nearest 5. 4 of the 7 cards on the shelf; the full card, the CPU rate and the reason there is no A100 are on pricing.
Credits, prepaid.
Packs from $25 to $2,000, always at one credit to the cent. Volume comes as extra credits, never as a cheaper credit, so the ledger means one thing forever. During the beta, credits are granted by us and the console says so on the balance.
What it does not do yet.
A beta should say so. These are the edges of the product today, in the order a studio would hit them.
- 01Blender 4.2 only. Other DCCs and the renderers that ride on them are out of scope for the beta; when they come, it will be bring-your-own-licence.
- 02One GPU per job, frames in sequence. Ask for more and the submit is refused, not quietly ignored. Fan-out across machines is on the road to beta.
- 03No container logs in the console. You get the full event history, the runner's status detail and every frame's state. Container logs are coming to the CLI's job logs.
- 04Secure tier only. Your scene never lands on a community host. Region is a deployment choice, not a promise; residency is enforced only when a client requires it.
- 05Credits by grant during the beta. Card checkout comes later; the console's balance says which it is.
Create a studio. Upload a scene. Get a number.
No card to start. The first thing you see is the estimate.