Every SaaS detector transmits student text to their servers.
The compliance wall that blocks Turnitin, GPTZero, Grammarly at K-12 and EU institutions.
Under FERPA (US education), GDPR (EU), and the EU AI Act Article 12 (August 2 2026 in force), transmitting identifiable student text to a third-party AI-detection API is a compliance event that requires DPAs, lawful basis, and tamper-resistant logs. Every SaaS detector fails at least one of those. On-prem deployment is the only clean answer. Our detector is CPU-only, air-gap-installable, and ships an Ed25519 audit log built in.
| FERPA-clean | GDPR-clean | EU AI Act Art. 12 log? | Air-gap install? | |
|---|---|---|---|---|
| Turnitin | Requires DPA + parental notice | Requires DPA | No | No |
| GPTZero | Requires DPA | Requires DPA | No | No |
| Grammarly Enterprise | Requires DPA | Requires DPA | No | No |
| Truth-in-AI (on-prem) | Yes (never leaves VPC) | Yes | Yes (Ed25519 log) | Yes |
On-prem deployment ships as a licensed, hardware-bound container. Buyer’s text never leaves their infrastructure. Audit log is Ed25519-signed at write time — tamper-resistant per EU AI Act Article 12.
Terraform module deploys inside AWS / GCP / Azure tenancy in a day.