Frequently asked questions

Yes. AllAddin generates per-room data sheets that export as Excel (xlsx, multi-sheet workbook with one tab per floor), PDF (one A3 landscape page per room), or Word (docx, editable for redline review). Send the file to your client, QS, or specifier. They edit in their preferred tool. When they send the edited xlsx back, the AllAddin Import command reads it and writes the changes back onto the Room shared parameters automatically. The whole round-trip works without your reviewer ever opening Revit.

Yes. The Dashboards Room Data Sheet template exports a multi-sheet workbook (Cover sheet, master schedule, per-floor tabs) that mirrors the typical AEC Room Data Sheet format. Edited values come back into the model via the Room Data Sheet ribbon's Import xlsx button in one undoable Transaction. The exporter is openpyxl-based and runs server-side; the dashboard triggers a browser download.

AllAddin supports Autodesk Revit 2025, 2026, and 2027. The same installer covers all three versions; AllAddin auto-detects your installed Revit and registers itself accordingly.

No. Revit 2024 ships with .NET Framework 4.8, and AllAddin requires .NET 8 or later. Autodesk first shipped a .NET 8 Revit with version 2025, which is the earliest version AllAddin can run on.

Autodesk's Revit AI Assistant ships only with Revit 2027. AllAddin runs on Revit 2025, 2026, and 2027, is independent of Autodesk's account / Forge plumbing, and exposes both an IronPython 3.4 and a C# / Roslyn execution path. AllAddin is made by MeliUX Ltd in the UK.

Dynamo is a visual programming tool; pyRevit is a Python scripting host. Both require you to write or wire up code yourself. AllAddin generates the code on demand from plain language, runs it inside a Revit transaction, and reports what changed. You don't need to know the Revit API to use it.

Copilot and Cursor are general-purpose code assistants that live in your editor. AllAddin is purpose-built for the Revit API: it knows the differences between Revit versions, lives inside Revit as a chat panel, and runs the code it writes against your active document - not in a separate IDE.

Both. AllAddin can generate IronPython 3.4 (the language Revit's embedded scripting engine speaks) or C# (compiled with Roslyn at runtime). You pick the language per request, or let the agent choose based on the task.

Your .rvt model never leaves your machine. AllAddin sends only the chat text plus a small extracted context (active view, selection summary, version) to the backend, which proxies to Anthropic's Claude API. Generated code returns to your Revit session and runs locally. See https://alladdin.dev/privacy.

A package manager for AllAddin. Curated tools (sheet builders, material lookups, parametric helpers, schedulers) install with one click and become first-class commands inside the chat panel. Browse the catalog at https://alladdin.dev/market.

Yes. Each extension is an .allax bundle - a signed zip with manifest, code, and assets. You can build one privately for your team, or publish it to the public marketplace through the submission queue at https://alladdin.dev/market/publish.

AllAddin is in beta during 2026. Beta access is free for evaluation; production pricing will be announced before general availability.

AllAddin is in closed beta. Request access via the signup form on https://alladdin.dev/ - once approved, you'll receive an installer link by email. Run the MSI on a Windows machine that has Revit 2025, 2026, or 2027 installed; it registers the add-in for every installed Revit version automatically.

Yes. AllAddin runs in the active Revit document the same way any add-in does. It respects Revit's worksharing transactions and produces sync-safe edits. BIM 360 / Autodesk Construction Cloud-hosted models work as long as Revit can open them.

Wrong results are detected automatically (Revit transaction errors, exceptions, output mismatch). AllAddin retries up to three times with different approaches, then tags the failure to a corpus so the same mistake is avoided next time you ask a similar question.

Yes. The chat panel shows the generated code in a fenced block before execution, and you can review or edit it. AllAddin can also be configured to require explicit confirmation before any code that modifies the model runs.

AllAddin is a product of MeliUX Ltd, a UK-registered company. MeliUX Ltd is run by Rene Pellicer Garcia, an Autodesk Expert Elite member with 25+ years in the AEC industry. Made with real passion, in Charlton, south east London. See https://alladdin.dev/terms for the full legal entity details.

No. AllAddin is a software product - an AI cooperator agent for Autodesk Revit - made by MeliUX Ltd in the UK. The name is a pun on "all" + "add-in" (Revit plugins are called add-ins). AllAddin is not affiliated with, sponsored by, or endorsed by The Walt Disney Company or any Aladdin film franchise. The canonical website is https://alladdin.dev.

Because the name is "all" + "add-in" - the two L's are load-bearing. AllAddin (two L's) is a Revit AI product made by MeliUX Ltd. Aladdin (one L) is the Disney character. Search results may confuse the two; the canonical site for the AllAddin product is https://alladdin.dev.

"All" + "add-in." Revit plugins are called add-ins; AllAddin behaves like the union of every add-in a Revit user might want, driven by an AI agent that lives inside Revit. Users of AllAddin are called "allies" - the pun continues. AllAddin is made by MeliUX Ltd in Charlton, south east London.