Annealage
FILE 03: licensing

Licensed per product. Stated up front.

Annealage Canvas and Annealage Mesh are licensed under the PolyForm Noncommercial License 1.0.0: the source is public, and you can read, run, modify and contribute to it for any non-commercial purpose at no cost. Annealage Pod is open source under AGPL-3.0-only, commercial use included, with its hardware designs under CERN-OHL-S-2.0. Each product has a commercial licence for what its public licence doesn't cover.

Source-available is not the same as OSI open source, and we don't call Canvas or Mesh open source. The PolyForm Noncommercial License restricts use by purpose, so it doesn't meet the Open Source Definition. Pod's AGPL does, which is why Pod is the one we call open source.

What is licensed how.

REUSE.toml

One licence per repository, with carve-outs mapped per file. In each repository a machine-readable REUSE.toml (REUSE 3.0) is the authority for every path, including files that can't carry an inline SPDX header.

CANVAS PolyForm-Noncommercial-1.0.0

**/*: the repository default.

Free for any non-commercial purpose; commercial use needs a commercial licence. The agent skill bundle and its manifest (skill/**, manifest.py) are MIT for any use, so the glue an agent loads to drive the tool stays permissive.

POD AGPL-3.0-only

**/*: the repository default.

Use it for anything, commercial included. Distribute it, or host a modified version for others, and you share your source under the same terms. The firmware carries an extra linking permission for the cyw43-driver and BTstack in the built image. Hardware designs are CERN-OHL-S-2.0.

MESH PolyForm-Noncommercial-1.0.0

**/*: the repository default.

Free for any non-commercial purpose; commercial use needs a commercial licence, which includes the bundled agent package. The skill under skill/annealage-mesh/ is MIT, and the vendored three.js stays under its authors' MIT licence.

Third-party code keeps its own upstream licence: git submodules, vendored libraries, and the agent backends Mesh drives, which are governed by their providers' terms.

Canvas and Mesh: the boundary

By purpose, not by who you are.

The line is the purpose of your use, not whether you are a company. Being a for-profit business doesn't by itself need a licence; using the software for a commercial purpose does. Pre-clearance is free. If you are unsure which side you are on, ask before you deploy.

FREE · NON-COMMERCIAL
  • Personal, hobby, and amateur projects.
  • Teaching, coursework, and student projects.
  • Academic and publicly-funded research.
  • Charities, government, and public-safety bodies.
  • Evaluation with no anticipated commercial use.
PAID · COMMERCIAL
  • Designing GUIs or parts for a commercial product.
  • Paid services using the tools on behalf of clients.
  • Distributing it inside a commercial product.
  • Hosting it as a service for a commercial purpose.
  • Any other use directed toward commercial advantage.
Pod: the AGPL

Commercial use is already allowed.

Running pods in your own lab to develop and test your own products needs nothing else: no fee, nothing to publish. The AGPL only asks for your source when you distribute Pod or host a modified version for other people. A commercial licence is for when that doesn't work for you: shipping Pod inside a closed product, or hosting it without sharing your changes.

  • USE Any use, commercial included, in your own lab.
  • SHARE Distribute it, or host a modified version for others: publish your source under AGPL-3.0.
  • CLOSED A test fixture, production programmer or instrument with Pod inside: commercial licence.
  • HARDWARE CERN-OHL-S-2.0: build, modify and sell hardware from the designs, publishing your modified sources.

A commercial licence.

COMMERCIAL.md

Commercial licensing is by email. For Canvas and Mesh, standard licences cover internal use by your organisation to develop, test, and design your products. For Pod, they cover shipping, embedding or hosting it without releasing your source. Redistribution and hosting terms are negotiated case by case. Tell us your organisation, what you plan to build or ship, and roughly how many engineers. You will get a proposal within a few business days.

Pre-clearance is free. Ask before you deploy.

  • SCOPE A commercial licence covers our own code only; third-party components keep their licences and notices.
  • CURE PolyForm: first written notice of a violation gives 32 days to come into full compliance before the licence terminates.
  • MARK "Annealage" and the product names are trademarks. No licence grants trademark rights; a modified fork must be renamed.
Contributions

DCO and an inbound grant, not a CLA.

Contributing does not require signing a separate agreement. You sign off each commit under the Developer Certificate of Origin 1.1 (git commit -s), and by submitting you grant the right to relicense the contribution, commercial terms included. That grant is what lets commercial licences include contributed code without re-clearing every contributor. You keep copyright in your work, and it stays available under the product's public licence.

  • DCO Sign off each commit with git commit -s; the format is checked in CI.
  • GRANT Inbound licence to relicense, including commercially. You retain copyright.
  • OUT Your work ships under the licence of the path it touches: the repository default, or its carve-out.
The source

Read it on GitHub.

Every licence file, LICENSE, COMMERCIAL.md, CONTRIBUTING.md, and REUSE.toml lives in the product repositories under the Annealage organisation. The text on this page is a summary; those files are the terms.