We spend a lot of time here auditing other people's tool roundups, because roundups are where most architects meet a render tool and roundups rot. Today's sweep surfaced a variant of the problem that is harder to dismiss, because the disagreement is not between review sites. It is between first-party pages. When the people who make and sell the software cannot describe it the same way on the same day, the usual advice, go read the vendor's own page, stops being a complete answer.
Three pages, three products
Here is what today's sweep returned, quoted from the pages themselves rather than paraphrased.
| Page | How it describes Veras | What it leaves out |
|---|---|---|
| chaos.com/veras | An AI visualization tool that transforms 3D models, 2D drawings and sketches into visuals and animations. Leads with a 500-credit allowance. | Which host applications, at which versions. |
| evolvelab.io/veras | An AI-powered visualization add-in for Revit that uses your 3D model geometry as a substrate. | Animation. Sketch and 2D input. Anything outside Revit. |
| architools.com (regional reseller) | Chaos Veras 4, filed under the Enscape section, framed around a major update to output quality and prompt adherence. | That it is a reseller page rather than the source. |
Read the middle row against the top row. One page sells you a Revit add-in. The other sells you a tool that ingests sketches and outputs animation. A practice on Rhino or SketchUp reading the EvolveLab description would reasonably conclude the product is not for them. That conclusion is wrong, and it was reached by doing exactly what we tell people to do.
We are not going to reconstruct the corporate arrangement behind those pages from three search snippets, and you should be sceptical of anyone who does. EvolveLab built Veras and Chaos sells it inside a much larger rendering line, which we covered when Chaos updated its whole product line at once. Whether a given page is stale, scoped to one audience, or maintained by a team that shipped it in 2023 and moved on, the buyer's problem is identical, and so is the buyer's move.
Why a plugin ends up with more than one home
This is not a scandal, it is the ordinary shape of the archviz software channel, and it is worth understanding because it predicts where the stale page will be.
A small studio builds a tool. A large vendor with an existing sales motion picks it up, because the small studio has a product and the large vendor has ten thousand firms already paying it for something else. The original page stays up. It ranks, it has backlinks, and taking it down would cost traffic nobody wants to lose. Then regional resellers, the companies that actually invoice studios in a given country and handle the VAT and the seat management, publish their own pages so they can be found locally.
Every one of those pages is first-party in the sense that matters to a search engine. Only one of them is downstream of the release notes. The others update when someone remembers.
A product page is not a fact about the product. It is a fact about who last had a reason to edit it.
The failure mode is the one we described in the piece on stale compatibility listings, and it fails in the same silent direction. A page that under-describes a tool never throws an error. It just quietly removes the product from your shortlist, and you never learn that it did.
The four questions, and which page answers them
You do not need to resolve the corporate history to buy well. You need four answers, and each one has a correct source.
1. Scope and host versions
Which applications, at which release years, on which operating system. Take this from the page that also hosts the release notes and the download, and check the date on the most recent release note. A product page with a 2026 feature list and a newest release note from 2024 is describing an ambition. If the release notes live on one domain and the marketing lives on another, the release notes win.
2. Price and what a credit is
Read the number on the day you buy, from the page that takes the payment. That sounds obvious until you notice that the page that takes your payment may be the reseller, not the maker, and the two can differ on currency, tier structure and what a bundle includes. We flagged this pattern when Veras went native inside Enscape, V-Ray and Corona with a unified credit pool. If you already pay for one of those, the standalone price on the standalone page is not your price, and no page will proactively tell you so.
3. Who answers the support ticket
This is the question the pages never address and the one that decides your Thursday afternoon. If you buy through a reseller, your first line of support is usually the reseller, and the escalation path to the people who wrote the code runs through them. That can be excellent, local language and a human who knows your account, or it can be a two-day relay. Ask before the purchase order goes out: when a render fails on deadline, which email address do I write to, and what is the response commitment.
4. Who holds the licence
Seats bought through a reseller often live in that reseller's portal. If you change resellers, or the reseller stops carrying the line, find out in advance whether your seats travel with you. This is a boring question that becomes an expensive one exactly once.
The forty-second version
When a tool has multiple vendor pages, do this before you read a single feature list. Find the page that publishes release notes and treat that as the version of record for what the software does. Find the page that processes payment and treat that as the version of record for what it costs. If those are two different companies, you have a channel, and you should ask the support and licence questions above. If they are the same company, you have a simpler purchase and one page to trust.
Then, and only then, read the marketing. Not because it lies, but because on a page nobody has edited since the last major release, it is a description of a product that used to exist.
Our take
We have written a lot about third-party bias this month, the vendor ranking itself first, the storefront reviewing what it stocks, the roundup with last year's date in its URL. The implicit advice underneath all of it was: go to the source. Today's sweep is a useful correction, because "the source" turns out to be a category with more than one member, and the members disagree about something as basic as whether the product runs anywhere other than Revit.
The fix is not more scepticism. It is one extra question, asked before the feature comparison rather than after the invoice. Not what does this tool do, but who has a reason to keep this page accurate, and when did they last act on it.
Three pages, three products, one piece of software. Buy from the one that publishes the release notes, pay the one that will answer the phone, and never let a marketing paragraph be the reason a tool leaves your shortlist.
Written from the 20 July 2026 intel sweep. Page descriptions are quoted from search results captured on 20 July 2026 and are reported to show their disagreement, not as vendor-confirmed specifications. We did not verify the commercial relationship between the publishers named, and the buying guidance here does not depend on it. Verify scope, price, host versions and support terms against the vendor page you actually transact with, on the day you transact.