Your Data Never
Leaves Your SAP.
Ever.
All AI inference runs inside your BTP. Zero data exported. Zero external API calls. The only thing that reaches Zynoviq is your license ID.
Crystal Clear: What Stays, What Goes
Two zones, one unbreakable rule. Your business data never crosses the boundary.
Customer's BTP Environment
All data stays here. 100% of it.
Zynoviq License Server
Only license metadata. Nothing else.
What NEVER Leaves Your SAP BTP
Six Layers. Zero Trust.
Every Request Verified.
No implicit trust. Every layer independently validates every request. Compromise one layer — the other five still protect you.
Authentication
SAP XSUAA with OAuth 2.0 + OpenID Connect
Authorization
RBAC with SAP role templates, minimum 3 roles per domain
Transport Security
TLS 1.3 mandatory for all communication
Data at Rest
AES-256 encryption for all HANA tables
Audit Trail
SHA-256 hash-chained, immutable, 7-year retention
Secret Management
SAP Credential Store — zero hardcoded secrets
Every Major Framework.
Covered.
Not just checkboxes — deep, structural compliance built into every layer of the architecture.
SOX
Sections 302, 404, 409
GDPR
Articles 17, 25, 30, 35
SOC 2 Type II
All 5 Trust Service Criteria
HIPAA
PHI Protection
PCI-DSS Level 1
Cardholder Data Protection
ISO 27001
Information Security Management System
SHA-256 Hash-Chained.
Tamper-Proof by Design.
Every action, every decision, every risk score — cryptographically chained. Break one link and the entire chain screams.
Every Audit Record Contains:
How Hash Chaining Works
Tamper detection: If any record is modified, its hash changes, which breaks the chain for every subsequent record. The system detects this immediately and triggers an integrity alert.
7-Year Retention
SOX requirement met. All records retained for 7 years minimum with automated lifecycle management.
Read-Only for Auditors
AuditViewer role grants read-only access. No modification capability for any role — not even Admin.
Export Ready
CSV and PDF export for external audit tools. PwC, Deloitte, KPMG, and EY compatible formats.
8 Layers of IP Protection
in Every .mtar
The distributed binary contains zero readable source code. Reverse engineering cost exceeds building from scratch.
TypeScript source compiled to JavaScript — original .ts files never shipped
Type annotations, interfaces, and source maps stripped
All modules bundled into a single optimized file
Module boundaries, file structure, and import paths eliminated
Variable names shortened, whitespace removed, dead code eliminated
Human-readable code reduced to compact, unreadable output
Control flow flattening, RC4 string encryption, dead code injection
Reverse engineering cost exceeds rewrite-from-scratch cost
Python source compiled to .pyc bytecode — no .py files distributed
Source code inaccessible without dedicated decompilation tools
Models distributed as binary .gguf and .onnx formats
Weights and architecture embedded in opaque binary containers
All 50,000+ regulations encrypted with AES-256 at rest
Decryption keys loaded from SAP Credential Store at runtime only
Application refuses to start without a valid RSA-4096 signed JWT
No valid license = no process start. Period.
5-Layer License Validation
Unhackable. Unbypassable.
RSA-4096 signed JWT, BTP subaccount fingerprint binding, and Certificate Revocation List — license forgery is mathematically infeasible.
Real-time server call to Zynoviq license server. Application refuses to start if validation fails.
Background refresh of license JWT. Runs silently, updates local token cache.
Local JWT signature validation. No network call. Validates expiry, scope, and BTP fingerprint.
Real-time server call for user additions, module changes, or license modifications.
7-day grace period if license server is unreachable. After 7 days, app enters read-only mode.
Tenant Isolation at Every Layer
Cross-tenant data access is not just prevented — it is architecturally impossible. Every system enforces isolation independently.
SAP HANA
Separate schema per tenant with discriminator columns
Row-level security ensures queries only return data for the authenticated tenant. Cross-tenant queries are architecturally impossible.
SAP XSUAA
Tenant-specific OAuth scopes
Each tenant gets unique scope prefixes. Tokens are bound to a single tenant and cannot be used across boundaries.
Event Mesh
Filtered subscriptions per tenant
Event subscriptions include tenant_id filters. Events from one tenant are never delivered to another.
AI Models
Shared binaries, separate inference contexts
Model binaries are shared for efficiency, but each tenant gets an isolated inference context with separate memory space.
Audit Trail
tenant_id on every record
Every audit record includes a mandatory tenant_id field. AuditViewer role is scoped to a single tenant.
Security That Your
CISO Will Approve
Zero data leaves your system. Six-layer zero-trust architecture. Immutable audit trails. Every major compliance framework covered. Start your assessment today.