Source available
OpenRoots and Elastic License 2.0
Incompatible, and unlike BUSL it does not resolve with time.
Inbound
noElastic-2.0 material entering an OpenRoots work
Elastic-2.0 forbids providing the work to third parties as a managed service, and forbids circumventing licence-key functionality. The first is a restriction an OpenRoots instrument does not impose and cannot pass on, since Hosting is a permission at 1.6.
Outbound
noOpenRoots material entering a Elastic-2.0 project
Elastic-2.0 cannot represent a revenue-triggered royalty.
Mechanism
Where the pairing holds and where it breaks.
A matrix cell tells you the answer. These are the clauses that produce it.
Derivative works
One combined, distributable artifact.Not permissible under current OpenRoots terms.
Composite distribution
Both shipped side by side, not merged.Aggregation only, and the managed-service restriction still governs the Elastic portion.
Patent position
Express grants and termination triggers.Elastic-2.0 includes a patent grant with a termination trigger.
The royalty
Where the Canopy obligation bites.The mechanisms differ in kind. Elastic forbids the hosting case outright; OpenRoots permits it and prices it above a threshold.
Current permanent terms
What holds for as long as the release exists.Elastic-2.0 has no change date, so it does not converge. The incompatibility persists indefinitely on the Elastic side.
Other pairs