Pleach is independently built.

The model

Two surfaces, one runtime. The runtime is free and trust-protected — no phone-home, no license check, no account to run it, no retroactive paywall. The FSL conversion clock runs per release, so the openness is contractual, not a promise we could revoke later.

Revenue sits one layer up: hosted products that wrap the substrate with operations a team can't cheaply self-host — multi-tenant routing, retention SLAs, SOC 2, SSO/SAML/SCIM, evidence-pack export. None of them gate a runtime feature. The full breakdown is on /pricing.

Why fair source

Fair source is a deliberate choice, not a hedge. Source-available means a team can adopt, audit, and self-host the substrate with no vendor lock — including air-gapped and sovereign-cloud deployments. Delayed Apache-2.0 conversion means that openness can't be walked back.

That combination is what makes the substrate safe to standardize on. Standardization is the precondition for the hosted layer to have a market: every team that builds on the runtime writes audit rows in a shape we defined.

The boundary we hold

The substrate is the public good; the hosted layer is the business. If those two ever pull against each other, the substrate wins. We don't ship a SKU whose only purpose is one customer, and we don't paywall a runtime capability to drive hosted upgrades. A boundary the reader can see is worth more than a roadmap we could quietly change.