Ship the AI features compliance keeps blocking.

# Lucairn > We pseudonymize sensitive data before the model sees it. Every AI call ships with a signed certificate your auditor can verify. Built for regulated organisations in Europe that want AI in real internal workflows without taking on compliance risk. ## What It Is Lucairn is a split-knowledge processing platform for safe AI use on sensitive business data. Two sandboxes — one holds identity (WHO), the other runs AI (WHAT). They cannot communicate directly. An ID Bridge connects them using opaque pseudonymous tokens. Re-linkage requires audited, access-controlled operations with a legitimate legal basis. This is not data redaction. Redaction is a software promise — a bug leaks PII. Lucairn enforces separation at the infrastructure level via Kubernetes NetworkPolicies and Docker network segmentation. The AI processing environment is network-isolated from identity data. ## Current Launch Lane - Brand: **Lucairn** - Main product: **Lucairn Core** - Wedge: **Lucairn PII Scanner** (PII exposure assessment — the conversation starter) - Evidence layer: **Internal component of Lucairn** (cryptographic AI decision provenance; part of Lucairn Core, not sold as a separate product; public surface at /evidence-layer; internal name VeilVault) - First vertical: **ITSM / ServiceNow-style internal workflows** - Deferred (not launch-ready, intentionally withheld from active marketing): **Veil Agent** - Commercial tiers: new self-serve signups receive **30 days of Pro features**. **Developer** is BYOK with 500 requests/month after the trial. **Pro** is BYOK with 50,000 requests/month, waitlist, no published price. **Enterprise** is self-hosted, contract; Assessment → Pilot → Production license. No credit-card checkout on any tier. ## Core Concept - [How It Works](https://lucairn.eu/en/how-it-works): Architecture overview — how identity and AI processing are separated at infrastructure level - [FAQ](https://lucairn.eu/en/faq): Common questions about Lucairn, c

# Source of truth: docs/openapi.yaml in # https://github.com/Declade/dual-sandbox-architecture # # Regenerate this file by copying the upstream copy: # curl -fsSL https://raw.githubusercontent.com/Declade/dual-sandbox-architecture/main/docs/openapi.yaml \ # > public/openapi.yaml # # Drift between this copy and the upstream is a known v1 risk. CI does # not auto-sync today. When the gateway team ships a major API change, # follow up with a sync PR on theveil-website. # # Note on legacy lite