In the architecture, engineering, and construction (AEC) sector, software licenses are quietly evolving into tools for corporate control. What once were agreements about installation limits and usage now assert authority over your designs, your data, and even your ability to innovate. Author Martyn Day discusses that shift in this AEC Magazine article.
Historically, a software license meant “you don’t own the software itself, but the right to use it under certain conditions.” EULAs and digital rights management protected the vendor’s IP, not your project files. Things are different today. As software has moved into subscriptions and clouds, the clauses have grown. License contracts now define how you can use your own outputs. They restrict your right to train AI models from your data. They regulate API access, control third-party developers, and set the terms of participation in their ecosystem.
Autodesk is cited as a recent and stark example. Its Acceptable Use Policy now prohibits using any “Output” from Autodesk software for training machine learning or AI, unless that happens inside Autodesk’s own ecosystem. On paper, they still “own your content,” but in practice, that ownership is hollow if you can’t use the content for your own innovation.
These restrictions pose real risks. Consultancies may be held liable if a license term conflicts with client contracts. Smaller software developers, the ones who build add-on tools or independent utilities, face tighter rules, revenue-sharing, metered APIs, and the threat of exclusion. Meanwhile, customers may lose access to the very data that holds strategic value: their project history.
Day argues that this concentration of power is not inevitable. Collective resistance, through procurement practices, regulatory pressure (such as Europe’s Digital Markets Act) or a sector “Bill of Rights” for software users, could push back. The central question emerges: In the age of AI and data, do you really control your work, or does your vendor control you?