Dashboard
Copy MarkdownDashboard
Preflight works fully from the command line, with no account. The optional dashboard at app.preflight.sh adds a history of your scans and an AI-written fix for each finding.
Your code never leaves your machine. Scanning runs locally, and publishing sends only a redacted summary: check IDs, statuses, and the messages that are safe to share, never file contents or secret values. What publishing sends has the details.
Connect the CLI
Create a free account, then authorize the CLI. auth login prints a code and opens your browser to confirm it.
preflight auth login # authorize this CLI in your browser
preflight auth status # who you're signed in as
preflight auth logout # remove the stored credentialsOn a machine with no browser, such as a CI runner, sign in with a token: preflight auth login --token - reads it from stdin, or set PREFLIGHT_TOKEN and run preflight auth login. The token is checked and stored like a browser sign-in, and later commands use what was stored.
Publish a scan
preflight scan --publishIt prints a link to the run. Publishing is best-effort: offline or signed out, the scan still runs and exits normally.
The dashboard shows each run’s passes, warnings, and failures, every finding, and a history per project, so you can see what changed between deploys.
Runs are grouped into projects by the repository’s git remote. An app scanned from a subdirectory, such as one app in a monorepo, is keyed by that subdirectory too, so apps/web and apps/api are separate projects.
What publishing sends
- Each check’s ID, title, and outcome (passed, failed, skipped, or inconclusive, with its severity), and the summary counts.
- The real message for checks whose messages are built from fixed text, counts, repo-relative paths, DNS names, or public page content: the SEO and social checks,
security_headers,ssl,www_redirect,email_auth,debug_statements,error_pages,image_optimization,legal_pages, and the web standard file checks. Fordebug_statementsandimage_optimization, that includes up to five findings, by file and line or file and size. - Those messages are scrubbed first. Your configured staging and production URLs are cut to their origins; the IndexNow key, the Stripe webhook URL, the
seoMetalayout path, and the env file names are taken out; and every URL loses its credentials, query string, and fragment. - A generic message for every other check:
secrets,vulnerability,env_parity,health_endpoint,index_now, every service check (Stripe’sstripeamong them), and any check that failed with an error. - A redacted copy of
preflight.yml: the project name, the stack, the URL origins, the declared services, and which checks are on. The IndexNow key, the Stripe webhook URL, the secrets allowlist, the env file names, the health path, the layout path, and the ignore list are left out.
Suggestions, file contents, audit tool output, and secret values are never sent.
Read the history from the terminal
preflight history # recent runs across your projects
preflight history --here # only this project's runs
preflight history <run-id> # one run's full results
preflight history --here --format json # machine-readable, for agents
preflight history --limit 50 # more than the default 20--here matches runs to the current repository by its git remote, the same key publishing uses. --limit sets how many runs to list (20 unless you say otherwise). The JSON carries schema_version and cli_version, like scan JSON.
AI fix suggestions
Open any failed or warning check on a published run, and the dashboard writes a step-by-step fix for your detected stack, with commands and code to copy. Suggestions are made when you ask and kept on the run.
Plans
- Free: 5 published runs a month.
- Your own key: add an OpenAI or Anthropic API key in your settings, and publishing stays free and unlimited. You pay your provider directly.
- Managed, $5 a month: unlimited runs, with the AI costs on us and no key needed.