ZeroFare
Console Get started

Roadmap

Phased, labeled, honest.

We ship in phases and mark every item with its true state. Nothing here is implied to work before it does — badges are shipped, in progress, and planned.

PHASE 1

The foundation — live today

shipped
  • Local edge shipped — loopback inference gateway with vaulted provider keys, admission control, and decision receipts; OpenAI / Anthropic / Responses compatible surfaces behind zerofare.compat/v1.
  • Hosted gateway shipped — bearer-key auth, fair admission, tenant isolation, receipts; served over TLS in early access.
  • Management API shipped — 25+ endpoints under the frozen zerofare.management/v1 contract: credentials, sessions, audit, policies, quotas, subscriptions, catalog, jobs, cache, emergency controls.
  • Customer console shipped — same-origin console with real credential auth: keys, sessions, audit, policies, quotas, subscriptions.
  • Production deployment shipped — hardened containers (read-only, cap-drop, non-root), TLS reverse proxy, digest-only secret storage, restart-survivable seed hydration.
  • Test estate shipped — 519+ deterministic tests incl. tenant-isolation, contract, load, and property suites.
PHASE 2

Commercial readiness — underway

in progress
  • Durable domain stores in progress — move console-backed domain data from in-memory/seed-only to durable storage.
  • Metered usage & billing planned — pass-through spend metering at provider rates with per-tenant invoices; subscriptions transition via the management API.
  • Provider origin dispatch (hosted) in progress — full commercial provider egress on the hosted path, with per-decision receipts end to end.
  • Teams & SSO planned — organization identity for the Team plan tier.
  • Public marketing domain in progress — this site; moving from the sslip.io preview host to a owned domain with the same TLS automation.
PHASE 3

The paid hosted product

planned
  • Learned routing & scoring plugins planned — policy-driven model selection; off by default until certified.
  • Caches planned — semantic serving, organization and tool caches behind hosted-cache entitlements.
  • Zero-egress proxy & regions planned — the paid hosted product described in our infrastructure policy: multi-region, no-KMS-free posture, regional redundancy.
  • Certified routes planned — routes earn "certified" status only with commercial, privacy, ZDR, authorization, and no-overage evidence in place.
Why phases? ZeroFare's contracts are frozen, which means we'd rather under-promise per phase than break a customer. Each phase lands behind the same versioned surfaces you build on today — features light up without contract churn.