NageSecurity

Security

Nage is built for regulated sectors where "my model said so" isn't good enough. Every answer is source-attributed. Every mutation is cryptographically audited. Customer data can be surgically removed on request — not retrained out.

Isolation by architecture

Each VARVE is a residual low-rank adapter over a frozen FACIES. IsolationIQ ≥ 0.85 guaranteed — customer A's data cannot leak into customer B's routing. Tested per injection via SEDIM-Bench.

privacy_delete() — surgical removal

One API call erases a VARVE's weights, anonymizes its STEMMA logs, and keeps a signed deletion proof in the audit log. No 'retrain the model and hope'. GDPR / KVKK Article 17 built into the architecture.

Hash-chained audit trail

Every lifecycle mutation — promote, rollback, consolidation, delete — writes an event cryptographically linked to the previous one. Tamper breaks the chain visibly. Signed exports available as JSON, NDJSON, or text.

Data residency + encryption

Training data stored encrypted at rest (AES-256) + TLS in transit. Business tier picks EU or US region; Enterprise gets custom placement. Nage never fine-tunes FACIES on customer data — VARVE is the only write surface.

Authentication + authorization

JWT + API keys (SHA-256 hashed, never plaintext). Rotate keys without downtime. IP allowlist on Enterprise. Tier-aware rate limits enforce per-minute burst caps. 2FA / SSO / SAML on Enterprise.

Governed Consolidation

Merging a VARVE into FACIES is irreversible — so it requires admin approval + superadmin execution. FACIES snapshots are saved before each execution as an emergency revert. Human-in-the-loop by default for any permanent change.

Compliance roadmap

Today
GDPR + KVKK via privacy_delete(), hash-chained audit, EU AI Act Article 13 signed exports
Q4 2026
SOC 2 Type II audit process kicks off (6-month observation window)
Q1 2027
HIPAA BAA ready, healthcare vertical
Q2 2027
SOC 2 report published, ISO 27001 certification, Zero-Knowledge Training production
Q4 2027
FINRA compliance for finance vertical, federated VARVE for multi-org collaboration
Reporting a vulnerability

We treat security reports as a partnership. Send findings to security@nage.ai — first acknowledgment within 24 hours.

Bug bounty program launches with the SOC 2 Type II report (Q2 2027).