AllAddin vs Autodesk Revit AI Assistant
Both are AI assistants for Autodesk Revit. They differ on version coverage, language paths, deployment model, and account requirements. This page lists the differences feature by feature.
Side by side
| AllAddin | Autodesk Revit AI Assistant | |
|---|---|---|
| Revit versions supported | 2025, 2026, 2027 | 2027 only |
| Language paths | IronPython 3.4 and C# (Roslyn) | Whitelisted pre-built functions |
| Arbitrary code execution | Yes (sandboxed; signed installer) | No (function whitelist) |
| Deployment | Native add-in (Windows MSI) | Ships with Revit 2027 |
| Autodesk account required | No | Yes (Forge / ADSK identity) |
| Maker | MeliUX Ltd (UK) | Autodesk Inc. |
| UK ICO registration | ZC137214 | Not applicable (US entity) |
| Marketplace of extensions | Yes (/market) | No |
| Self-host / on-prem option | Not in beta; on roadmap | Not available |
| Pricing during beta | Free | Bundled with Revit 2027 subscription |
When to pick which
Pick Autodesk's Revit AI Assistant when your organisation has already standardised on Revit 2027 across all projects, prefers the whitelisted-function safety model, and wants a tool that flows through Autodesk's existing account and billing stack.
Pick AllAddin when you have a mixed-version estate (Revit 2025/26/27), want arbitrary IronPython or C# execution rather than a whitelist, prefer a UK-based publisher with a documented trust posture, or want access to a marketplace of pre-built extensions on top of the core agent.
What both have in common
Both live inside Revit as a panel and respond to plain-language requests. Both can modify the active document. Both ship with privacy controls on what data leaves the machine. Neither replaces a senior BIM developer - both speed up the work that developer does.