Before you ship your AI-built SaaS, Assurly tells you in 60 seconds what will break in production — and what you can safely ignore.

Scan your live URL or public repo, get a trusted Ship Score, fix blockers with one-click PRs or AI prompts, and keep monitoring on every deploy — without uploading your source code to a third party.

Sign In with GitHubnpx assurly scan

How It Works

From a deployed URL to a fix you can ship — four steps, under a minute for the first scan.

URL Scan

Paste your live app URL. Assurly probes Supabase RLS exposure, secrets in the production bundle, and security headers — no repository required. The same scan returns an SEO & GEO Audit for machine readability.

Ship Score

One trusted verdict: blockers you must fix, warnings you can review, and noise you can safely ignore — tuned for high-confidence production risks.

One-Click Fix

Open an auto-fix pull request for common misconfigurations, or copy an AI fix prompt straight into Cursor or Claude Code.

Continuous Monitoring

Connect GitHub to scan every deploy, catch regressions early, and keep your Ship Score badge current.

Scan a Deployed URL

Paste your live app URL to probe Supabase RLS, production bundle secrets, and security headers — no repository required.

Scan a Public Repository Instantly

Enter a public GitHub repository path to inspect configuration flaws in real-time. No registration required.

github.com/

See It in Action

Assurly catches critical security misconfigurations that ship undetected to production.

terminal — assurly scan
$ npx assurly scan --path ./my-saas-app
OKStatic Analysis Engine initialized.
OKDetected stack: Next.js + Supabase + Stripe + Vercel
Scanning schema.sql...
ERROR[Line 3] Supabase table 'profiles' is created but Row-Level Security (RLS) is not enabled.
Add: ALTER TABLE profiles ENABLE ROW LEVEL SECURITY;
Scanning app/api/stripe/webhook/route.ts...
ERRORStripe webhook endpoint lacks signature verification.
Use: stripe.webhooks.constructEvent(body, sig, secret)
2 errors found. Fix before deploying to production.
Try it free — Sign in with GitHub

Why Assurly?

Local-First Scanning

Manual web checks run in your browser and CLI scans run on your machine. GitHub web integrations securely proxy selected repository content without retaining complete source files.

Zero-Bundle Overhead

Assurly runs as a development-only tool. It adds exactly 0kb to your final production bundle size.

Indie-Stack Native

Deep out-of-the-box rule configurations for Next.js, Supabase Row-Level Security, Stripe webhooks, and Vercel.

Auto-Fix Engine

Quickly repair common misconfigured variables or missing database scripts with deterministic CLI fix actions.

Scan your repository in 60 seconds

Connect your GitHub repositories to automatically detect security flaws, missing RLS policies, and unverified webhook endpoints on every push.

Connect your repo — Sign in with GitHub

The Real Cost of AI Code Vulnerabilities

AI code assistants write fast code, but miss critical production security. What could a single slip-up cost you?

Severe Risk

Missing Supabase RLS

Cost: €20,000+ GDPR fine & reputation ruin. Leaving a profiles or users table readable without Row-Level Security allows competitors to scrape your entire customer database in seconds.

Financial Loss

Webhook Spoofing

Cost: $100 - $10,000+ in api usage & unpaid features. A Stripe webhook endpoint lacking signature verification allows attackers to spoof events and gain premium access without paying.

User Dropoff

RSC Leaks & Cold Starts

Cost: 15% - 30% checkout conversion loss. Importing server-side database libraries inside client files increases serverless bundle sizes, causing massive loading delays and user bounce rates.

Calculate Your Savings

See how much time and money you save by validating your AI code deployments automatically.

8 hrs
$60/hr
Your Est. Monthly Savings
$461
ROI: 2526%
Manual Audit Cost$480/mo
Assurly Cost$19/mo
Net Monthly Savings$461

Simple, Transparent Pricing

