10specialist bridges
Multiplenative technologies
9AI clients
1hub · policy
1licence across the stack
The hosts
Ten AEC applications. One AI connection.
Find your tool below — the assistant drives it through its own native API, not a lossy export. Nine more come with the same hub, licence and policy.
Revit
Design, engineer & document
Archicad
Design & build the BIM
Vectorworks
Design across disciplines
Rhino
Shape & compute form
AutoCAD
Draft & detail
Tekla Structures
Engineer the structure
Blender
Visualize & present
SketchUp
Think in 3D, fast
QGIS
Ground it in the real world
openBIM
Coordinate & hand over
More on the way — the bridge architecture is uniform, so new hosts join the same AI surface with your prompts, skills and guardrails intact.
The difference
Not a plugin.
An AI layer across your stack.
Most AEC automation is locked to one tool and one fixed command list. Archi Automate composes each operation on demand, in the host's own native technology — screened, previewed in dry-run where supported, and executed inside the host's own transaction model.
One assistant, ten applications: read from any, write to any, governed by one policy.
Composed on demand · screened · dry-run · audited
Governed composition engine
plain language → native operation
ten host applications · each in its own native technology
Interoperability
The highest-value work happens between the applications.
Ten hosts around one AI core. The assistant queries every bridge, and creates, edits and coordinates according to each host's capabilities and your active policy. Cross-tool work is explicit and AI-orchestrated — no background sync.
Revit
Archicad
Vectorworks
Rhino
AutoCAD
Tekla Structures
Blender
SketchUp
QGIS
openBIM
Archi Automate core
MCP · skills · guardrails · audit
Handoffs become explicit, reviewable instructions — no custom integration for every pair of tools.
Concept geometry → native production
Read the approved facade geometry in Rhino, recreate the selected elements natively in Revit, then carry the structural requirements into Tekla for detailing. The handoff becomes a guided workflow — not a flattened export and a manual rebuild.Model QA → coordination → correction
Federate the discipline IFC models, run an IDS validation, open a BCF issue with a snapshot for each failure — then return a precise correction list to each authoring team. Automated checking becomes team action — not another PDF report.The openBIM backbone
Open or federate. Validate. Coordinate. Hand over.
A vendor-neutral QA and coordination layer that works on IFC directly — the whole loop from check to team action, without opening a CAD application.
Author & federate IFC
Open, author and federate IFC models from any authoring tool — no CAD application required.
Validate with IDS
Check models against IDS specifications — and author the specifications themselves from plain language.
Clash & quantities
Detect clashes across disciplines and take off quantities directly from the federated model.
Carbon estimates
Produce embodied-carbon estimates from model quantities — honest numbers for early decisions.
BCF issues, with pictures
Turn validation failures into a BCF issue set with referenced elements and snapshots — in one call.
Handover exports
Export COBie, glTF and USDZ for handover, viewing and AR — from the same conversation.
What you can do
Query, convert, validate, contextualize, render.
The same AI surface that answers a one-line question moves data between tools and runs a project-wide workflow — each operation inside the host's own transaction model.
Query any model in plain language
Ask a live model in any host — categories, parameters, geometry, relationships — without schedules or scripts.
Which blocks on this AutoCAD sheet sit on the wrong layer?
Convert between tools
Translate geometry and data across hosts with intent preserved — not a lossy dump. The AI maps source to target through each native API.
Rebuild this SketchUp massing as a Revit mass with matching levels.
Validate across disciplines
Run compliance, naming, and integrity checks — and cross-check one model against another for consistency.
Run an IDS check on the IFC and open a BCF issue for each failure.
Pull real-world context
Bring site, terrain, and neighbour data from GIS into the model so early decisions sit in the real world.
Pull the terrain and adjacent buildings around this site from QGIS.
Automate multi-step workflows
Describe logic spanning categories, conditions, and several hosts. Archi Automate composes the operations and runs them in order.
Query the Tekla assembly, then tag matching elements in Revit.
Render and present
Drive the visualization host — scene, materials, sun, cameras — and produce presentation imagery through the same governed layer.
Set up a sun-study scene in Blender for the June design review.
Why Archi Automate
The idea, in one short film.
Two minutes on why one AI layer across your whole AEC stack changes the work — and what it looks like in practice.
Multi-modal inputs
Anything the AI client can understand can inform the workflow.
Voice, images, drawings, spreadsheets, regulation PDFs, external APIs — whatever your AI client can read, Archi Automate can ground in the live model of any connected host.
Voice
Speak the operation.
Voice input through compatible AI clients turns spoken instructions into native operations — hands free, mid-meeting, in any connected host.
“Show every column in Rhino that clashes with a Revit beam.”
Images
Drop in a reference.
Hand the AI a site photo, a sketch, or a precedent image. It reads the visual, grounds it in the model, and composes the next step.
“Match the window rhythm in this facade photo on the south elevation.”
2D drawings
Read consultants' PDFs.
Feed in 2D PDFs, DWG snapshots, or annotated markups. The AI extracts intent and maps it onto the live model in any host.
“Tag every door on this consultant's fire-strategy markup.”
External data
Bridge any source.
Excel, GIS, manufacturer catalogues, energy-model results, building-code databases, your own APIs — wired in through the AI client.
“Pull the latest equipment-load table from the consultant SharePoint.”
How it works
Four hops from prompt to model — whichever host you point at.
The whole chain is inspectable. You can swap the AI client, pin the policy, and review the complete action history of any session.
01 · step
AI client
Your existing chat with Claude, GPT, or any MCP-compatible client. No new UI to learn.
Claude · GPT · MCP→02 · step
Model Context Protocol
Open MCP transport carries the request to the Archi Automate core. Standard, inspectable, swappable.
open protocol→03 · step
Archi Automate core
Selects the right bridge, composes the native API operation, and checks it against your active policy and skills.
policy · skills · dry-run→04 · step
Host execution
Executes host-natively — whichever of the ten you point at — with rollback or undo where supported.
ten AEC hosts→Get started
Up and running in a minute.
Straight from the installer to your first prompt. Breadth grew, setup didn't — one install detects your hosts, one click connects your AI, and you're asking questions.
01Install onceOne installer detects the hosts on your machine.
02Connect your AI clientOne-click Claude, GPT, Gemini — or any MCP client.
03Run your first promptAsk a question in plain language — read-only by default.
Safety & governance
Read-only everywhere. Preview where supported. Every change audited.
Connecting an AI to a model does not mean giving it permission. Archi Automate separates what the assistant can understand from what it may change — one policy, enforced the same way on all ten hosts.
Analysis without risk.
Inspect any element, parameter, or relationship in any connected host. The bridge refuses any write operation, regardless of what the AI tries.
Query categories, parameters, geometry
No transactions opened
Safe for federated and review models
Preview before commit.
Where the host and operation support it, the AI runs the operation as a non-persistent preview — so the workflow can be checked before anything is kept.
Non-persistent preview run
Apply deliberately after review
Supported per host and operation
Full automation, audited.
Write operations execute host-natively, with rollback or undo where supported. Every step is logged, on every bridge.
Host-native execution
Rollback or undo where supported
Timeout and API constraints enforced
Screening & action history.
Every composed operation is screened against a configurable deny-list and your policy before execution. Every session writes a complete, reviewable action history.
Pattern-based deny-list
Element caps · delete blocking
Reviewable action history
Inside the app
A small console for a very large surface.
Archi Automate runs as a quiet desktop app beside your authoring tools. One install detects the hosts on the machine and bridges them all — a handful of screens cover the entire operator workflow across all ten.
BridgesTen host cards — Revit, Rhino, Archicad, openBIM, Blender, AutoCAD, Tekla, QGIS, SketchUp, Vectorworks — with live sessions below.
From pilot to practice
Start with one painful workflow. Expand from evidence.
Begin in read-only mode on a live project and find where better context saves time. Automate one bounded process — documentation, QA, parameter updates, coordination — with controlled changes only where the team is ready.
Then standardize: capture what worked as reusable skills, mappings and company rules. They apply across every bridge, and as the underlying AI models improve, the workflows you've built improve with them — no migration.
Book an AI workflow sessionOffice naming conventions
Ship your studio's number/letter conventions as a skill the AI applies in every host automatically.
studiopolicy
Template & layout libraries
Wrap your view templates, sheet layouts, and Archicad master layouts so the AI uses them, not generic defaults.
graphicstemplates
Building-typology rules
School, hospital, office, residential — encode the rules of thumb that govern each typology.
typologyrules
Regulation packs
TEK17, IBC, NBC, fire codes — distil regulations into checks the AI can run against any model.
compliancevalidate
Conversion mappings
Define how your studio maps geometry and data between tools — Rhino layers to Revit categories, and back.
convertinterop
Custom domain skills
Anything you can describe in a doc, you can package as a skill. The AI picks the right one for the task and host.
modularopen
Compatibility
Works with your assistant — and your whole stack.
Any MCP-capable AI client can drive Archi Automate, and every host bridge speaks its application's native API. Bring the assistant you already use.
ClaudeMCP
CodexMCP
CursorMCP
VS CodeMCP
WindsurfMCP
AntigravityMCP
Gemini CLIMCP
ClineMCPJetBrainsMCP
Any MCP clientopen
Host applications
- Revit
Design, engineer & document - Archicad
Design & build the BIM - Vectorworks
Design across disciplines - Rhino
Shape & compute form - AutoCAD
Draft & detail - Tekla Structures
Engineer the structure - Blender
Visualize & present - SketchUp
Think in 3D, fast - QGIS
Ground it in the real world - openBIM
Coordinate & hand over
Platform & protocol
- Model Context Protocol
open spec - Windows 10 / 11
x64 - One install detects & bridges all hosts
auto - Multiple host sessions at once
supported - One licence across every host
included - Floating & desktop licenses
both - Voice input via compatible clients
indirect
Versus
Where it fits next to what you already have.
Dynamo, Grasshopper, and macros stay excellent for known workflows inside one tool. Archi Automate covers the rest — the one-off tasks, the validations, and the moves between tools that don't have a script yet.
| Capability | Platform scripts | Single-tool AI plugin | Manual IFC exchange | Archi Automate |
|---|---|---|---|---|
| Plain-language input | ○ no | ◔ partial | ○ no | ● yes |
| Works across ten AEC hosts | ○ no | ○ no | ◔ partial | ● yes |
| Read from one tool, write to another | ○ no | ○ no | ◔ partial | ● yes |
| AI composes in the host's native technology | ○ no | ○ no | ○ no | ● yes |
| No manual export / import round-trip | ● yes | ● yes | ○ no | ● yes |
| openBIM QA: IDS check → BCF issues | ○ no | ○ no | ◔ partial | ● yes |
| AI-driven rendering host | ○ no | ○ no | ○ no | ● yes |
| Preview before commit (where supported) | ○ no | ◔ partial | ○ no | ● yes |
| Audit trail of every session | ○ no | ○ no | ○ no | ● yes |
| One policy across every host | ○ no | ○ no | ○ no | ● yes |
Learn & support
Docs, community, and fleet deployment.
Get the most out of your Archi Automate subscription — step-by-step guides, an active forum, and silent-install tooling for IT.
Learn
Choose topics, find answers, get step-by-step instructions, and develop your skills with the full user guide.
User GuideDiscuss
The Archi Automate Forum is the place to ask questions, find answers, learn from experts, and share your knowledge.
Archi Automate ForumDeploy
Roll out Archi installers across multiple machines with the Silent Installer Guide, built for fleet deployment.
Silent Installer Guide
Included in Archi Collection
Get this plugin as part of the full Revit workflow bundle.
Archi Collection gives you Archi Automate plus the rest of archi's Revit workflow toolkit, expanding workflow coverage while offering better value than licensing plugins one by one.
Buy
Floating Licenses
Archi Automate
One assistant for
every model
in your project.
14-day full trial — all ten bridges, governance and cross-tool workflows included. Start read-only, prove the value, and add automation at the pace your company can govern.
