OpenSite/Licensing
Understand the distinction between the application, your account and third-party components.
Application licence
OpenSite is described by its repository as a commercial structural engineering platform. The name “OpenSite” does not mean open source. No final product licence text, EULA, pricing table, trial duration or public purchase/activation procedure is provided by the reviewed repository. This help page does not create those terms.
What to do before production use
Obtain the applicable licence and distribution terms from the product owner. Keep the terms supplied with your actual build. Do not infer an application licence from access to a repository, a documentation page, an SDK example or a third-party open-source dependency.
Accounts in this development build
The production account portal and credential store are unavailable seams. A successful login to this documentation wiki is not an OpenSite application licence or an active desktop account. See OpenSite/Reference/Features/Accounts and licensing for the development contract. No working online activation, subscription purchase or offline lease is demonstrated here.
Local work and disabled commands
Ordinary local document-workspace and user-material operations are separate from engineering/catalog-provider authorization. A disabled operation can reflect build features, current selection, a busy Python lane, or unavailable authorization. Read its message and use OpenSite/Support. Do not treat --development-host as a licensing remedy.
Third-party software and documentation
Dependencies retain their own notices and terms; see OpenSite/Third-party notices. Documentation and imported template histories are separate from the application’s licence. A wiki footer licence does not relicense the OpenSite program.
