Skip to content

Simple pricing

Three ways to deal with what the free check finds.

What has been recorded

Release Gate

49one-time

$49 credited toward a Launch Review within 30 days.

A launch checklist your coding agent runs before every release.

On your statement: Gate installed, with the version.

  • A production-review skill file your agent loads on demand.
  • Release, regression, and failure-path checklists.
  • Rollback requirements, definition of done, and evidence rules.
  • An AGENTS.md block plus Claude Code and Codex instructions.
  • Works in Lovable, Claude Code, Cursor, and Codex.
  • Every update included.
  • Bonus: the Stack Launch Checklist for your declared stack, as markdown.
  • In your library the same minute.

Refund window: Refundable within 7 days of purchase.

Scope, timeline and delivery

Best for

Builders who make their own changes and want their coding agent to follow the same launch process on every release.

Not included

  • Nobody looks at your app. You install the package and run it yourself.
  • No changes to your code and no verdicts on your statement.

What is in the file

  • SKILL.md, the production-review skill your agent loads on demand, with the seven-step gate and a SHIP, SHIP WITH NOTES, or HOLD verdict.
  • The AGENTS.md block, the standing rule that makes your agent run the gate.
  • Blocks for Claude Code and Codex, plus the Cursor rule.
  • Five checklists: release, regression, failure path, rollback, and definition of done, with the evidence rules.
  • The Lovable install, which works without a repository.
  • The release note template.

A sample: the release checklist

  1. Name every change since the last release that touches sign-in, payments, data access, or deployment.
  2. For each one, state how it was tested and paste the evidence, not a tick.
  3. Run the failure path: what a customer sees when the call fails, times out, or returns nothing.
  4. Confirm the rollback: the exact step that puts the last good version back, and who can run it.
  5. Confirm no key, token, or connection string reaches the browser bundle.
  6. Give the verdict: SHIP, SHIP WITH NOTES, or HOLD, with the reason in one line.

What happens after you buy

  1. You check out and the package lands in your library the same minute.
  2. You drop the AGENTS.md block into your repo.
  3. Your agent loads the skill file on demand from then on.
  4. Every later version shows up in the same place.

Delivery

In your library the same minute.

Launch Review

199one-time

First reply within 1 business day. Delivered within 3.

Speed

Alex checks what a URL check can't see and tells you what to fix.

On your statement: Each item Verified or Needs fix, dated, with Alex's note.

If it turns up nothing you did not already know, you do not pay.

  • Founding price for the first 20, then $299.
  • Every Not verified item from your check gets a verdict, Verified or Needs fix, with the fix prompt for your builder.
  • Alex reads your public repo if you share one, and your evidence either way.
  • Risks ranked by what they would cost you.
  • A written review plus about 15 minutes of Loom from Alex.
  • Bonus: Release Gate included, $49 value.
  • Bonus: a re-check 30 days later that shows which items are cleared.
  • $199 credited toward a Hardening Sprint within 30 days.

Refund window: Refundable in full any time before work starts.

Scope, timeline and delivery

Best for

Founders putting real users on an app that signs people in, stores their data, or takes payments, in the next 30 days.

Not included

  • No changes to your code. You or your builder apply the fix prompts. Having the fixes made with you is the Hardening Sprint.
  • No second reading after you fix things. That is Re-verification, $99, or part of a Hardening Sprint. The 30 day re-check reruns the free check.
  • Nothing is attacked and nothing is written to your data. Signed in checks use test accounts you create.

What happens after you buy

  1. You check out and fill in a short intake, about four minutes.
  2. Alex replies within 1 business day with anything he needs.
  3. The written review plus the Loom arrive within 3 business days.
  4. Your statement is updated item by item, dated, with Alex's note.
  5. A re-check 30 days later shows you the cleared list.

Delivery

First reply within 1 business day. Delivered within 3 business days.

Hardening Sprint

1,750founding price

Scope confirmed in writing before any fix begins.

Alex fixes your top problems with you, then checks them again.

On your statement: Needs fix becomes Fixed and re-verified, dated.

Every item in the confirmed scope gets fixed and re-verified, or that item is refunded.

  • Founding price rises to $2,500 after the first cohort.
  • Starts with a Launch Review, included, if you have not had one.
  • Scope confirmed in writing before any fix: 3 to 5 highest-priority items, acceptance criteria, exclusions.
  • The fixes, made with you, in your repo.
  • Repo guardrails installed: Release Gate plus the AGENTS.md rules that keep the fixes in place.
  • Before and after review, release checkpoint, handoff notes a future developer can read.
  • Daily updates for 7 business days.
  • Bonus: re-verification 30 days after handoff, so your statement shows Fixed and re-verified with a date.
  • Access needed: read and write to the repo and a staging environment, nothing else.

Refund window: Refundable in full any time before scope confirmation.

Scope, timeline and delivery

Best for

Teams with priority fixes who want them made together, inside seven business days, before or just after launch.

Not included

  • Anything outside the written scope. New items mean a new agreement.
  • New features or redesigns.
  • Production passwords or secret keys. Access is the repo and a staging environment.

What happens after you buy

  1. You check out and share repo and staging access.
  2. A written scope reaches you within 2 business days.
  3. Fixes land across 7 business days with a daily update.
  4. Handoff notes, a release checkpoint, and an updated statement.
  5. Re-verification 30 days after handoff.

Delivery

Daily updates across 7 business days once scope is confirmed.

Release Assurance

$3,500 per month

Every client app you ship carries a current Launch Risk Statement, and a person watches every release.

On your statement: A current statement per client app.

First review within 5 business days of onboarding, or the first month is refunded.

How you pay

  • Four release-risk reviews each month, each one adding verdicts to the statement.
  • One architecture clinic.
  • Priority triage on anything that breaks.
  • Repo guardrails installed and kept current across the apps.
  • Bounded remediation hours included.
  • A statement per client app, up to five, the client-ready deliverable agencies hand over.
  • For agencies and product teams that ship every week, not for solo founders.
  • Cancel monthly.

Refund window: Cancel monthly. Access runs to the end of the paid period.

Scope, timeline and delivery

Best for

Agencies and product teams shipping every week across several apps.

Not included

  • Not a monitoring tool or an uptime pager.
  • Not open ended development. Remediation hours are bounded.

What happens after you buy

  1. An onboarding call within 3 business days covers your apps and your release rhythm.
  2. The first review lands within 5 business days.
  3. Four release-risk reviews land each month, plus one architecture clinic.
  4. Every client app carries a statement that stays current.
  5. Cancel monthly at the end of the paid period.

Delivery

First review within 5 business days of onboarding.

Talk to Alex first

Release Assurance Studio

Priced on the call

For agencies running Release Assurance across a client book.

  • White-label statements carrying your agency name beside ShipReady's.
  • Unlimited client apps.
  • One invoice.

Which one fits

Three answers, one suggestion, and the reason for it. Nothing is saved.

Who will make the changes?

What do you need most?

When do real users arrive?

3 of 3 answers to go.

Building for clients? How agencies use ShipReady.

ShipReady is not a penetration test or a security certification. No automated check can prove an application is secure.

Last updated October 29, 2026

View as markdown

Questions