Ferryte
Source-available · BSL 1.1

Free where developers debug.
Paid where teams run in prod.

Same model as Sentry and MariaDB. The debugging engine is source-available (BSL 1.1) — read every line, self-host it, run it in production free. The hosted plane — persistent timelines, prod alerts, shared history — is the paid product.

The only thing with a price today · $500 · 48 hours

Not ready to self-serve? Start with the Agent Memory Audit — we instrument your agent with you, run the full battery in your infra, and hand you the evidence. Money back if we find nothing actionable.

Book it →

Core

Available today

BSL 1.1 · free forever (self-hosted)

The library, the CLI, and the local memory inspector. Read it, self-host it, debug your agent today — free forever for self-hosted use.

  • ferryte.instrument() one-line auto-patch
  • ferryte why — attribute any answer to the memory behind it
  • Write-time lineage graph + blast radius (SQLite)
  • Mem0 · vector · Zep · Letta · Cloudflare adapters (pgvector / Chroma / Qdrant)
  • Local memory inspector dashboard
  • Fix & verify: prove a deleted memory is really gone
  • CI gate for memory regressions

Cloud

Pre-release

Free for design partners · paid after · pricing TBD

Not built yet — five design partners are shaping it. Free during the design-partner window, then a paid product. When it ships, the hosted memory-observability plane for agents in production.

What it will do once we ship it

  • Everything in Core
  • Hosted memory timelines (persistent, cross-session)
  • Prod incident alerts when memory misbehaves
  • Regression detection across deploys
  • Slack, PagerDuty, Linear integrations
  • Per-user & per-tenant memory dashboards
  • Team collaboration + shared history

Enterprise

Roadmap

TBD · talk to us

Direction, not product yet. Self-hosted hardening + signed compliance — built once Cloud is mature.

What we plan to build, once Cloud is in hands

  • Everything in Cloud
  • Self-hosted / VPC with SSO + RBAC
  • Audit logs + SOC2-ready posture
  • Signed deletion attestations (GDPR / CCPA)
  • Premium adapters: deep AgentCore, GovCloud, custom
  • Runtime memory governance (v2)
  • Support SLA + dedicated channel

See LICENSING.md and COMMERCIAL.md in the repo for the exact licensing boundary, contributor policy, and commercial-tier scope.

Side by side

Where the boundary actually sits.

●  in Core = ships today.   ●  in Cloud = building it with the first five design partners.   ●  in Enterprise = roadmap, once Cloud is mature.

FeatureCoreCloudEnterprise
Local CLI + memory inspector●●●
ferryte why — memory attribution●●●
Fix & verify a deletion●●●
Mem0 · vector · Zep · Letta · Cloudflare adapters●●●
Hosted memory timelines (cross-session)—●●
Prod incident alerts + regression detection—●●
Slack / PagerDuty / Linear—●●
SSO + RBAC——●
Audit logs · SOC2 posture——●
Signed GDPR / CCPA deletion attestations——●
Premium adapters (deep AgentCore / GovCloud / custom)——●
Runtime memory governance (v2)——●
Design partners · five seats

Paired with the founder.
Six months of Cloud free. Shape the roadmap.

Ferryte Cloud isn’t built yet — five design partners will shape it before we ship. Today: the founding engineer paired with your team for the first Core integration. When Cloud ships: six months free for design partners.

Join the waitlist
Or book a call →
FAQ

The questions everyone asks.

Why source-available (BSL) and not MIT or fully closed?

Nobody instruments their agent's memory with un-auditable tooling, so the engine stays readable and self-hostable — read the source on a Friday afternoon, ship it Monday. BSL adds exactly one restriction over MIT: you can't resell Ferryte itself as a competing hosted service. That closes the hyperscaler-clone risk that hit Elastic, Redis, and HashiCorp, without locking anything away — every version converts to Apache 2.0 after four years.

Can I self-host the dashboard without paying?

Yes. The local Next.js dashboard is source-available and ships in the repo. Run it against the JSON reports the CLI produces, in production, for free. Enterprise adds SSO, audit logs, multi-environment management, and signed compliance receipts on top of the same surface.

Will Core ever become paid, or get features clawed back into Cloud?

No. Core is free forever for self-hosted use — we never paywall something Core already does. Cloud and Enterprise are net-new surface (hosted memory timelines, prod alerts, signed attestations) sold to teams running agents in production. The design-partner cohort gets Cloud free during the build window; after that Cloud is a paid product, while Core stays free.

What license do contributions fall under?

Contributors sign a CLA that grants us a license to incorporate their changes into both the source-available core (BSL 1.1, converting to Apache 2.0) and the commercial tiers. The core repository stays source-available in perpetuity, and every version becomes Apache 2.0 four years after release. See LICENSING.md and CONTRIBUTING.md.

When does Cloud GA?

After the design-partner cohort. We are deliberately not pushing the button until we have five teams running stateful agents in production and the timeline + alerting surface have survived a quarter of real memory bugs.