LoricAI · IT
Technical verification, step by step.
Hardware platforms, data flow, key management, and checks your IT contact can repeat against the service profile.
Download the PDF guideHardware enclaves
LoricAI infrastructure offers hardware enclaves on NVIDIA RTX PRO 6000 Blackwell Server Edition and NVIDIA B200. AMD CPUs and NVIDIA GPUs contribute to verification of the protected environment. The assigned profile identifies the platform, protection mode, and customer configuration.
- GPU
- NVIDIA RTX PRO 6000 Blackwell Server Edition · NVIDIA B200
- CPU
- AMD · Confidential Computing
- AI model
- Qwen 3.8 Flash Next
- Hosting
- Verda
- Where the data is held
- Servers in the European Union, in Finland.
- Key management
- Google Cloud KMS
- Network and storage
- Cloudflare — network; encrypted R2 storage in the European Union. Backblaze — encrypted B2 backups in the European Union.
Backup retention: 5 years. The continuity plan distinguishes active storage, backups, recovery access, and deletion cycles. Erasure requests and applicable obligations are handled under the DPA and controller instructions.
How AI reads encrypted data
Device encryption protects transfer and storage. To process a request, data is decrypted only inside the authorized enclave where the AI model runs. The answer returns to your workspace over a protected channel.
Who controls key release
Each customer has a dedicated key, managed separately from documents through the key-management service. The key-management service does not receive documents. The release policy authorizes the protected environment after integrity checks; credentials, roles, and access logs govern key operations.
The IT verification procedure
Identify the service you are checking: CPU, assigned GPUs, AI model, software, and key-release rules.
Gather signed CPU and GPU proofs, certificates, and reference values. The proof must be recent and tied to your session.
Use official AMD and NVIDIA verifiers to check signatures, validity, and certificate revocation. Check every assigned GPU.
Compare measurements and protected mode with the authorized configuration. GPU verification does not replace CPU verification.
Check that expired, invalid, or mismatched proof blocks key release. Use demonstration data.
Keep the result, time, configuration, and verifier versions in your register.
Before sending a document, your app asks the chip for proof signed by AMD and NVIDIA. The proof shows that the protected area is sealed and runs only the program we published. If the proof does not check out, the document is not sent.
Security terms, explained.
- Confidential computing
- Protects data while CPUs and GPUs process it.
- Integrity proof (attestation)
- Signed evidence used to compare an environment against its authorized configuration.
- Data processing agreement (DPA)
- Defines roles, instructions, and customer data protections.
- Service levels (SLA)
- Define availability measurements, support, and contractual remedies.
- Acceptable use (AUP)
- Rules for using the service with authorized documents and access.