Specmate licensing

Core

Specmate's application core and original project source are licensed under AGPL-3.0-only, except where an applicable file or package declares another license. See LICENSE for the full terms. This license applies to Specmate; upstream source repositories retain their own terms.

Separate package and material licenses

• Reusable capability packages retain the licenses declared in their add-on.json manifests and any accompanying notices. Their source templates, assets and compiled add-on packages are not silently relicensed by the root license. Existing MIT declarations remain intact.
• Imported WireHub helpers retain their pinned AGPL text, attribution and provenance under packages/wiring/vendor/wirehub/. No CouchCAD pipeline code is imported.
• Third-party dependencies retain their own licenses, copyright notices and applicable patent/attribution requirements. The root license does not replace their terms.
• CAD libraries, models and other assets retain their own terms. The bounded recipe uses standard KiCad libraries under CC-BY-SA-4.0 with the KiCad libraries exception; see workers/cad/THIRD-PARTY-NOTICES.md and each build's provenance/notices.
• Private catalogs, credentials, deployment configuration and independently authored engineering data are not made public by this software license. Generated outputs need their own input/asset rights review; they do not inherit AGPL merely because Specmate or a GPL command-line tool generated them. Outputs embedding copied program source retain that source license separately from the engineering data; distributing recipe/source files also requires their applicable license notices.

Modules and integrations

A separately licensed reusable package can be included in Specmate when its terms permit the combination. Its own license remains applicable, alongside the obligations for the combined application. Modular packaging alone does not exempt a combined AGPL program from those obligations.

Independent programs communicating through versioned APIs or signed webhooks are the preferred seam for proprietary integrations. Check actual independence and code reuse; a communication boundary is not an automatic exemption. Proprietary in-process extensions need an appropriate exception or separate permission from all relevant rights holders. No blanket plugin exception is granted by this document.

The copyright holder can offer alternative terms for code they control. That option does not waive third-party requirements or revoke previously granted licenses.

Distribution and deployment

Applying a source license is not authorization to publish or deploy. Before distributing an image or running a public service, account for its exact contents: retain dependency and asset notices, meet applicable source-availability requirements (including AGPL's network provision), and verify binary/runtime redistribution terms. The application image includes the core license, licensing policy and WireHub notices. Its /source/ page offers the exact clean build context and installed dependency source/license files; OCI metadata identifies the source revision. This source offer does not waive individual third-party, base-image or native-tool distribution terms.

See licensing review for review scope and references. Engineering exports and deployment configuration retain their own visibility and asset-rights requirements.