Pricing
The runtime is free.
Pleach ships fair source under FSL-1.1-Apache-2.0 — source-available, production-ready today, converting automatically to Apache-2.0 two years after each release ships. Not OSI-approved open source during that window.
Two surfaces. One runtime.
The runtime is free and trust-protected. Hosted products on top of it are enterprise products. Per-package terms are on /license.
The runtime@pleach/* on npm | Hosted productsbuilt on the runtime | |
|---|---|---|
| License | FSL-1.1-Apache, converts to Apache-2.0 two years after each release | SaaS contract; annual term |
| Phone-home | None. Runtime doesn't call us. | Required — you sign into the dashboard |
| License check | None on the runtime | Per-seat / per-tenant entitlement |
| Account to run | Not required | Required for hosted surfaces |
| Retro-paywall | Impossible — FSL conversion clock runs per release | — |
| Self-host | Yes, indefinitely. Air-gap, on-prem, sovereign-cloud in scope. | The operational wrapper is the product |
| SSO / SAML / SCIM | — | Per-seat on hosted dashboards |
| SLA / retention | Your storage; your policy | Annual contract; custom windows |
| SOC 2 | Your stack | Bundled wrapper around the audit ledger |
| Pricing | $0 | Contact sales; custom by tier |
Audit rows ship where you point them — Postgres, Supabase, an OTel collector, or a custom destination. What we sell on top:
- Hosted Gateway — multi-tenant routing, per-tenant cost caps, provider failover, per-tenant subscription; no markup on inference.
- Hosted Observe at enterprise scope— SSO/SAML/SCIM, retention SLAs, SOC 2, the export bridge into the dashboard you already use, per-tenant evidence-pack export.
- Marketplace bundles — AWS, Azure, GCP.
None of these gate a runtime feature. Self-serve tiers for teams without enterprise procurement are in development; pricing for any paid surface lands on a page like this one before it ships.
What FSL-1.1-Apache-2.0 lets you do
FSL grants almost every right Apache 2.0 does, with one restriction during the first two years after each release:
- Allowed: Use it in production — internal apps, customer-facing products, agents, services.
- Allowed: Modify the source. Ship a fork. Vendor it into your monorepo.
- Allowed: Build a commercial product that uses Pleach as a runtime dependency.
- Allowed: Self-host it to serve your own customers. That's a product, not a competing offering.
- Not allowed: Sell a hosted offering of Pleach itself that substitutes for the original. This is the only restriction, and it expires per release on the conversion date.
On the conversion date, that release becomes plain Apache-2.0 — no restrictions, no action required. The terms travel with the release.
What costs money in production
The runtime is free. The third-party costs of running an agent product are real — and none of them flow back to Pleach.
Sibling packages
The @pleach/* scope sits in three buckets. Every shipping release uses the same FSL-1.1-Apache-2.0 terms as @pleach/core; each npm page is the source of truth for current state.
@pleach/core, @pleach/tools, @pleach/base-tools, @pleach/compliance. Stable contract, semver applies, in production today.@pleach/react and @pleach/langchain. Real implementation; pin an exact version, because ^0.0.xwon't catch the next preview.0.0.1 · UNLICENSED@pleach/eval, @pleach/gateway, @pleach/replay, @pleach/mcp, @pleach/coding-agent. Names held, no shipping code — implement the relevant HarnessPlugin plug-points yourself for now.For procurement & legal
Short answer for the questionnaire: fair source, FSL-1.1-Apache-2.0, converting to Apache-2.0 two years after each release. Each FSL package publishes its conversion date in package.json under pleach.fslConversionDate, so you can audit the schedule directly. The full text lives in the repo:
Have a commercial question we didn't cover? Email getpleach@protonmail.com.