Security and sovereignty, by design.
Your infrastructure. Your data. Your decision. Qriton is built for organisations that must control where data goes, who decides, and how every decision can be explained later.
Your perimeter
Deployed where your data lives. There is no Qriton-hosted copy of your data.
Policy first
Outbound connections are restricted by default and only made where your policy allows.
People in charge
Uncertain or consequential cases go to an accountable reviewer.
Evidence by default
Decision records, run records and receipts, kept in your environment.
Security controls.
- Identity and sign-on
- Deploys behind your identity provider or zero-trust gateway, so your sign-on and MFA policies apply first.
- Access
- Passwordless sign-in for people and individually issued keys for systems. No shared credentials.
- Encryption
- Encrypted in transit throughout. At rest, data stays in your storage under your own keys.
- Outbound access
- Validated against your policy. Every connection is recorded.
- Audit
- Runs and decisions recorded end to end, exportable for review.
Built for the EU AI Act.
In an EU-funded pilot (EUSAiR), Qriton was one of 80 companies assessed for robustness and EU AI Act compliance, and the only one working in such a high-risk domain.
Article 12
Record-keeping: decision and run records, kept together and replayable.
Article 13
Transparency: reasoning, uncertainty and sources delivered with every output.
Article 14
Human oversight: review thresholds, approvals and refusals when evidence is missing.
Article 15
Robustness and cybersecurity: Qriton Shield and governed, reversible change.
Qriton supports these obligations. Compliance depends on how the whole system is designed, deployed and run.
Runs where your data lives.
Found a security issue in a Qriton service? Report it to hello@qriton.com