We want you to leave us (until you shouldn't)

Most SaaS "we're so honest" marketing is still marketing. This post is the exception we actually believe: there are several cases where you should not use Vergate, and we'd rather tell you now than have you discover them after paying. A customer who stays because we tricked them is a customer who leaves angry — and angry customers are bad for everyone.

So here's the un-marketing post. The list of when to use something else.

#Don't use Vergate for: a one-off audit

Need to check one page, once, before a launch? Use the free tools. Lighthouse in DevTools is free, excellent, and maintained by the people who define the metrics. A free scan on vergate.dev covers the security side with no account or card. There is no reason to pay anyone, including us, for a single snapshot. We've said this before and we mean it.

#Don't use Vergate for: compliance-grade penetration testing

Our scans are fast, automated, and excellent at the top of the attacker's checklist — but they are not a human penetration test. If a client or a regulator needs a professional assessment with a signed methodology, scope negotiation and manual exploitation, hire a pentest firm. We say this in our terms, our docs, and our own transparency post: no scanner catches everything. Any tool that claims otherwise is lying about something.

#Don't use Vergate for: keyword research and rank tracking

Ahrefs, Semrush and their peers have indexes, history and competitive data we simply don't have. If you're doing serious organic search strategy — keyword selection, competitor gap analysis, backlink audits — use those tools. We didn't build a rank tracker, and we're not going to pretend our SEO/AEO module replaces one. (It does one thing they don't: analyzing the rendered page and AI-answer-engine readiness — see our comparison post.)

#Don't use Vergate for: a static HTML brochure site

If your site is five static pages, no JavaScript, no user accounts, no third-party scripts, and it hasn't changed since 2021 — a free scan will likely pass it with one or two trivial findings. Set up monitoring anyway for the uptime side (that's genuinely useful), but you almost certainly don't need a paid security subscription for a site that doesn't change.

#Use Vergate when the problem is continuity

Everything above is a snapshot problem. Vergate exists for the continuity problem, which is where free tools and specialists both stop:

• You ship often. Every deploy is a chance to regress something. Scheduled scans with regression alerts catch it at 9am, not at the next audit you remember to run.
• Your site is JS-heavy or AI-exposed. Rendered-page analysis and AEO checks are the difference between "the tool saw an empty div" and "the tool saw what Google and ChatGPT actually see."
• You want the whole picture in one workflow. Security + performance + SEO/AEO + accessibility in one scan, one history, one signed report, one MCP tool your AI assistant can call inline.
• You want to be alerted, not just audited. Monitoring with history, threat re-scans that diff against your last scan, and alerts to email, Slack, Discord or Telegram.

#The deal we're making

We'd rather lose your $20/month today than take it under false pretenses and lose your trust next month. If you read this post and realized Vergate isn't right for you — genuinely, thank you for checking. Use the free scan, use Lighthouse, hire the pentest firm, subscribe to Ahrefs. And if your needs change — when the site gets real users, real deploys, real third-party scripts — the free tier is still here, and we'll be happy to see you when the question you're asking is "is my site getting better or worse, and why?"