Checkout
Stripe test-mode session
Preparing launch surface
Complete product inventory
See the live PreFlight product in one place: Audit, Deploy, Health, Revenue, Growth, Trust, and the operational layer that connects them.
7
Product systems
35
Verified capabilities
20
Integrations
Priority system / Revenue integrity
Run a full Stripe test payment. Check that the webhook arrived. Check that Supabase gave the customer access. Save the result. Revenue Guard repeats the test after every deploy.
Stripe test-mode session
Signed event delivery
Supabase side effect
Reconciled trace
Audit
Turn the public app and connected stack into one ordered, fixable release verdict.
A prioritized view of this app’s current status and next action.
Scan the public app and rank verified findings by impact.
Check the connected services and delivery paths your app depends on.
Define an assertion for the behavior only your product knows.
Deploy
Bring pull-request evidence, real browser journeys, and production comparison into the release decision.
Read a plain-English release verdict before promotion.
Put PreFlight evidence directly on a push and pull request.
Run real browser paths for signup, checkout, onboarding, and critical flows.
Compare a preview journey with verified production evidence.
Health
Operate uptime, incidents, alerts, dependencies, and API defense as one recovery loop.
Connect user impact, deployments, endpoints, threats, and next action.
Continuously sample the public paths that customers rely on.
Own, remediate, and verify open incidents in one place.
Route evidence to Slack, email, Discord, and webhooks.
Inspect active attacks, blocking, and API hardening signals.
Revenue
Follow money from Stripe Checkout through the signed webhook and into your entitlement state.
See the payment path, risk, and next action in one operating view.
Track live MRR, churn, and revenue forecast signals.
Reconcile completed Stripe sessions with the fulfillment side effect they should create.
Run a safe Stripe test-mode purchase without a customer charge.
Schedule payment evidence around deploys and on a regular cadence.
Keep the proof chain from checkout to provider event, webhook, and reconciliation.
Growth
Research the opportunities, publish genuinely useful articles, connect the pages, and measure the result.
See the search opportunity and your editorial work at a glance.
Use keywords, competitors, gaps, clusters, articles, links, backlink profiles, and rankings together.
Inspect provider-backed referring domains, anchors, and a bounded external-link sample.
Research demand and identify terms that match the product you actually sell.
Move approved opportunities into accurate, reviewable SEO articles.
Measure organic positions and use the result to steer the next piece of work.
Trust
Publish the right evidence, share reports, and make reliability visible outside the dashboard.
Operations
The rest of the live workspace for connections, automation, evidence history, dependency risk, and grounded assistance.
Configure the providers and credentials that power the real customer path.
Schedule recurring checks, reports, and response workflows with a durable run ledger.
Keep deploys, checks, incidents, and drift in an attributable evidence history.
See third-party providers that can break your app.
Model outage blast radius and forecast time until a reliability threshold may be breached.
Ask questions against live workspace evidence and approve writes explicitly.
Bring PreFlight checks and evidence into your own systems.
Integration coverage
Each connection knows what success means for that provider and feeds the same alerts, release rules, evidence, and recovery workflow.
Public research library
Explore the public scanner briefs, individual checks, comparison guides, and use-case playbooks that explain what PreFlight can observe and where a deeper review belongs.
Coverage questions
Audit combines an outside-in scan of the public app with provider-specific probes for the services you connect. Full audit, targeted checks, and Custom Checks produce findings with evidence, severity, and a fix path instead of a single generic uptime number.
The catalog covers the services commonly on a SaaS customer path, including Stripe, Supabase, Clerk, Firebase, Vercel, Cloudflare, Sentry, PostHog, Resend, SendGrid, Twilio, Slack, Discord, Postmark, OpenAI, Upstash, Lemon Squeezy, and more. Each adapter checks the signals that matter for that provider.
Health brings uptime monitors, real-user speed, incidents, deploy context, backup integrity, API defense, and alert delivery into one recovery loop. Launch monitors at up to 5-minute cadence, Pro at 1 minute, and Max at 30 seconds; the exact interval is shown by your plan.
Route health, revenue, and release events to Slack, email, Discord, or a generic webhook. When a signal becomes an incident, the Issues view keeps ownership, remediation, and verification together so closing an alert also records how the system recovered.
Release Desk combines the current audit with deploy evidence. GitHub checks can report on pushes and pull requests, Journey Canary runs real browser paths such as signup or checkout, and Production Twin compares preview behavior with verified production evidence.
Checkout Test creates a Stripe test-mode session, verifies the signed webhook, checks the expected fulfillment side effect, and saves the trace. Payment Sync reconciles the payment with access; Revenue Guard repeats the path after deploys or on a schedule.
Growth connects keyword research, competitor comparisons, content gaps, topic clusters, article briefs, internal-link suggestions, and rank tracking. The workflow starts with a product-relevant opportunity, moves through editorial review, and uses results to choose the next page or refresh.
Trust Pages, Reliability Score, and Reports publish a controlled view of selected evidence. You decide what is public, and the page is built from the same checks and history used inside the workspace.
Yes. Custom Checks let you define HTTP requests, headers, assertions, and ordered steps for an endpoint or workflow that the built-in catalog cannot understand. Secrets and request headers can be stored encrypted and results appear with the same evidence model.
Operator answers questions against live workspace evidence and requires approval for state-changing actions. Pro and Max can also bring checks, reports, and approved workflows into external systems through the Developer API and MCP.
Yes. Create an app for the environment you want to verify, use test-mode credentials for payment rehearsals, and keep production comparison explicit with Production Twin. PreFlight records which app and evidence source produced each result.
Start outside-in
Run the free public scan without signup. Add providers only when you want PreFlight to protect the release continuously.