Comparison
Sekrd and Lovable's security scan
Lovable's scan runs inside the Lovable project. Sekrd scans a URL you can open in a browser, with no Lovable account. The Lovable facts below are from Lovable's security overview, fetched in November 2026.
As of November 2026.
Free scan. Pre-Launch Audit is $39 once. Continuous Pro is $24/month billed annually ($288/year), or $29/month billed monthly.
What Lovable's docs say
- Quick scan runs automatically when you open the publish dialog. It checks database access rules (tables without per-record access control, rules that let everyone through, leaked-password protection turned off), known vulnerabilities in npm dependencies, and an MCP server exposed without authentication.
- Only critical dependency vulnerabilities become findings. Some are not raised when Lovable has confirmed they cannot affect Lovable apps, or when their EPSS score is low. Those stay visible in the dependency list with a marker.
- Deep scan is on demand. It includes the Quick scan and reviews application code for access control, unauthenticated or abusable endpoints, unsafe input and injection, leaked secrets, payments, authentication, and personal data in errors and logs. It does not run automatically as you work, except that publishing an app whose MCP integration allows access without sign-in also starts a Deep scan.
- The docs say the built-in scanners and the optional Wiz connector perform static analysis by reading code and configuration. Dynamic testing is the optional Aikido pentest, billed by Aikido, which sends payloads against the running app.
- The docs say these tools cannot guarantee complete security and do not replace a review for apps that handle sensitive data. Running Quick scan or Deep scan does not count as build usage. Try to fix all draws on 10 free fixes, then credits. Asking in chat to review security uses credits. The scans themselves stay free in that sense.
- A Trust center can be enabled at /.well-known/trust.html on the app's domain. The docs say it publishes facts Lovable observes about the live app, that the app's code cannot edit the results, and that the page is informational, not a certification. The overview does not list which observations that page includes.
Sekrd
Sekrd does not read the Lovable project. It fetches the deployed URL. The free scan reports secrets in the bundle (not the publishable Supabase key), client env prefixes on server-secret names, security headers, and an unsigned payment webhook that returns HTTP 200. A deep scan, on the $39 audit or Pro, adds a read of common Supabase tables with the anon key found in the page, and can read policy SQL if you supply a database password. It does not apply Lovable's fixes.
Side by side
| Sekrd | Lovable security scan | |
|---|---|---|
| Where it runs | The URL you paste. | Inside the Lovable project. |
| Sees project source | No. | Yes. Deep scan reviews application code. |
| Sees the deployed bundle | Yes. | The built-in scanners are described as static analysis of code and configuration. |
| Price | Free quota, $39 once, or Pro. | Running Quick or Deep scan does not use build credits. |
| Account required | No, for a URL scan. | The Lovable project. |
When to choose them
Use Lovable's scan when the app is still in Lovable and you want the project source, the database rules, and the npm audit in the same editor that can try to fix them. Run it before publish. The docs tell you it is not a guarantee. Use Sekrd when you want to see what the deployed URL returns, including an app that was exported or hosted somewhere else, or when you want a second pass that does not depend on the Lovable project. Using both is consistent with what each one can see.
Related reading
- What Lovable's scan checks
A longer walk through the same docs.
- How to secure a Lovable app
The checklist after both scans.
- Scan a Lovable URL
The checks Sekrd runs on the deploy.
- All comparisons
Vibe App Scanner, CheckVibe, and VibeEval.
Frequently asked questions
Does Lovable's scan make Sekrd unnecessary?
No. Lovable's docs say the built-in scanners read code and configuration and cannot guarantee complete security. Sekrd reads the deployed URL, which is a different input. Neither result is a guarantee.
Does Sekrd replace Try to fix all?
No. Sekrd returns findings and, on a paid scan, fix prompts you paste into your editor. It does not edit the Lovable project.
Is Lovable's Deep scan the same as Sekrd's deep scan?
No. Lovable's Deep scan reviews the project's application code. Sekrd's deep scan adds read-only requests against the deployed URL, and optional Supabase or Firebase credentials you provide.