Gendo: the renderer that will not tell you what it runs

Ask Gendo which model made your image and you will not get an answer. That is not evasion; it is stated policy. The company's published principles include a line — outcomes over models — which commits it to hiding engine selection from you entirely. Everything else about the product follows from that decision, including the parts that make it the most credible AI renderer in the category and the part that should give a practice pause.

What it is and who makes it

Gendo is a browser-based collaborative canvas for architectural visualization, made by a UK company of the same name founded in 2022. It has raised £5.2 million from Concept Ventures, Ascension, PT1 and LEA Partners, and sits in NVIDIA's Inception program. George Proud is CEO and co-founder, Will Jones co-founder and CTO. The name comes from Dürer's 1515 rhinoceros woodcut, made from a written description of an animal Dürer never saw — a text-to-image exercise five centuries early. Gendo was the rhino's name.

The company says it has 200,000-plus architects and designers signed up, and shows Zaha Hadid Architects, KPF and ICRAVE as customers. Both are vendor claims, unaudited.

The product's shape matters more than the funding. This is not a render button bolted onto a viewport. It is a shared multiplayer canvas — closer in feel to a pin-up wall than to a render queue — where variations sit side by side, teammates comment, and decisions get made in view of the alternatives. Gendo is aiming at the design review, not the render farm.

Where it sits in your week

Earlier than most AI renderers, and it stays longer.

The entry point that matters is source-file rendering. Export from SketchUp, Rhino, Revit or CAD, drop it on the canvas, and Gendo renders it while holding the geometry you built. No plugin, no remodelling, no round-trip. That single capability is what moves it out of the mood-board category and into the working week.

From there it covers the arc. Sketch-to-scene for a napkin drawing at concept stage, text-to-image when nothing is modelled yet, material transfer and lighting changes through the middle when the argument is about cladding and time of day, entourage, then upscaling and short video for the pitch at the end.

The vendor's own case study is instructive about where the value lands: a practice stuck at pre-application for months took a rendered version of a hand sketch into the meeting and got the planners on board. That is not a rendering benefit. It is a communication benefit, and it is the honest argument for the tool.

What it is genuinely good at

Holding your geometry. Of the hosted renderers, Gendo is the one built around design adherence as the first requirement rather than a setting, and it shows in outputs that follow your massing instead of drifting toward a generic computer-generated look.

The tool vocabulary is the second thing, and it is more significant than it sounds. The commands are Material Transfer, Populate, Enhance, Style Transfer, Box Edit, Pencil — named for what architects do rather than what the model does. Nobody is asked to reason about denoising strength. Box Edit in particular earns its place: select a region, change only that, leave the rest of the composition alone. Small changes stop costing you the whole frame.

Parallel rendering suits how the work is actually reviewed. Generate variations simultaneously and the meeting compares rather than waits.

And the governance story is the cleanest in the category. On Studio plans and above, projects are private by default, workspace data and generated content are not used for training, the commercial licence is described as client- and NDA-safe, and multi-factor authentication is standard. For a practice that has to answer a client's data question in writing, that is a short and unusually satisfying answer.

Where it breaks

The model opacity is the real cost, and it is not a small one.

You cannot audit what made your image. You cannot reproduce it anywhere else. You cannot tell when the engine changed underneath you, because Gendo updates its orchestration without announcing it. For most work this is exactly the relief it is meant to be — you did not want to manage a pipeline. But the day an image goes into a planning submission and someone asks what in it was invented, the honest answer is that Gendo made it, and no more detail is available. Architects have always signed work produced in software they did not write. They could, until now, name the software and its version.

Design adherence is also a ceiling. Creative range is narrower than a general model shelf, deliberately, and if you want an image that departs from your geometry you are fighting the product's central premise.

The free tier is not a professional tier and should not be mistaken for one. Projects are public, exports are watermarked and capped at 1k, and there is no commercial licence. Client work has no business there.

"Unlimited" generation is governed by a Fair Use Policy whose thresholds are not published. Video is metered separately from images: 15 free seconds, then paid packs. And the ordinary limit still applies — nothing Gendo produces is measurable, dimensionally reliable, or a substitute for a drawing.

What it costs, what it asks

Browser only. No plugin to install, and none needed; you work from exports.

Prices from Gendo's own pricing page, checked September 2026, excluding tax and quoted in sterling. Free: £0, one canvas, 50 assets, watermarked, public. Studio: £79 a month, or £66 a month billed annually at £790 a year, covering up to five team members with unlimited projects and generations, no watermark, 2× and 4× upscaling, private workspaces and 15 one-off video seconds. Studio Scale: £299 a month for five seats with unlimited video, currently at early-access pricing. Enterprise: custom, minimum 20 seats, adding SSO, custom trained models and a dedicated account. Video packs run £40 for 100 seconds down to £125 for 500. Students and educators with a .ac or .edu address get a free licence for non-commercial coursework.

For a five-person studio, £790 a year is roughly two days of a visualizer's time. That is the comparison the pricing is built to invite, and it is a fair one.

Who should bother

The principal: this is the one in the category worth your attention, because the answer to "where does our client's model go" is written down and it is a good answer. Price it against what you currently outsource at concept stage.

The project architect: yes. Source-file rendering from an export you already produce is the feature that changes your week, and Box Edit is the one that will stop you dreading revisions.

The graduate: you will find it constraining, and that is the point. Fewer knobs, less drift. Take the free student licence and learn the workflow, then go elsewhere when you want to experiment with engines.

Watch rather than buy if broad stylistic range is what you need, or if you work in a context where you may be required to state what produced an image.

Gendo's bet is that architects want to stop thinking about models — and for most of the work, most of the time, it is right. But abstraction moves accountability rather than removing it. The image still goes out under your name, and the engine that made it now has no name at all. That is a professional trade, not a technical one, and it is worth making deliberately.