Skip to content
Verification, not certification — by design

Compliance that ships with your code

Continuous accessibility, cookie, tracker, and privacy-policy scans across every page you ship. Real findings, real fixes, public verification badge — built for engineers, not auditors.

No credit card. Free tier covers a small site indefinitely.

Why teams choose Auditly

Honest about limits

We say "verified," not "compliant." No automated scanner can certify legal compliance — and we don't pretend to.

All four pillars in one place

Accessibility, cookies, trackers, privacy. Most tools cover one. We cover them all so your team has one source of truth.

Findings you can fix

Every issue includes the exact location on your page, what's wrong, and a link to how to fix it. No vague advice.

How it works

From signup to badge in 5 minutes

1

Add a domain

Drop in a hostname. We generate a unique ownership token.

2

Verify in 60 seconds

Add a single <meta> tag to your homepage and click Verify. We check it once and remember.

3

Run a scan

Pick which pillars to run. Headless Chromium does the work. JSON results land in your dashboard within a couple of minutes.

4

Embed the badge

A public SVG badge linking to your verification page. Updates automatically on every successful scan.

Pricing

Honest, credit-based pricing

One scan on one pillar = 1 credit. Failed pillars are auto-refunded. Free plan covers small sites indefinitely.

Free

$0

25 credits / month

Pro

$20

100 credits / month

Business

$35

250 credits / month

Enterprise

$70

500 credits / month

Compare plans →

Common questions

Is this a substitute for a real audit?

No, and we don't pretend otherwise. Automated scanners catch ~50–60% of WCAG issues; we use ours for continuous monitoring and a structured punch list, then bring humans in for formal certification.

Why does the badge say "Verified" not "Compliant"?

Because we can verify a domain is monitored — we can't certify legal compliance. Vendors who claim otherwise are setting their customers up for liability.

Can I integrate with CI?

The API is designed for it; a GitHub Action is on the near-term roadmap. POST to /v1/scans, poll the result, fail the build on regression — that's the whole flow.

Find what you'd rather find before regulators or users do

Sign up, scan one site, see the report. If it's not useful, you've lost five minutes.