Release confidence for fast-moving SaaS teams
Ship withproof, nothope.
Know whether your SaaS is safe to launch in minutes. PreFlight finds public launch blockers for free, then proves signup, checkout, that payment unlocks access, and production health after every release.
PreFlight dashboard products: Audit, Deploy, Journey checks, Preview comparisons, Monitor, Revenue, Operator, Uptime, Reports.
The continuous proof protocol
One release. Four signed moments.
PreFlight does not mimic four dashboards. It creates one chain of evidence that survives the release—from the decision to ship through the state of production.
Release / Verified artifact
The build earns permission.
Policy resolves against current build, migration, preview, and journey evidence before promotion.Release #482Journey Canary / browser proof
A 200 response cannot tell you the customer got in.
A clean browser drives your activation and revenue routes against the deployed app — signup through to a workspace, checkout through to unlocked access. Each step leaves an assertion, timing, screenshot, console record, and safe error when it fails.
Explore Journey CanaryCold Chromium session
200 /signupStripe test-mode checkout
checkout.session.completedThese tapes are a light, illustrative glimpse of two routes. The connected Journey Canary is far more capable: headless Chromium drives multi-step, authenticated contracts on the environment you configure — and retains the observed evidence for every step.
Revenue · Payment Sync
Prove every payment becomes customer access.
Run a safe Stripe test-mode purchase. PreFlight follows the provider event, verifies the signed webhook, confirms the expected Supabase change, and saves the full trace. Payment Sync keeps reconciling completed sessions after launch.
Revenue at risk
$0Open drift
0Reconciled
1,284Clean streak
43d1,284 payments matched
0 fulfillment gaps
Public-surface read / zero credentials
Attackers read the build you shipped.
PreFlight fetches only what the public internet can fetch. It follows the generated assets, source maps, rendered HTML, and reachable files that accidentally turn private credentials into public infrastructure.
Explore the launch auditObserved token
eyJhbGci…████████CriticalSupabase service_role key
Bypasses row-level securityIllustrative redacted artifacts. A real run records only evidence observed on the submitted domain.
Illustrative redacted artifacts. A real scan reports only evidence observed on the submitted public domain and redacts credential material at capture time.
See which customer path is unhealthy.
If your host is down, a monitor running on your host is down too. PreFlight probes public paths from its own infrastructure, connects provider health to the incident queue, and keeps the measured history in one recovery loop.
The Health Desk mirrors the operational dashboard and updates from your configured monitors, provider checks, and incident records.
Explore MonitorKnow what breaks before it breaks.
Every other tool tells you what already went wrong. PreFlight models the outage you have not had yet, projects the threshold you are about to cross, and names the upstream vendor before you spend an hour debugging code that was never broken.
The dependency model is a product twin of the workspace view. Your graph is generated from the providers and alert channels you connect.
Ask production. Get an answer with receipts.
This is the same interaction model users see in the dashboard. Operator reads live workspace evidence, shows the tools it called, separates observed facts from inference, and asks before it changes anything.
Every answer cites stored check failures, reports, revenue snapshots, incidents, or activity.
Opening an incident, pausing a monitor, or rerunning a gate waits for your approval.
Operator, REST API, and MCP read the same evidence store and return the same verdict.
The difference
A scanner grades your page. PreFlight proves your product.
The free public scan is the front door, not the product. Everything below is what happens once PreFlight can see the real customer path.
A scanner never touches your billing. PreFlight runs a test-mode checkout, verifies the signed webhook, and asserts the entitlement row exists.
Journey Canary drives a real browser through signup, login, checkout, and onboarding, and reports the failing step with a screenshot.
Ship Guard runs on every push and pull request, then fails the check when the build, migrations, env keys, dependencies, or leaked secrets say the release is not safe. Make it required and it blocks the merge.
Dependency Watch polls official vendor status feeds and attributes the failure to the upstream instead of your last commit.
Risk Forecast projects a confidence-rated ETA range for latency, failure rate, and expiry clocks, and flags accelerating trends.
Outage Impact simulates losing each provider, surfaces cascades and single points of failure, and finds the alert-channel blind spot.
Every run is stored, exportable as PDF, CSV, or JSON, and publishable to a branded Trust Center with expiring share links.
A scoped REST API and an MCP server expose the same evidence, so your editor or coding agent can ask production whether a change is safe.
Trust Center · Reports
Hand customers the proof before they ask for it.
Proof should be ready when the question arrives. Publish a branded status page wired to the checks PreFlight already runs, keep the measured history, and export the exact evidence a prospect, an auditor, or a teammate needs.
Publish your API, dashboard, auth, payments, or a custom service and bind each one to the PreFlight check that actually proves it. Nothing on the page is typed in by hand.
Rolling uptime per component with an incident timeline and scheduled maintenance, so a customer can see the pattern rather than a single green dot.
When a monitored component fails, the incident opens and subscribers are notified. You are not writing a status post while you are still debugging.
Logo, palette, copy, and a custom status domain. It reads as your status page, not as a third-party widget bolted onto your product.
PDF, CSV, and JSON exports of scoped evidence, so the reliability answer in a procurement review is a document rather than a promise.
Send one prospect one report without giving them a login, and have the link stop working on a date you choose.
The status board beside this mirrors the published layout. Your page only publishes the components you bind and the uptime your own checks recorded.
05/ 05
Customer-facing components with measured evidence
Your next release can carry evidence
Find the risk. Ship the proof.
Start with a free public launch audit. If the surface is clean, connect your app and prove the paths a scanner cannot reach: signup, checkout, access, deploys, and uptime.
No signup to scan · Setup guidance included · Cancel anytime