How Pleach is licensed.

@pleach/core, @pleach/tools, @pleach/base-tools, and @pleach/compliance ship under FSL-1.1-Apache-2.0 — the Functional Source License, version 1.1, with an Apache-2.0 future grant.

In practice: use, modify, self-host, embed, and ship products on top of them. The one restriction: don't build a hosted product that competes with the package itself. Two years after each release, that release converts to a plain Apache-2.0 grant with no restrictions. The clock runs per release; pleach.fslConversionDate in each package's manifest publishes the exact date.

The @pleach/core LICENSE is canonical for the template: LICENSE in pleachhq/core. That file is the contract; this page is a summary.

@pleach/react and @pleach/langchain ship as 0.0.x previews under the same FSL-1.1-Apache-2.0 grant — real license, moving surface. Pin an exact version; ^0.0.xwon't catch the next preview, and 0.0.x → 1.0.0isn't caretable either.

The remaining @pleach/* names — @pleach/eval, @pleach/gateway, @pleach/replay, @pleach/mcp, @pleach/coding-agent, and @pleach/trust-pack — exist as 0.0.1 placeholders, marked UNLICENSED with no functional code.

Each adopts a license at its first real release — expect the same FSL-1.1-Apache-2.0 grant, but the LICENSE in the shipped tarball governs.

getpleach.com — marketing pages and rendered docs — is covered by the site terms, not the package licenses. Site content is © Pleach.

Code snippets in the docs inherit the license of the package they document — treat a @pleach/core snippet as FSL-1.1-Apache-2.0 code.

• — @pleach/core LICENSE
• — @pleach organization on npm (per-package LICENSE shown on each package page)
• — FSL specification (fsl.software)