Apache 2.0
Specification
Apache 2.0, plus a patent non-assertion commitment for implementations of Final versions of the specification.
Licensing
Open source under Apache 2.0. All of it.
The Governed Objects Specification, its conformance suite, and our Python and Go runtimes are licensed under the Apache License, Version 2.0. You can use, modify, embed and redistribute them, including in commercial and closed-source products, without paying us or asking permission.
What’s covered
Apache 2.0
Conformance suite
Apache 2.0. Anyone can run it, and no permission or paid tool is needed to establish conformance.
Apache 2.0
Python runtime
Apache 2.0, including its conformance adapter and tests.
Apache 2.0
Go runtime
Apache 2.0, including its conformance adapter and tests.
What Apache 2.0 means for you
- Use it commercially, for any size of organization.
- Modify it and build it into your own products, including closed-source ones.
- Redistribute it, keeping the license and NOTICE file and marking files you changed.
- Contributors grant a patent license for their contributions, as Section 3 of the license sets out.
- The license does not grant use of the Governed Objects name or logo. See “Using the name” below.
Our commitments
For our open-source runtimes, Brafford Labs, LLC commits that:
- When a runtime implements a capability defined by the Governed Objects Specification, including its optional profiles, that capability is available in the open-source edition.
- Security fixes for supported open-source releases are published in the open-source edition.
- Features in the open-source edition are not moved to a paid-only edition. Paid offerings add value beyond the specification, such as hosting, enterprise administration, integrations and support.
Using the name
- You may say, without asking, that your product “implements the Governed Objects Specification” and name the version.
- To say it “conforms to” a version, you need to:
- pass the open conformance suite for that version;
- meet the specification’s claim requirements;
- name both the specification and suite versions.
- Using the name or logo in a product, company or domain name, or suggesting endorsement, needs written permission.
Contributing
Contributions are welcome under Apache 2.0, with a Developer Certificate of Origin sign-off (git commit -s) on each commit. There is no contributor license agreement. Each repository’s CONTRIBUTING.md has the details.
Questions
Can I use this in a commercial, closed-source product?
Yes. Apache 2.0 allows commercial use and closed-source products, provided you keep the license and notices.
Do I have to publish my changes?
No. Apache 2.0 does not require it. We welcome contributions if you choose to share them.
Do larger companies have to pay?
No. The license does not depend on company size, and there is no fee.
Will you sell anything?
We may offer paid services and tools that go beyond the specification, such as hosting, enterprise administration, integrations and support. They do not take anything away from the open-source edition (see our commitments above). None are available today.
Can I build my own implementation?
Yes. That is a goal of the project. The specification is Apache 2.0, the conformance suite is free to run, and our patent non-assertion commitment covers implementations of Final versions. Current versions are drafts, which that commitment does not cover yet.
Does the license affect my data or my applications?
The license covers our software, not your data. Its conditions (keeping the license and notices) apply only when you redistribute the software itself.
Where do I report a security issue?
Privately to security@governedobjects.com, not in public issues.
This page is a summary, not legal advice. The license text in each repository controls.