Guide · DevOps & Platform
Why Production Readiness Scores Fail SaaS
Teams search for a production readiness score. APRF refuses a single percentage—use gated Core Profile pass/fail blockers instead.
People search for a score—APRF answers with gated Core Profile blockers instead of a vanity percentage. Start with: Core Profile
A single percentage can't carry a fatal gap
Boards like "87% ready." Composites average past missing restores, client-side keys, or uncapped AI endpoints. APRF answers with gates: each control passes with evidence or blocks. One startup sold investors on a high checklist score while never testing restore and leaving a public AI route unlimited—the first abuse week burned runway a gated assessment would have flagged on Reliability and Cost.
Replace the scoreboard with blockers
Stop optimizing an average. Run Core Profile at `/aprf/assess/` for pass/fail. Prioritize: secrets in clients, untested restore, no spend ceilings, blind observability, missing tool/model controls if you call AI. Attach artifacts (restore report, budget screenshot, allowlist) so the gate is reusable for audits—not a slide.
What investors should hear instead
"Here are open blockers and the dates they close" beats a vanity number. APRF Change Management and Assessment exist for that conversation.
Next: Core Profile
Open the related pillar specification for mandatory checks, artifacts, and pass conditions. Self-attest is optional.
Related
Frequently asked questions
- What is a production readiness score?
- Usually a 0–100 composite from a checklist. APRF rejects that pattern—readiness is gated pass/fail with evidence, not an averaged percentage.
- How do I check production readiness without a score?
- Run the StackRail Core Profile assessment at /aprf/assess/. You get blockers and pass conditions—not a vanity percentage.
- What should I fix first for production readiness?
- Whatever the assessment marks as blockers—commonly untested restores, client-side secrets, missing rate/spend limits, and no production logs.