The current main branch and current public release packages are licensed only under GNU GPL v3.0 or later (GPL-3.0-or-later). Anyone may run, inspect, modify, and redistribute the current community edition subject to the GPL. Distribution of object code must satisfy the GPL corresponding-source obligations.
The presence of historical repository records does not give recipients a choice to apply an earlier license to current revisions or current release binaries.
A separately negotiated commercial license is available for proprietary integration, OEM/white-label distribution, private product branches, and contractual support. See COMMERCIAL-LICENSE.md.
This commercial path is separate from the public GPL community license. It does not make the current public source dual-licensed under GPL and Apache-2.0.
Revision 0df1007d9538b978edba67218136bc5c4f8019ad and earlier public revisions were released under Apache-2.0 and remain available on branch archive/apache-2.0-final. Existing rights previously granted for those historical revisions are not withdrawn.
The historical Apache license text is retained on that archive branch, not in the current main branch or current release package. Apache-2.0 does not apply to changes made after the historical boundary.
ArIED links directly to ARIEC61850. A distributed combined build must use mutually compatible licenses or a separately authorized commercial arrangement for every component.
New contributions require DCO sign-off and agreement to CONTRIBUTOR-LICENSE-AGREEMENT.md. Branding is governed separately by TRADEMARK.md.
Repository history cannot resolve employment, invention assignment, customer confidentiality, or off-repository ownership. Obtain professional review before signing a high-value commercial or OEM agreement.