Know you are ready before Apple and Google tell you.
Prioritized Launch Doctor findings, store metadata, screenshots, checklists and re-scan verification.
See a redacted sample report or sample verification receipt. Both are synthetic — not from a real scan.
The free Launch Score is a self-assessment questionnaire available today. The paid Launch Doctor Review is Founding Beta: an evidence-backed automated review of your repo or ZIP (ZIP upload today — automated self-serve GitHub upload is planned) that delivers evidence-backed findings via deterministic checks, AI explanation, an independent model challenge, and automated quality gates. Founding Beta is capped at a limited number of reviews per cohort. The fully connected version — reading live evidence from GitHub, Supabase, RevenueCat and the app stores — is on the roadmap. ShipForge is not currently able to offer a qualified human technical reviewer; findings are produced by the automated pipeline.
Scope of review
The Launch Doctor Review is a launch-readiness analysis based on the source code, configuration, and artifacts you submit. It is not a penetration test, a security audit, a legal review, or a guarantee of App Store or Google Play approval. A clean review means no blocking issue was found within the inspected scope — not that none exist anywhere. You remain responsible for your own store submission and compliance.
What Launch Doctor produces
- Launch Score
- Launch Doctor findings with evidence
- App Store + Play checklists
- Metadata & store copy
- Screenshot + promo asset generation
- Data Safety & privacy checklist
- Release checklist
- Re-scan and verification
Every finding shows evidence
No opinion-based reports. Each finding includes: what was detected, where it was found, why it matters, the severity, the business impact, and the recommended action. Every finding is labeled by evidence status — Deterministically verified, Could not verify, or AI recommendation. When a fix is applied and re-scanned, the finding is closed with a verification receipt.
Example finding — Auth
Supabase RLS disabled on the profiles table.
Evidence: supabase/migrations/2026-08-01-init.sql creates the table without ALTER TABLE … ENABLE ROW LEVEL SECURITY. Severity: high. Impact: any authenticated user can read any other user's profile. Fix: run the suggested migration; re-scan verifies the policy exists.