Windows 11 + Node.js 20+
Version 1 baseline verifiedDoctor, safe initialization, profile execution, reporting and packaging pass on the declared launch environment.
← All products
Pre-launch app checks for vibe-built and AI-assisted apps
LaunchReady: The App Launch Check Kit
A pre-launch app checking toolkit for founders, vibe coders and AI-assisted developers. See the exact app version across desktop, tablet and mobile before customers see it.
Catch visible layout and interaction problems, fix them, check again and keep one clear go-live record.
Check your app before customers do.
£59 launch priceOne-time purchase
Watch the 40-second LaunchReady introduction ↓- Version 1.0
- Desktop + tablet + mobile
- 7 separate launch checks
Plain-English guide
The technical terms, translated immediately.
You do not need release-engineering vocabulary to use this kit. Here is what the original technical name means in normal language.
- Release proof
- A clear record of which app version you checked, what passed, what failed and whether it is ready to go live.
- Visual QA
- A screen-by-screen quality check on desktop, tablet and mobile, so you catch layout, interaction and presentation problems before customers do.
- Harness
- The repeatable local process that runs the checks and keeps the screenshots, results and final decision together.
Technical name: Release Proof and Visual-QA Harness Pack
Watch first, then inspect Version 1
Check your app before customers do.
1 of 6
Watch the 40-second LaunchReady introduction
A short, silent and captioned introduction to the buyer problem, the visual review journey and the human-owned release decision. The detailed 72-second technical navigation film remains inside the Version 1 download.
Start hereOne launch decision
Product manifest
- Version 1.0
- 52 manifested files
- 111-item architecture
- 11 chapters
- Individual licence
What is included
Everything you need to check the app before real users arrive.
- An executable local CLI, Evidence Workbench and 111-item system mapped across eleven chapters
- Desktop, tablet and mobile Chromium captures with HTTP, console, failed-request and overflow receipts
- Command receipts, clean ZIP extraction, SHA-256 inventory, required-file checks and privacy-pattern scans
- Human-owned HOLD/release gates, JSON + Markdown + printable HTML reports, templates and raw evidence
- A broken/corrected synthetic fixture, manual, quick start, Individual licence, 72-second film and visual map
Current build
Version 1.0.0- Version 1.0
- Desktop + tablet + mobile
- 7 separate launch checks
How the system works
One candidate. One evidence chain. One accountable decision.
The application and toolchain can change. Candidate identity, proof states, exceptions and human authority remain visible.
- 01
Vibe-build
Move fast with your coding agent, then freeze the exact candidate you actually intend to review.
- 02
Collect proof
Capture responsive Chromium, console, command, package, hash and privacy receipts against that candidate.
- 03
Review + improve
Label exceptions in the Evidence Workbench, correct the application and re-test as a new candidate lineage.
- 04
Human gate
Finish with one bounded evidence packet and a named HOLD, conditional or release decision.
Version 1 proof boundary
The supported local evidence core is executable; release authority stays human.
Version 1 is built, fixture-tested, deterministically packaged and live on Payhip and Ko-fi. Deployment, certification and a paid-buyer delivery test remain separate proof states.
Playwright Chromium Web profile
Broken/corrected fixtures verifiedThe acceptance pair detects intentional console and mobile-overflow defects and preserves the corrected candidate separately.
ZIP + Document profile starters
Baseline includedZIP extraction, file requirements, hashes and privacy patterns are automated; document inventory is automated while native render judgement stays manual.
Payhip customer route
Public route verifiedThe £59 product page exposes Buy Now and declares the 14 MB customer ZIP. Paid-buyer delivery has not yet been independently exercised.
Ko-fi customer route
Public route verifiedThe £59 product page exposes Add to cart, two preview images and the 14.8 MB customer ZIP. Paid-buyer delivery has not yet been independently exercised.
Build evidence
A real local harness, fixture acceptance loop and deterministic customer archive.
Version 1 passes its foundation and product tests, detects the intentional broken fixture, preserves corrected evidence as a separate lineage, refuses overwrite during initialization, generates the Evidence Workbench and rebuilds the same customer ZIP hash from the same source.
See how the launch check works →- 52
- manifested customer files
- 3
- responsive browser viewports
- 2
- separate fixture candidate lineages
- 2
- public buying routes
Before you buy
What the Version 1 harness covers - and what remains human-owned.
Who is this for?
Founders, vibe coders, agentic developers and engineers who have an app that works and want a clearer way to decide whether it is ready for real users.
Do I need to understand visual QA or release engineering?
No. LaunchReady guides the process in plain language. Visual QA simply means checking what the real app looks like and how it behaves across screen sizes; release proof is the saved record of what you checked and decided.
Does it automatically deploy an application?
No. The baseline is local-first and evidence-focused. Production credentials, irreversible actions and the final release decision remain outside agent authority.
Are these 111 loose files?
No. The pack organizes 111 system deliverables across eleven chapters rather than padding the ZIP. Version 1 ships 52 manifested files that implement the supported core and clearly label optional or later adapters.
Need this operating knowledge applied to your own system?
See ChaseInTech services →