For twenty years, architects owned their renderers in the most literal sense. You bought V-Ray or Corona, the software ran on boxes in your office, and if you liked version 5 you could keep running version 5 until the hardware rusted. The vendor could raise prices on the next version, but the one on your disk kept producing the same pixels forever. That arrangement shaped how firms planned: a renderer was a capital decision, made rarely, amortized over years of identical output.
AI rendering quietly deleted that arrangement, and this week a vendor finally said so in writing. The model weights that turn your massing into a photograph live on servers you will never see. The plugin in Revit or SketchUp is a thin client, a well-dressed upload form. This is not an accusation, it is the published architecture of nearly every tool in the category, confirmed by the company that sells the most prominent one.
Four dependencies you signed without reading
1. The engine can change under your project
When the model behind your renderer is server-side, the vendor can swap it whenever they choose, and they do. Veras has already replaced its underlying engine more than once this year, and output character shifted with it. Better on average, yes. But if you are eleven images into a fourteen-image planning set and the engine changes on a Tuesday, your remaining three images will not match the first eleven, and no setting brings the old behavior back. We wrote about set consistency as a craft problem; cloud engine swaps make it a scheduling problem too. Finish sets in tight windows. Do not let a presentation series straddle a vendor's release cycle if you can help it.
2. The price is a dial, not a tag
Cloud renderers meter usage in credits, and a credit is worth whatever the vendor says it is worth this quarter. Chaos has already reorganized how Veras credits flow across its product line once this year. Midjourney sells fast hours that evaporate at month's end. None of this is scandalous, but notice the asymmetry: your old perpetual license could not be repriced retroactively. A credit meter can. The subscription line in your overhead is a floor, not a ceiling, and the ceiling moves in the vendor's favor during exactly the weeks you render most.
3. The queue does not know about your deadline
Every remote render shares capacity with every other customer's remote render, and demand peaks for everyone at the same time: end of quarter, competition season, the Monday after a major model release. A local GPU renders at 2 a.m. the night before a submission at the same speed it renders in April. A cloud queue does not make that promise, and an outage the night before a deadline is not a hypothetical, it is a status page you will refresh with your heart rate climbing. If your delivery process has no offline fallback, your deadline risk is now partly someone else's uptime chart.
4. Your massing model leaves the building
Every render is an upload. For most projects that is fine; for some clients, NDAs, competitions, and public-sector work, it is not fine at all. We covered the contractual side in our piece on client confidentiality and cloud rendering, so here we will only repeat the operational rule: know which of your active projects can legally ride a third-party server, and route the others down a local path before the question gets asked in a deposition.
The old renderer was a tool in your office. The new one is a counterparty in your workflow.
What still runs on your machine
The honest local list in mid-2026 is short. ComfyUI with SDXL or Flux weights on a decent GPU is the one genuinely self-contained AI render path: the model files sit on your disk, and the workflow you saved in January produces the same output in December, which no cloud tool can promise. The real-time renderers, D5, Twinmotion, Enscape, Vantage, still compute their core images locally, though their newest AI extras mostly phone home. Even Photoshop's generative fill is a server round trip. That is the whole map. One fully local AI path, a family of local renderers with cloud-attached AI features, and everything else remote, exactly as the Chaos FAQ says.
This is not an argument for moving your practice to ComfyUI. We have been clear about the hardware reality: the cloud tools exist because most firms do not want to own GPUs, and for day-to-day concept work the convenience trade is worth it. The argument is narrower. Keep one local path proven and current, the way you keep a fire extinguisher inspected. You are not planning to use it. You are planning to have it.
The playbook
- Archive outputs the day they are accepted. The render your client approved may be unreproducible after the next engine swap. Save the image, the prompt, the settings, and the source view together, locally, same day.
- Do not let image sets straddle vendor releases. Batch a presentation series in one sitting where possible. Consistency is now partly a calendar problem.
- Read the processing sentence before adopting anything. Every tool's FAQ now contains a line about where renders are computed. Find it, and file the answer under risk, not trivia.
- Budget credits like a utility, not a license. Track one heavy month, then assume the price per useful image drifts upward and re-check quarterly.
- Keep one offline route rehearsed. A ComfyUI workflow that works, or simply the discipline to ship a raw Enscape frame with Photoshop cleanup, no AI required.
Our take
Nothing in this argues against cloud AI rendering. We use it daily at Vista Studios, and the output-per-hour case is not close. But the sweep this week put the vendor's own words on the record, and the words deserve a sober reading. When Chaos tells you the rendering happens on remote servers, it is telling you the terms of the relationship: continuous improvement in exchange for continuous dependency. Most weeks that trade favors you. The weeks it does not, deadline weeks, engine-swap weeks, repricing weeks, are precisely the weeks you cannot renegotiate.
Your geometry is yours. Your drawings are yours. The pixels, for now, are on loan.
Written from the July 12, 2026 intel sweep: Chaos's six-option AI rendering comparison and its FAQ on cloud processing, plus this week's r/archviz and r/comfyui threads on local workflows. Engine and credit-system history from our prior Veras coverage. No affiliate relationship with any tool named.