Start by proving reuse, not by guessing at savings.

One honest self-service plan. One measured design pilot.

Free Observe shows whether a workload is reusable. Indie adds governed repair and policy. Teams evaluating production use start with an isolated 14-day pilot.

Self-service

For independent developers and small production workloads.

Self-service is deliberately narrow. Isolated environments are scoped after a design pilot.

Verify

Free Observe

Measure reuse eligibility, actual cache use, and drift before you enforce anything.

$0/monthManaged service · no formal SLA
Verify one workflow free
  • 1 project and 10,000 requests per month
  • 7-day reuse, token, latency, and drift telemetry
  • Observe mode only; CachePilot does not mutate requests
  • OpenAI Responses and Anthropic Messages routes
Governed self-service

Govern

Indie

Repair reuse-breaking drift and enforce policy with the Indie plan.

$49/monthMonthly, cancel anytime · no formal SLA
Start Indie

Create an account first, then confirm billing in secure Stripe checkout.

  • 3 projects and 50,000 governed requests per month
  • 30-day telemetry and 10 golden-run baselines
  • Stable-prefix repair, cache breakpoint injection, and policy enforcement
  • Output budgets, drift alerts, and auditable X-CP-* receipts

Design pilot · $5,000 fixed · 14 days

One workflow, an isolated pilot environment, baseline versus governed traffic, and an evidence package covering reuse eligibility, actual cache use, drift, latency, receipts, policy outcomes, and cost.

The adoption path

Instrument, verify, govern, then decide.

1

Route one workflow

Swap the base URL and add the CachePilot project key.

2

Run the same request twice

The first call warms the provider path; the second tests actual reuse.

3

Inspect the evidence

Compare the stable prefix, expected reuse, cached tokens, latency, drift, and receipts.

4

Enable governance

Only paid or pilot workloads move from observation into policy and safe request repair.

Questions worth answering before purchase

Clear boundaries, before checkout.

What does CachePilot guarantee?

CachePilot can guarantee cache-eligible request construction, stable-prefix policy, drift detection, and auditable request receipts. It cannot force an opaque upstream provider to return a cache hit; the dashboard verifies actual cached tokens after the response.

What is the Indie service boundary?

Indie is a managed service for independent developers and small workloads. It has no formal uptime SLA or custom data-residency commitment. Design pilots, demos, and larger accounts use isolated environments with separately scoped data boundaries.

Is cost reduction the main metric?

No. The leading indicators are reuse eligibility, stable prefixes, expected versus actual reuse, drift, latency, and receipt completeness. Cost is an important downstream outcome, but not every workload is cost-led.

Does this work with Claude or Fable?

Yes. Anthropic Messages traffic and Claude/Fable adapter traffic can be governed when routed through CachePilot's supported Anthropic or OpenAI-compatible surfaces. Provider-specific behavior remains visible in telemetry.

Design pilot inquiry

Bring one repeated, expensive, or operationally sensitive workflow.

We will decide together whether it is a credible reuse-governance pilot before provisioning a dedicated environment.