EU-first · GDPR + EU AI Act

GDPR and the EU AI Act first. Every layer in one API.

Lexinode starts with GDPR privacy controls and EU AI Act governance, then audits accessibility alongside them. Point it at a site once; get remediation tickets and audit-ready PDF reports on a schedule you control.

Coverage
EU-first
Delivery
API + PDF
Onboarding
Self-serve

EU-first coverage

Start with GDPR and the EU AI Act.

Lexinode treats EU obligations as the baseline for a serious launch, then keeps accessibility in the same pass. Each engine maps findings to the regulatory clause that applies — so triage starts with severity, not with a vendor label.

01
GDPR · primary EU layer
Privacy
Continuous crawl against cookie banners, consent flows, data-subject endpoints, and policy versioning. Maps each finding to the article-level clause it violates.
  • Cookie & consent audits
  • DSR endpoint checks
  • Policy diff over time
02
EU AI Act · primary EU layer
AI governance
Detects disclosed and undisclosed model usage, training-data lineage gaps, and high-risk system classifications before a regulator does.
  • Model-inventory crawl
  • Risk-tier classification
  • Lineage documentation
03
WCAG 2.2 · accessibility
Accessibility
Axecore-level scans against every shipped route, with manual sampling on the flows assistive tech actually uses. Severity mapped to WCAG success criteria.
  • Per-route WCAG mapping
  • Manual a11y sampling
  • Atkinson-style reports
US applicability

The EU lead does not leave US teams behind.

The same audit maps US requirements across CCPA/CPRA, NIST AI RMF, and WCAG for a clean regional handoff.

secondary regional lens

Pipeline

From one POST to an audit-ready PDF.

  1. Point at a domain

    POST a domain root to api.lexinode.dev/v1/scans. We do the discovery queue, robots-aware, no PII required out of the box.

  2. Scheduled parallel crawls

    Three scan engines run on independent cadences. Privacy nightly, AI weekly, accessibility on every deploy you ping via the push hook.

  3. Tickets + audit PDFs

    Findings stream into your tracker of choice (Linear, Jira, GitHub) as remediation tickets. A signed PDF audit report is generated per scan cycle.

Developer API

Three endpoints. Zero SDK.

You can integrate Lexinode with curl. Tokens are per-domain, scoped, and rotated from the dashboard.

Kick off a scan cycle. Returns a scan_id you can poll.

  • domain · root URL to audit
  • layers · array; default all three
  • cadence · hourly / daily / weekly
# 1. Kick off a scan
curl -X POST api.lexinode.dev/v1/scans \
  -H "Authorization: Bearer $LEX_TOKEN" \
  -d {"domain":"acme.io","cadence":"daily"}

# 2. Pull findings
curl api.lexinode.dev/v1/findings?min_severity=high \
  -H "Authorization: Bearer $LEX_TOKEN"

# 3. Download the PDF report
curl api.lexinode.dev/v1/report/$SCAN_ID?format=pdf \
  -o acme-audit-$(date +%F).pdf

Pricing

One EU-first audit surface. Two clear operating modes.

Both plans use hosted Stripe checkout. Choose the cadence and scope that match your release motion, then keep every finding in the same developer workflow.

Read the audit API
Standard
$499/mo
1 domain · weekly cadence · 1 regulatory layer
  • 1 domain
  • Weekly cadence
  • 1 regulatory layer
  • Email remediation digest
Scale
Most chosen
$1,999/mo
Unlimited domains · on-demand rescans · all three layers
  • Unlimited domains
  • On-demand rescans
  • All three layers, in parallel
  • EU + US regional runs
  • SSO + role-scoped tokens
  • Dedicated support channel

FAQ

The blunt questions, answered.

Still curious? Write to lexinode@polsia.app.

Those platforms sell SOC 2 attestations to enterprise security teams. Lexinode audits three regulatory layers in parallel — privacy, AI, and accessibility — and ships findings as a developer API, without a procurement cycle. We complement those tools rather than replace them.

Start a GDPR + EU AI Act audit

Put GDPR and the EU AI Act on your deploy path.

Bring your domain and leave with a regulator-ready report. Email us with the domain you want audited and the layers you care about; we'll reply within one business day with a scan_id, the rule pack version we'll use, and a quote if it's outside the self-serve bands.