Start free with the live proof-probe and one guarded app. Pro includes a 3-day free trial. Upgrade for a continuous guardian on every deploy — or embed the verdict in your own platform.

Free

$0/ forever
  • Live proof-probe: paste a URL, see what leaks
  • One guarded app
  • MCP server access for AI agents
  • CLI scanner (unlimited local scans)
  • Community support
Get Started Free

OEM / Platform

Customusage / seat
  • Everything in Pro
  • Keyed verdict API for your users
  • assurly_verdict MCP ship-gate
  • White-label “security-checked” widget
  • Higher programmatic rate limits
  • Volume pricing & priority support
Contact Sales

SEO & GEO Audit

Your app can look fine and still be invisible to AI

AI coding tools often ship sites whose HTML is little more than an empty root element. The page looks complete in a browser. ChatGPT, Perplexity, and Google's AI answers fetch that same HTML and find almost nothing they can read.

What the audit scores

Paste a live URL in the scanner above. Alongside the Ship Gate security verdict, Assurly returns an AI Readiness Score out of 100 with a separate machine-readability verdict — FULLY VISIBLE, PARTIALLY VISIBLE, or INVISIBLE TO AI. That score is not a ChatGPT or Perplexity ranking; Assurly does not query those engines. It reads your page the way a crawler would.

Concrete checks

The audit looks at canonical URLs, structured data (JSON-LD), llms.txt, server-rendered content, AI crawler access in robots.txt, and share images (og:image), plus related readiness signals such as title, meta description, and a single H1.

Scores first, fixes behind sign-in

Anonymous visitors see the headline scores and verdict immediately. Signing in on Pro unlocks every check and the exact fix for each gap — the same paywall the dashboard uses, not a CSS hide.

Built for teams shipping AI-generated code

The same production failures keep showing up — exposed Supabase RLS, unverified Stripe webhooks, secrets in client bundles. Assurly catches them before deploy.

Assurly is new, so there are no customer quotes here. Everything below can be checked yourself in about a minute.

13 rule areas

Supabase row-level security, Stripe webhook signatures, secrets in client bundles, React Server Component leaks, migration safety, connection pooling, edge compatibility, cold starts, agent tooling, and install-time trust (npm allowScripts).

Read the rule list

Three packages on npm

assurly, @assurly/scanner-core and @assurly/mcp-server are published and installable right now. Run the scanner against your own repository before you create an account.

View on npm

6 MCP tools

Cursor, Claude Code, VS Code and Windsurf can call Assurly as a ship gate before they deploy. A blocked verdict is returned as an error, so the agent stops instead of shipping.

See the MCP server

Your source stays on your machine

Local scans run entirely on your own hardware. The Trust page states exactly what is read, what is stored, and what never leaves your device.

Read the Trust page

MIT licensed

The scanner and the MCP server are open source. Read the rules, disagree with one, and check what it actually does rather than taking our word for it.

Inspect the source

No SOC 2. No ISO 27001.

Assurly holds neither, and says so on its own Trust page rather than implying otherwise. If a security vendor is vague about what it has been audited for, that is the answer.

See what we do claim

Questions people ask before shipping

Straight answers about what Assurly checks, what leaves your machine, and what it costs.

How do I know if my AI-generated app is safe to deploy?

Run a pre-deploy check that reads the project the way an attacker would, not the way the code reads. Assurly scans a Next.js, Supabase, Stripe and Vercel project across 13 rule areas and returns a single verdict — READY TO SHIP, REVIEW RECOMMENDED, or NOT READY TO SHIP — with a Ship Score out of 100. AI coding tools produce working code quickly but routinely leave production wiring unfinished: a database table without row-level security, a payment webhook that never verifies its signature, a service key that reaches the browser. Those are the gaps the scan is built to find.

What does Assurly check before I ship?

