Custom Autodesk Plugin Development: Packaged, Deployable, Sellable
Professional plugins for AutoCAD, Inventor, Revit and other Autodesk products, built as real software products: multi-version support, licensing, installers, automatic updates and Autodesk App Store publishing.
From internal tool to software product
Some tools stay inside one team. Others need to be deployed across many offices, supported for years across several Autodesk versions, or sold to customers. These plugins need more than working code: shared cores that serve multiple products, clean installers, licence management, update channels, documentation and a support process.
ENGIMANDI develops Autodesk plugins with a product mindset. We structure code so one core serves several Autodesk products and versions, package plugins as Autodesk bundles or MSI installers, add licensing and activation, set up automatic updates and telemetry where appropriate, and prepare everything for Autodesk App Store submission. Software vendors and equipment manufacturers use this service to give their customers Autodesk tools under their own brand.
Related reading: how to build custom CAD plugins.
What you get
- Multi-version plugin builds
- Shared core across products
- Autodesk bundle & MSI installers
- Licensing & activation
- Automatic updates
- Code signing
- User documentation
- App Store publishing
Plugin product engineering
Everything needed to ship and support plugins.
Architecture
Shared business logic with thin product-specific layers for AutoCAD, Inventor and Revit.
Version Support
Builds for several releases, including the .NET Framework to .NET 8 transition.
Packaging
Autodesk .bundle packages, MSI installers and silent deployment for IT teams.
Licensing
Trial, subscription and node-locked or floating licences with online activation.
Updates
Update checks and delivery so users always run the latest version.
App Store
Listing, packaging and submission for the Autodesk App Store.
Plugin stack
Development and delivery tools.
Typical projects
- Manufacturer plugin placing its products in Revit and AutoCAD
- Commercial Inventor tool sold on the App Store
- Company-wide plugin deployed silently to 500 seats
- Plugin rebuilt for AutoCAD and Revit 2025 on .NET 8
- Subscription licensing added to an existing tool
- Single codebase for AutoCAD, Civil 3D and Map 3D
How we build plugin products
Define
Users, products, versions and business model.
Architect
Shared core, packaging and licensing.
Build
Features, installers and CI builds.
Release
Beta testing and publishing.
Maintain
New Autodesk versions each year.
Plugin questions
How is this different from add-in development?
Add-in work focuses on in-product tools for your team. Plugin product work adds packaging, licensing, multi-version support and distribution for wider or commercial use.
Can we sell a plugin you build?
Yes. You own the code and can sell it directly or through the Autodesk App Store.
How do you handle new Autodesk releases?
We test on Autodesk beta and new releases and ship updated builds, usually as part of a maintenance plan.
Can one plugin work in AutoCAD and its verticals?
Yes. A single plugin can support AutoCAD, Civil 3D, Mechanical, Electrical and other toolsets.
Do you protect the code?
Yes. We use obfuscation, native code or licensing checks where appropriate.