Security you can verify yourself.
Attestations ask a vendor risk team for trust. Qgentic gives it something to check instead: every control below can be reproduced in your own environment, against your own data, during technical validation. That is the scrutiny DORA's ICT third-party rules expect a regulated firm to apply.
The model proposes; code decides
The language model extracts and drafts, and that is all it does. Every validation, classification and final schema compilation is static, deterministic code, and nothing the model produces reaches a regulatory record without passing through that code first.
| Deterministic code: validation and logic | The model: extraction and drafting |
|---|---|
| Cryptographic checksums: ISO 17442 LEI (MOD 97-10), VRN mod-97, FRN regex | Unstructured data extraction (contracts, policies) to JSON schema |
| ISO 3166 / 4217 validation, regime-specific static rules engines | Drafting vendor outreach |
| Mathematical derivation: VAT aggregation, SLA/tolerance-breach calculations | Agentic exploration and data correlation |
| SHA-256 audit chaining, IAM/JIT token issuance, payload hashing | Nothing in the MTD module, which runs with no model at all |
Every action on a tamper-evident chain
Hash chains, verified continuously
Each service appends its state changes to its own SHA-256 hash chain, where every entry hashes the previous hash together with the canonical payload. The chains are verified continuously, and you can verify them offline with independent tooling.
A run verifies five service chains; in SaaS deployments a sixth audits API gateway activity and IAM approvals. The evidence is packaged as a hashed archive with a readable attribution report, and a complete data export keeps you portable.
No standing privileges
A high-privilege action, such as a regulatory submission or a bulk export, needs a short-lived HMAC-signed grant, and a grant is minted only after an IAM-authenticated person approves. The approval, the minting and the action are each recorded as their own audit event.
Where it runs
Multi-tenant cloud
Logical isolation between tenants. API credentials are hashed (SHA-256) at rest and shown once, at generation. UK or EU data residency is enforced, and every sub-processor is documented, with contractual notice before any change.
Single-tenant cloud
Physical isolation in a dedicated VPC, with your enterprise KMS holding customer-managed encryption keys (CMEK), and change controls that include named maintenance windows.
Air-gapped
A statically compiled binary with no external telemetry, no sub-processors and external API access switched off, so processing stays local and deterministic. In-process egress controls block and log outbound requests, and your standard network monitoring can verify all of it.
The delivery mechanics behind the on-premise topologies (cosign-signed images, pinned digests, IT-run updates and the pre-answered change request) are on the deployment and updates page.
Read-only into your ERP
Watched-directory files
Watched-directory integrations inside your perimeter, compatible with legacy ERP exports such as SAP AL11 output. Data flows one way, and Qgentic never needs write access to the source ERP.
REST polling
Read-only integration against REST endpoints you expose, authenticated with scoped bearer tokens. Pull model only: nothing external ever writes into your ERP.
The middleware you already run
Works with the iPaaS you already run, such as SAP CPI, MuleSoft or Boomi. Standardised boundary contracts make integration configuration, not an engineering project.
Bring your due diligence
Before you sign
A full security dossier, a lockfile-generated SBOM, signed binaries with published SHA-256 hashes, source-code review under NDA, and local technical validation. Everything your security team will ask for, ready before they ask.
In the contract
Pre-populated DORA register documentation (B_05.01, B_02.02, B_07.01), and schedules carrying Article 30 audit and access rights, defined exit and export protocols, sub-processor limits and documented capability boundaries.