Same model as Sentry, PostHog, Supabase. The detection engine is MIT because nobody adopts un-auditable security tooling. The trust plane — hosted, hardened, attested — is where the revenue lives.
MIT · free
The library, the CLI, and the four scenarios. Ship it in your CI today.
Design-partner waitlist
The hosted oracle. Continuous verification, regression alerts, full history.
Annual · contact us
Self-hosted, hardened, and where compliance receipts and runtime enforcement live.
See LICENSING.md and COMMERCIAL.md in the repo for the exact open-core boundary, contributor policy, and commercial-tier scope.
| Feature | Core | Cloud | Enterprise |
|---|---|---|---|
| Local CLI + dashboard | ● | ● | ● |
| Four canary scenarios | ● | ● | ● |
| Mem0 + pgvector adapters | ● | ● | ● |
| Hosted continuous verification | — | ● | ● |
| Historical reports + regression alerts | — | ● | ● |
| Slack / PagerDuty / Linear | — | ● | ● |
| SSO + RBAC | — | — | ● |
| Audit logs · SOC2 posture | — | — | ● |
| Signed GDPR / CCPA attestations | — | — | ● |
| Premium adapters (AgentCore / Zep / GovCloud) | — | — | ● |
| Runtime retrieval enforcement (v2) | — | — | ● |
Ferryte Cloud goes private beta with five companies running multi-tenant memory in production. We pair an engineer with your team and wire the first integration in a day. We say no to most. The few we say yes to get the first six months free and a direct line to engineering.
Nobody adopts un-auditable security tooling. Putting the detection engine under MIT means appsec teams can read the source on a Friday afternoon and ship a CI gate on Monday. The trust plane — hosted, hardened, attested — is where the revenue lives.
Yes. The local Next.js dashboard is MIT-licensed and ships in the repo. Run it against the JSON reports the CLI produces. Enterprise adds SSO, audit logs, multi-environment management, and signed compliance receipts on top of the same surface.
Yes — contributors sign a CLA that grants us a license to relicense their changes, but the core repository remains MIT in perpetuity. See LICENSING.md and CONTRIBUTING.md.
After the design-partner cohort. We are deliberately not pushing the button until we have five teams running multi-tenant memory in production and the alerting + history surface have survived a quarter of regressions.
