Chaos published a useful comparison of six AI rendering tools for architects. Its Veras section also contains a basic chronology problem. The page says “Veras 4.0 runs on Google Gemini’s Nano Banana 2.” A few lines later it describes one interface for “Veras 6 and under” and another for “Veras 7.” All three references appear in the same current product review.
That does not prove which label is wrong. It proves the page cannot establish the version by itself. A buyer who copies its feature description into a studio recommendation may be documenting a product that does not exist in the form described.
The contradiction is small. The decision is not.
The Chaos comparison page was listed in today's ArchiGen AI sweep and identifies itself as updated on 18 June 2026. It compares Veras, Midjourney, Rendair AI, ArchiVinci, Spacely AI, and Archsynth. It is unusually clear about a valuable distinction: some tools sit inside design software, while others require a web upload or a separate image workflow.
The trouble begins when that clear category work becomes a specific version claim. Version numbers tell a team which interface to expect, which tutorial to follow, and whether an older office install supports the feature in a buying guide. “The control is a slider” and “the control is written in the prompt” are not equivalent instructions.
Chaos's current official Veras product page advertises sketch-to-image, model-to-image, image-to-video, and image-to-3D workflows. The same page refers to Veras 4.6 in its video section. It does not support the comparison page's jump to versions 6 and 7. Chaos's May 2026 support notice describes Starter, Pro, and Ultra offerings and their included credits, but it does not announce Veras 6 or 7 either.
A vendor domain is a source. It is not a guarantee that every page on that domain agrees with every other page.
Separate four clocks
Fast-moving AI products carry several dates at once. A blog has a publication date and an updated date. A desktop plug-in has a version and build. A hosted generation model can change without the plug-in receiving a new major number. A pricing plan can change while an older tutorial remains indexed.
A buying guide becomes unreliable when it compresses those clocks into “current.” Record each one separately:
| Clock | Evidence to record | Why it matters |
|---|---|---|
| Article | Published and updated dates | Shows when the claim was last edited |
| Application | Version and build from the installed product | Connects instructions to the interface in use |
| Model | Named engine shown at generation time | Hosted output can change between application releases |
| Offer | Plan, credit allowance, billing term, access date | Prevents old pricing from becoming a budget assumption |
This record takes minutes. It also makes a later retest possible. Without it, a team can only say that a feature worked on some unnamed configuration when the review was written.
Check the action, not the adjective
The comparison calls Veras BIM-native and says its geometry control distinguishes it from general image generators. That is a testable workflow claim. The official product page confirms integrations with design and rendering applications, plus image and model inputs. A separate Chaos V-Ray announcement is more precise: Veras receives a viewport or V-Ray Frame Buffer image, then generates or modifies a visual without changing the underlying 3D scene.
That last detail changes how “reads the model” should be understood. An embedded command can remove export friction while the AI operation still works at the image level. Native placement, direct access to a current viewport, and semantic access to BIM objects are three different capabilities. A comparison table should not merge them into one integration checkmark.
Turn every buying-guide adjective into an action. For “geometry-aware,” ask whether the tool receives pixels, a depth signal, object data, or editable geometry. For “native,” ask what launches inside the host and what is sent to a remote service. For “fast,” start the timer before export or setup and stop it after an acceptable file returns. For “editable,” name the file or object that can actually be changed.
A five-minute verification pass
Start with the comparison's product name and claim. Open the linked official product page, then the vendor's release notes or support center. Search both for the version number and feature name. If the version appears only in the comparison, mark it unconfirmed. If two official pages conflict, record both access dates and ask support before specifying the product in a project plan.
Next, verify the feature at the level your studio needs. A page that says “Revit integration” does not answer whether it is available on your license, works with your Revit release, preserves a saved camera, or sends only a viewport image. A pricing page does not answer whether generation credits are shared across products. Keep a short list of unanswered procurement questions.
Give the evidence a simple status: confirmed, contradicted, or unverified. Confirmed means a current product or support page directly answers the question. Contradicted means two current sources give incompatible answers. Unverified means the claim appears in a roundup but not in the product record you can find. Do not convert “unverified” into “false.” It is a prompt for a trial or a support ticket, not a verdict.
Capture the page title, access date, and exact section, not just a browser bookmark. Vendor pages are edited in place, so the sentence that supported a decision may disappear. A dated note lets the office explain what it knew when it approved the purchase. For a major rollout, save the relevant release note or support reply with the software evaluation.
Finally, run a trial on a disposable project. The purpose is not to crown an image winner. Confirm the installed version, input path, available control, export type, credit charge, and whether a second user can repeat the steps. Save one screenshot of the About panel and one of the generation settings with the test record.
What remains useful in the guide
A contradictory version reference does not erase the entire comparison. Its strongest conclusion is category-level: integration and geometric control often matter more to an architect than raw image polish. Its cloud-processing note is also operationally relevant. Those ideas can be verified independently and used to build a shortlist.
The product ranking deserves more caution because the publisher is also the vendor behind the top recommendation. That conflict is visible, not disqualifying. Treat the guide as Chaos's account of the market, then check competing products on their own documentation and test them on the same office task.
Do not repair the contradiction by guessing that “7” is a typo, a planned release, or an internal naming scheme. We found no cited release note on the reviewed pages that resolves it. The honest status is unresolved.
Our take: freshness needs receipts
AI rendering guides age at different speeds inside a single paragraph. The category advice may hold for a year. A price can change next month. A model name can change next week. A control can move overnight in a hosted interface.
Architects already know how to manage revision risk. We put dates on drawings, clouds around changes, and issue records behind decisions. A software recommendation deserves the same discipline.
Write down the version. If the page cannot, stop at the shortlist.
Editorial basis: the 15 September 2026 ArchiGen AI intel sweep and current Chaos product, blog, and support pages linked above. The version conflict was checked across those sources. This is a source audit, not a hands-on product test, and it makes no claim about an unannounced release. ArchiGen AI carries no sponsored placements.