We relicensed HyCanvas from ELv2 to AGPL. Here’s why

Description and use

HyCanvas moved from ELv2 to AGPL‑3.0‑only to meet OSI open‑source standards, enable hosting and internal use, and support a dual‑licensing business model.

Problem

HyCanvas was under Elastic License 2.0, which limited hosting and made it not OSI‑approved, conflicting with the product’s open‑source positioning.

Outcome

HyCanvas now meets OSI open‑source definition, allows hosting and internal use, and supports a dual‑licensing business model while maintaining clear trademark guidance.

Workflow

• 1. Release v0.3.17 with AGPL license.
• 2. Ship license files (LICENSE, NOTICE, COMMERCIAL.md, TRADEMARKS.md) in all artifacts.
• 3. Audit dependencies’ licenses (e.g., @imgly/background‑removal is AGPL‑3.0).
• 4. Publish trademark policy to distinguish official builds.
• 5. Communicate changes in release notes and FAQ.

Evidence

Everything up to v0.3.16 was under the Elastic License 2.0 (ELv2). From v0.3.17 onwards the code is under the GNU Affero General Public License v3, AGPL-3.0-only.

Source

You may not provide the software to others as a hosted or managed service that gives them a substantial set of its features.

Source

The AGPL closes that gap with one rule: if you distribute HyCanvas, or let people use a modified version over a network, you offer them the complete source of your version under the same license.

Source

Ship the license files in every artifact.

Source

Audit your dependencies' licenses first.

Source