Curated directory of Plugins & Extensions software for AEC teams. 56 published tools.
Plugins and extensions stretch your authoring platform without waiting for the next major release. They can add calculations, exporters, content libraries, or quality checks that sit right inside familiar interfaces. The tradeoff is support: each add in is another vendor relationship, another upgrade path, and another place where conflicts appear after core product updates. Evaluate stability, release cadence aligned with your host version, and whether the vendor signs reasonable security terms. Prefer tools with clear uninstall steps and documented APIs so you are not locked into opaque binaries. Weigh how each add in affects model open times and support tickets filed by authors in the first month after install. A proof of concept on a large healthcare or campus template will reveal performance issues that never appear on vendor samples. This category helps you discover specialized capabilities that sit beside core modeling. Pair listings with internal standards that name approved extensions per project type. Keep a lightweight catalog that records why an extension was approved, who owns updates, and which host versions it was last tested against.
Create an allow list per discipline, version pin critical extensions, and test upgrades on a sandbox model quarterly. Track who installed what and require BIM manager approval for anything that writes project data. Document rollback steps when a host upgrade breaks compatibility.
Per seat, per project, and floating network licenses still appear. Some vendors bundle maintenance as a percent of list. Ask whether cloud features require separate identity and whether offline grace periods exist for site laptops.
Heavy automation can bloat families, add invisible parameters, or create circular dependencies. Run health checks before major milestones. Teach authors to avoid stacking overlapping tools that touch the same elements without coordination.
Treat them like software supply chain risk. Request hashes, signing practices, and subprocessors. Block unsigned installers on corporate devices. For macros, prefer signed packages and central distribution.
When you need full control of roadmap, deep customization, or the plugin cost exceeds internal build cost over three years. Also when IP must stay inside your network boundary.
You can scan many specialized products quickly, then jump to vendor sites for trials. Listings aggregate categories so teams do not rely on forum threads alone.
