Loading...
Loading...
Education & Research
Students and research labs can render on GPUs without buying a workstation or queuing for lab time. Every job is priced before it runs, and a budget cap with auto-stop means a class cannot overspend. Academic pricing for verified .edu and .ac addresses is rolling out.
The work that does not fit on a laptop: final-quality frames, animation sequences and scripted compute runs. The publicly available integration is the Blender add-on, which submits Cycles renders straight from the viewport — its render lane is still completing production qualification, so plan a dissertation deadline with that in mind. Browser-based tools need nothing installed at all, which matters on locked-down lab machines where students cannot install software.
This is the question that actually decides whether a course can use cloud rendering, and it has a concrete answer. Every job is estimated in hours and dollars before it runs, and settlement is capped at the quote that was approved — the estimate is a ceiling, not a guess. Each account can then carry a hard USD budget with an optional auto-stop threshold that pauses new tasks at a chosen percentage of the cap. A student who leaves 4K samples on a 900-frame animation hits their own ceiling and stops, instead of discovering the mistake on a departmental invoice weeks later.
Sign-in is a browser-based OAuth 2.0 login — magic-link email, Google or GitHub — with one account per person, so per-student usage and per-student budgets stay separate. Departments and labs can use SAML single sign-on. On shared machines this matters more than it sounds: desktop plugins keep the session in the operating system keyring, so there is no raw API key sitting in a config file on a lab workstation that thirty people use.
Discounted pricing for verified .edu and .ac institutional email addresses is rolling out. It is not live yet — we would rather say so than list a price nobody can claim. Creating your account with an institutional address is what makes it eligible when the programme opens, so use the university address rather than a personal one.
Running a whole cohort or a lab? Institutional billing, procurement timelines and per-student budget caps are handled case by case — get in touch with the shape of the course and we will tell you plainly what we can support today.
Set the shape of the job — GPU class, frame count and time per frame — for an indicative figure before you commit a project to it. The estimate shown inside the plugin is the one that caps what you are actually charged.
Estimated Total
*Pricing may not be accurate at the time of rendering
FAQ
GPU rendering and compute without buying hardware. The publicly available integration is the Blender add-on, which submits Cycles renders from the viewport; full production qualification is still in progress. Browser-based tools and scripted research workloads run through the same account and the same billing.
Discounted pricing for verified .edu and .ac institutional email addresses is rolling out — it is not live yet. Signing up with your institutional address now is what makes an account eligible when it lands, so use the institutional email rather than a personal one.
Two mechanisms stack. Every job is estimated before it runs and settlement is capped at that quote, so nothing costs more than the number that was approved. On top of that, each account can carry a budget — a hard USD cap — with an optional auto-stop threshold that pauses new tasks at a chosen percentage, so a mistaken 4K setting on a 900-frame animation stops rather than draining a departmental card.
There is no local GPU to buy and no render farm to set up. Browser-based tools need nothing installed; rendering from Blender uses the downloadable add-on, whose render lane is still completing production qualification.
A browser-based login using OAuth 2.0 — magic-link email, Google or GitHub — with one account per person. Departments and labs can use SAML single sign-on. Desktop plugins keep the session in the operating system keyring rather than storing raw API keys on shared lab machines.
Yes. The REST API with API keys and the plugin Python APIs both cover estimate, submit, status and output retrieval, so a coursework batch or a parameter sweep can be driven from a script rather than submitted by hand.
Talk to us before you set a cohort up. Institutional billing and procurement timelines are handled case by case — tell us the shape of the course or lab and we will tell you plainly what we can support today.