What we measure — and how it backs your pricing
fastpace sells outcomes, not just features. The six metrics below are computed by your own fastpace install, surfaced in your org dashboard, and either guarantee, refund, or scale your bill against thresholds we publish here. Every number is independently verifiable from your repo's signed artifacts — and every number is vendor-neutral: it holds across Claude Code, Codex, and Gemini CLI, because the underlying evidence chain does.
How outcome pricing works at fastpace
Traditional SaaS pricing is per-seat per-month, period. fastpace's pricing has three outcome dimensions layered on top:
- Score-pause guarantees (Team) — if a metric doesn't move by the contracted amount in the contracted window, your billing pauses until it does. The dashboard stays live, support stays on, and there's no churn dance.
- Tiered Enterprise pricing — your per-seat rate scales down as your framework readiness scales up. We benefit when you do.
- Refundable SLAs (Enterprise) — evidence-request SLO + hash-chain integrity uptime refund a defined % of your monthly spend if breached.
Audit-chain coverage gauge
Metric: % of AI-attributed commits with complete evidence chain
Threshold: ≥80% Team / ≥95% Enterprise
Computed from: F0.2 hash-chained audit log · F1.1 run manifests · F2.3 provenance trailers
Verify yourself: fastpace audit coverage
Pricing role: Team-tier score-pause guarantee #2. Billing pauses if coverage drops below 80% for 60 days in the customer's fleet. Enterprise renewal contingent on sustained ≥95%.
Why this metric: The single number that proves an AI dev workflow is fully audited. Joins the three core primitives — audit log, manifests, commit trailers — into one customer-readable percentage.
Framework compliance readiness
Metric: % of mapped framework controls with shipped + fresh evidence
Threshold: ≥60% Team / ≥85% Enterprise
Computed from: F1.15 framework mapping · audit-chain freshness · F2.4 AI-BOM
Verify yourself: fastpace compliance readiness --framework=nist-ai-rmf
Pricing role: Enterprise tiered pricing — $99/seat at 50% coverage scales down to $59/seat at 95% coverage. Customer pays less as fastpace delivers more value.
Why this metric: The metric an auditor actually checks. Framework-specific (NIST AI RMF, ISO/IEC 42001, EU AI Act, SOC 2) so a customer can request a per-framework readiness number.
AI-Native Maturity scorecard
Metric: 0–100 weighted aggregate across 9 competencies (F4.1–F4.9)
Threshold: L1 → L3 climb in 6 months (Team) · L3 → L5 in 12 months (Enterprise)
Computed from: F4.x maturity sub-scores · F4.12 aggregate
Verify yourself: fastpace maturity
Pricing role: Outcome-based Enterprise add-on. Customer commits to a maturity climb; fastpace shares the risk — if the climb doesn't happen by the deadline, the climb-bundle add-on fee is waived.
Why this metric: The "CTO board-slide" metric. Single number to justify continued investment to leadership over multiple budget cycles.
AI reliability score
Metric: 0–100 trailing 30-day correction-event rate (F2.1)
Threshold: Sustained ≥75 (Team) · Sustained ≥85 (Enterprise)
Computed from: F2.1 correction-detector hook · LCS-based attribution
Verify yourself: fastpace reliability
Pricing role: Customer-success milestone — a 25% reduction in correction rate within 90 days triggers a complimentary Enterprise migration window (no procurement cycle for the bump).
Why this metric: The number a senior reviewer trusts. Customers who pay attention to corrections-per-1000-lines see real velocity gains; we share in that win.
Evidence-request SLO (Enterprise)
Metric: Time from "auditor asked for X" to "fastpace produced signed receipt for X"
Threshold: 5 business days (Enterprise) — refundable SLA
Computed from: F2.5 evidence-request tracker
Verify yourself: fastpace evidence list
Pricing role: Enterprise SLA — each missed 5-business-day SLO refunds 10% of monthly Enterprise spend, capped at 100% in any one month.
Why this metric: Compliance teams plan their audit cycles around evidence-fetch SLOs. Predictability beats speed.
Hash-chain integrity uptime
Metric: % of fleet repos returning `fastpace verify` exit-0 in any given hour
Threshold: 99.5% (Enterprise SLA)
Computed from: F0.2 hash-chained audit log · F0.1 install identity
Verify yourself: fastpace verify
Pricing role: Enterprise infra SLA. Below 99.5% in a month → 10% refund per 0.1% below target. Cap: 100% of monthly spend.
Why this metric: The "is your governance system trustworthy right now" number. Independently re-verifiable by any auditor.
What a customer sees vs. what fastpace bills against
Critical: fastpace cannot reach into your repos to compute
these. They're measured by your fastpace install, signed
with your own per-machine identity key, and pushed to your
self-hosted org-dashboard. We see the rollups only when you
explicitly push them via fastpace replicate push.
That means: the numbers backing your bill are your numbers,
verifiable against your repo at any point.
For Enterprise customers under an SLA, the rollup-replication cadence is contractual (default 5 minutes, configurable). Missed replication windows are tracked as SLO misses in their own right.