every decision.
on record.
kint runs decisions for organisations that answer to boards, regulators and the public. kint's own controls are part of the platform: sign-in through your identity provider, roles and releases, versioned data and a record of each run. kint hosts and operates the platform in Germany.
what the platform does. what you can show.
These controls are kint's own, built into the software and active on every run. Where the platform runs is set out below.
- 01
your identity provider
People sign in through your identity provider over OpenID Connect, with SAML on request.
- 02
role-based access
Roles separate who may model, run, release and read.
- 03
every action in the record
Uploads, model changes, runs and releases are recorded with who acted and when.
- 04
release
kint's decision agent proposes, and a person on your team releases each plan before it is written back. An approved workflow runs whenever your systems call it.
- 05
versioned data and replay
Every upload becomes a version with a content hash. Each run pins the data version, the model version and the solver settings, so the plan can be re-checked against the record.
- 06
data separated per tenant
Each customer's data is separated from other customers' data by tenant-level access control in the database.
- 07
encryption
Data is encrypted in transit (TLS 1.2 or higher) and at rest (AES-256).
- 08
language model on record
The agent uses a language model to read descriptions and draft models. Which model is used and in which region it is hosted is documented per setup. The plan itself always comes from a solver.
for your runs only
The data is used for your decisions.
never shared
The data is not shared with other customers.
never trains for others
kint trains no models for other organisations on your data.
documentation from the running system.
The obligations of the EU AI Act describe what a responsible system records and explains. kint records it during every run and maintains drafts of the documentation from that record.
kint keeps the drafts current. Compliance reviews them and owns the assessment, because the risk class depends on how your organisation uses a decision.
| Reference | Topic | What the platform contributes |
|---|---|---|
| Art. 9 | Risk management | A risk register drafted from the configured decisions and their limits. |
| Art. 12 | Record keeping | An audit trail of every run, logged automatically: data, model, settings, result, releases. |
| Art. 13 | Transparency | Plans from exact models name the binding limit and what one more unit of it is worth. |
| Art. 14 | Human oversight | A person releases each plan, and people can stop and override. |
| Art. 17 | Quality management | Versioned models and reviews that feed quality records. |
| Annex IV | Technical documentation | Drafts kept current from the running system, for your compliance team to review. |
hosted in germany. or in your network.
kint is hosted in Germany and operates the platform itself. For operations that must not leave your network, we scope an installation inside it.
| Where | Run by | What applies |
|---|---|---|
| hosted in Germany | kint | kint hosts and operates the platform: engine, decision agent and record. The controls above apply on every run. |
| your data centre | your team | An installation scoped for your infrastructure, with its identity provider, network rules and monitoring. Releases, the record and documentation work the same way. |
short answers.
For the full set, ask for the documentation pack.
Does our data train models for other customers?
Where does the language model run?
Can we re-check a decision for an auditor?
Can kint run inside our own network?
bring the questions your auditors ask.
Talk to the founders and engineers behind kint. We walk your security and compliance team through the controls, the record and the documentation drafts.
- Hosting
- hosted in Germany, or an installation in your network
- Regulation
- GDPR · EU AI Act documentation drafts
- Contact
- hello@kint.pro