Free
$0/ month
Prove the basics before you connect production systems.
- 1 project
- 3 manual audits each month
- 8 AI visibility checks
- 1 editorial draft
- 7-day history
01Built for vibecoders
Stop shipping brokenapps to real users.
Start with a free SEO audit — no signup. Then PreFlight scans your Stripe, Supabase, auth, emails, and webhooks in one click, and watches everything after deploy so you find problems before your users do.
Free SEO audit, no signup20+ integrations coveredAuto-blocks broken deploysYour code never leaves GitHub
preflight ~ free seo audit
liveChecks the providers your launch depends on
StripeSupabaseClerkLemon SqueezySentryPostmarkPostHogOpenAISlackDiscordPrivacy AnalyticsCloudflareFirebaseResendSendGridTwilioVercelUpstashEnvironmentDeploymentStripeSupabaseClerkLemon SqueezySentryPostmarkPostHogOpenAISlackDiscordPrivacy AnalyticsCloudflareFirebaseResendSendGridTwilioVercelUpstashEnvironmentDeploymentStripeSupabaseClerkLemon SqueezySentryPostmarkPostHogOpenAISlackDiscordPrivacy AnalyticsCloudflareFirebaseResendSendGridTwilioVercelUpstashEnvironmentDeployment
PostHogOpenAISlackDiscordPrivacy AnalyticsCloudflareFirebaseResendSendGridTwilioVercelUpstashEnvironmentDeploymentStripeSupabaseClerkLemon SqueezySentryPostmarkPostHogOpenAISlackDiscordPrivacy AnalyticsCloudflareFirebaseResendSendGridTwilioVercelUpstashEnvironmentDeploymentStripeSupabaseClerkLemon SqueezySentryPostmark
0+
Integrations covered
Stripe, Supabase, Clerk, Vercel, and more
0+
Things we check
Webhooks, auth, email, payments, secrets, DNS
0min
To your first scan
Connect, scan, fix — that fast
0
Bytes of your code we see
Seriously. We never touch your source.
Ship Guard · GitHub
Every push gets a health check. For free.
Ship Guard drops a GitHub Actions workflow into your repo. It runs readiness checks on every commit and posts the results as a commit status. Your code stays on GitHub — we only get a small JSON report back.
11minavg time from bad push to blocked deploy
0 bytesof your code ever touches PreFlight
100%runs on GitHub's own free runners
Connect GitHub
One-click setup, zero server cost
Authorise PreFlight once. We create a workflow file in .github/workflows/ — from then on, every push triggers a full readiness scan on GitHub's own runners and posts the result as a commit status.
Zero cost
All checks run on GitHub's free CI runners. PreFlight never sees your source code.
Shows up in your PRs
Commit status checks and PR summaries on every push — reviewers see health inline.
No secrets exposed
We only get key names and exit codes. Never key values, never source files.
Auto-block bad deploys
Wire the gate API to your CI. If checks fail, the deploy gets stopped before real users see it.
Requires repo scope for commit status and workflow file creation.
What gets checked
Build / Typecheck
Exit code + error headSchema Drift
Supabase migration parityEnv Parity
Key names vs .env.exampleDependency Audit
npm audit severity countsSecret Leak Scan
Pattern match, no values sentPR commit status
preflight/checksAll checks passed
Data Integrity Guard · Supabase
Supabase backups that work even on the free tier.
Supabase's free tier doesn't have a backup API. We work around that with metadata snapshots, pause detection, and integrity drills that verify your schema is intact. Zero row data stored, ever.
Connect Supabase
Works on every tier, including free
Metadata only
We grab table names, column names, and row counts. Never your actual data.
Pause detection
Catches those free-tier projects that silently go to sleep after inactivity. You find out before your users get a 500.
Integrity drills
Verifies every captured table is still present and readable. Not a file sitting somewhere — a live check that your data is intact.
RLS policy checks
Confirms row-level security is on for your public tables. Catches the auth hole nobody remembers to check.
What we never store
No row data, everNo query resultsNo schema contentsOnly table names + counts
Latest snapshot
3 min agousers
1,247 rowssubscriptions
891 rowswebhooks_log
42,810 rowsaudit_events
15,003 rowsIntegrity drill passed · all tables present and readable
The full picture
Everything that can break your app. One dashboard.
The launch scan is just the start. The real risk is what happens after deploy — so PreFlight keeps watching, blocking bad releases, and catching revenue drift.
The full protection surface
Everything that can go wrong. One health score.
From CI checks on every push to silent revenue drift detection — one platform for every failure mode between your code and your customers.
Ship Guard
Every push gets a health score
GitHub Actions checks on every commit — schema drift, env parity, secret leaks, dependency audit. Your code never leaves GitHub.
- Build / Typecheck
- Schema Drift
- Env Parity
- Secret Leak Scan
- Dependency Audit
100%
Runs on GitHub. Free.
Uptime Monitor
Always watching after deploy
5-minute sampling of every connected integration. Auth callback drift, webhook signature rotation, delivery failures — caught the moment they happen.
- Stripe webhooks
- Supabase auth
- Resend delivery
- Clerk JWKS
5 min
Sample cadence
Deploy Gates
Block broken releases at CI
One HTTP call. Checks, uptime, revenue, schema — all green means gate open. If not, CI fails before users see anything.
- Checks green ✓
- Uptime stable ✓
- Revenue reconciled ✓
- Schema synced ✓
1
API call to block a release
Revenue Watch
Stripe ↔ Supabase reconciliation
Silent billing drift is invisible until someone complains. Revenue Watch snapshots paid sessions and confirms they actually landed in your database.
- Paid sessions tracked
- DB rows matched
- Drift alerts sent
143/143
Sessions matched
Data Integrity Guard
Supabase backups on free tier
No backup API? We work around it. Metadata snapshots, pause detection, integrity drills — zero actual data stored.
- Table metadata only
- Pause detection
- Integrity drills verified
0 bytes
Of your data stored
Security
AES-256, zero customer data
Keys encrypted on save. Never shown again in the browser. Your user data stays in your own dashboards. We only store health metadata.
- Keys encrypted at rest
- Never echoed to browser
- Zero customer data
AES-256
Encryption at rest
Runbooks
Step-by-step fixes, not guesswork
Every failure maps to a recovery path: what broke, where to look, how to verify it's fixed. Real steps, not vague suggestions.
- Find the failed check
- Follow the fix steps
- Verify recovery
30+
Known failure patterns
Start free
One project. Unlimited scans. $0.
Free plan includes Stripe + Supabase checks, runbooks, and exports. No credit card. Upgrade when you need always-on monitoring.
- 1 project included
- Unlimited scans
- PDF + JSON exports
$0
To scan your first project
Inside the product
This is what you see after your first run.
Click the tabs to explore how checks, Sentinel monitoring, deploy gates, and revenue reconciliation are organized. This walkthrough contains no live telemetry.
app.getpreflight.dev / dashboard
Product preview
Your project
Readiness
98%
All systems nominal
Pre-flight checks
Last run: 4 minutes ago · 6/6 probed
StripeWebhook signing + endpoint reachabilityPass
SupabaseAuth admin access + DB connectivityPass
ClerkJWKS endpoint + frontend key scopePass
ResendVerified sender + delivery testWarning
VercelDeployment status + domain SSLPass
SentryDSN reachability + synthetic eventPass
10Before vs. after
Your users shouldn't be your monitoring.
These failures are tiny until launch traffic makes them visible. PreFlight catches the quiet breakages that never show up in a happy-path demo or localhost test.
Refreshing Stripe logs at 2 AM after a customer tweets about failed payment
One automated scan catches every fragile payment path before launch
Manually clicking 'Reset Password' to check if the email actually sends
Delivery checks fire on every push and again after every deploy
Discovering RLS was turned off after a user reports seeing other people's data
RLS probe flags the open table before the release goes live
Deploy went green but auth callbacks quietly broke under real traffic
Uptime monitor samples auth flows continuously after deploy
Webhook signing key rotated and nobody noticed for 3 hours
Signature mismatch gets caught in the next 5-minute sample
11How it works
Three steps. Five minutes.
Built for launch day and just as useful for every release after it.
Step 01
Connect
Add a project and link the integrations your app depends on. We store key names and health metadata — never your actual customer data.
Step 02
Scan
Hit the button. PreFlight probes your payments, auth, email, webhooks, and infra. Every check comes back pass, warning, or fail — with evidence.
Step 03
Watch
Turn on monitoring and deploy gates. PreFlight keeps checking after every release and routes failures to the channels you actually look at.
12Trust & operations
Your keys are safe. Your workflow is handled.
Safe by design
We ask for your API keys. That requires trust. Here's how we earn it.
- AES-256 encryption on everything. Your API keys get encrypted the moment you save them. They never travel back to the browser after that. Period.
- We don't store your user data. PreFlight only keeps health metadata. Your customers' data stays in your own dashboards where it belongs.
- Project-scoped key isolation. Each project gets its own encrypted key vault. Rotate a key in one project without affecting anything else.
key storage model
✓ STRIPE_SECRET_KEY → encrypted, scoped to project
✓ SUPABASE_SERVICE_ROLE → encrypted, never echoed
✗ values never returned to browserBuilt for operators
Alerts that are precise, readable, and point to exactly what needs fixing.
- Slack, Discord, and email alerts. Route failures to the channel you actually check during launch — not some generic inbox nobody reads.
- Full API + GitHub Actions support. Trigger scans, read gate status, pull reports — all from CI. No UI required.
- Share reports without giving access. Generate expiring links and PDFs for investors, ops teams, or compliance reviews. No account needed to view.
deploy gate check
GET /api/v1/projects/{id}/deploy-gate
→ 200 { gate: "open", score: 98 }Clear limits. No surprise usage bills.
Production confidence that compounds.
Start with evidence, then add continuous monitoring, managed model visibility, editorial workflows, and critical-journey verification.
Launch
$39/ month
Continuous launch protection for a serious independent SaaS.
- 3 projects
- 10-minute monitoring
- 100 AI visibility checks
- 5 editorial credits
- 100 Journey minutes
- 1 public trust center
Pro
$99/ month
Automated growth and reliability controls for a scaling product.
- 10 projects
- 5-minute monitoring
- 750 AI visibility checks
- 20 editorial credits
- 500 Journey minutes
- Autopilot and deploy gates
Max
$149/ month
Everything PreFlight does, at full scale — for a single operator running many production projects.
- 30 projects
- 5-minute monitoring
- 365-day history
- 3,000 AI visibility checks
- 60 editorial credits
- 2,000 Journey minutes
- 20 trust centers
- API, MCP, Autopilot, deploy gates, and Foresight
AI check: one prompt, provider, and locale.
Editorial credit: research through quality-gated revision.
Journey minute: one minute of isolated browser execution.
14FAQ
Questions you should ask before handing over API keys.
Straight answers. No filler.
Ready?
Five minutes. That's all it takes to know what's broken.
Connect a project, run a scan, and see exactly what would blow up at launch. Free plan, no card needed.
5 minutes flat
From signup to your first scan results.
Free forever tier
No card. One project, unlimited scans.
Guides for everything
Setup docs for all 20+ integrations.