Assurly checks 13 rule areas: Supabase row-level security and exposed service-role keys, Stripe webhook signature verification, secrets and undocumented environment variables reaching the client bundle, React Server Component data leaks, SQL and migration safety, serverless connection pooling, Vercel edge compatibility, cold-start cost, TypeScript strictness, missing CI checks, the AI agent's own tooling and MCP configuration, and install-time trust under npm 12. Each finding arrives with the exact fix — the SQL statement or the config change — rather than a warning to go research.

Does Assurly upload my source code?

No. The Assurly CLI and the MCP server analyse your project entirely on your own machine and make no network calls while scanning. The manual web checker parses pasted snippets, folders and ZIP files inside your browser. Connected GitHub scans are the exception and are explicit: Assurly retrieves repository content server-side using a short-lived GitHub App token, stores findings, file paths and line numbers, and does not retain complete source files.

Which of my dependencies can run code when I install them?

Run `npx assurly scan --supply` to list them. npm 12 stopped running install scripts by default, so every project now records which dependencies it trusts to execute code during installation in an `allowScripts` allowlist. A bare package name in that allowlist grants execution to every version of the package, forever — including a version published later by whoever takes the package over. An exact version pin does not. Assurly reads the allowlist, the lockfile install-script flags and non-registry dependencies, entirely offline.

Can my AI coding agent run the check itself before deploying?

Yes. Assurly ships an MCP server with 6 tools, so an agent in Cursor, Claude Code, VS Code or Windsurf can gate its own work. Install it with `npx -y @assurly/mcp-server`. When the verdict is blocked the tool returns an error rather than a passing result, which stops the agent instead of letting it ship. Assurly also audits the agent stack itself with `npx assurly scan --agent`, reporting MCP servers that run shell commands, remote endpoints on plain HTTP, credentials written into config, and instructions hidden from readers but visible to models.

What is a Ship Score?

A Ship Score is a single number out of 100 summarising whether a project is ready for production, shown with one of three verdicts. Blockers are the findings that must be fixed before deploying and drive the verdict to NOT READY TO SHIP. When the verdict is blocked the score is capped so the number never looks like READY. Warnings are worth reviewing but do not block. The score exists so the decision to deploy is one answer rather than a list a non-specialist has to interpret.

Can Assurly run in CI and fail the build?

Yes. `npx assurly scan` exits with a non-zero status when the verdict is blocked, so it drops into any CI pipeline as an ordinary step with no plugin required. `assurly init` writes a GitHub Actions workflow for you. Because the CLI scans locally, CI needs no API key and no account.

Is Assurly free?

The CLI is free and unlimited: `npx assurly scan` runs the full gate locally with no account. The free hosted plan adds the live URL proof-probe, one guarded app and MCP server access. The Pro plan, at $19 per month, starts with a 3-day free trial and adds unlimited guarded apps, continuous monitoring on every deploy, AI deep review, auto-fix pull requests and private repository scanning.

Does Pro include a free trial?

Yes. Pro includes a 3-day free trial. You add a payment method at checkout; nothing is charged during the trial. Unless you cancel before it ends, the subscription converts to the plan you chose ($19 per month or $149 per year) and billing starts. One trial per customer and payment method.

What is the SEO & GEO Audit?

The SEO & GEO Audit scores a live URL for machine readability — separately from the Ship Gate security verdict. It returns an AI Readiness Score out of 100 and one of three verdicts: FULLY VISIBLE, PARTIALLY VISIBLE, or INVISIBLE TO AI. The audit checks canonical URLs, structured data (JSON-LD), llms.txt, server-rendered content, AI crawler access in robots.txt, and share images (og:image), among related readiness signals. It does not query ChatGPT, Perplexity, or Google for rankings. Anonymous visitors see the headline scores; Pro unlocks every check and the exact fix for each gap.

Support & Contact

Have questions, found a bug, or need help with your Assurly integration? Drop us a line.

Developer Support

Get direct technical assistance for integrating Assurly with your CI/CD pipelines, custom configurations, or custom rules.

Minimum 10 characters — a sentence or two is enough.