No phone home.
No telemetry and no external runtime dependency. The air-gapped install is the normal install.
Trust / Security & compliance
Compliance is an output, not a project.
The runtime produces the artefacts your DPIA, QMS and conformity assessment consume. The evidence exists because the agent ran — not because a review team reconstructed it six months later.
Security model
Isolation is a kernel property.
Application frameworks isolate at the process layer. Dintellinno pushes the boundary down to the kernel and keeps the capability decision on the dispatch path.
- seccomp-bpf limits the syscall surface per agent domain.
- Landlock bounds filesystem reach; cgroup v2 caps memory and CPU.
- Capability tokens are granted per tool, expire, and can be revoked.
- Zero egress is a deployment property, not a promise about network policy.
04
Scoped
Agent identity
Its own identity, purpose and data-scope manifest.
03
Revocable
Capability check
Tool grants evaluated before the call leaves the boundary.
02
Hard
Kernel enforcement
seccomp-bpf · Landlock · cgroup v2 · no ambient access.
01
Sealed
Evidence
Every verdict and tool call appended to the ledger.
Evidence map
Every obligation has an artefact.
The mapping below is the operating contract between the runtime and your compliance function. It is intentionally narrow: what the engine produces, and when.
GDPR ART. 30Record of processing
Per-agent purpose and data-scope manifest compiled from the typed definition, with tool-level data classes and retention fields.
Build
GDPR ART. 32Security of processing
Signed build manifest: seccomp-bpf syscall set, Landlock path rules, cgroup v2 ceilings and capability tokens granted per tool.
Check / deploy
EU AI ACT ART. 12Automatic record-keeping
Hash-chained, append-only ledger with one record per dispatch: agent, tool, policy verdict, epoch and timestamp.
Audit
EU AI ACT ART. 15Accuracy & robustness
Epoch-ordered replay bundle and a re-execution diff proving the same decisions in the same order.
Compile / audit
EU AI ACT ART. 14 / 26Human oversight
Approval, override and revocation events written to the same ledger, with per-tool grants that expire.
Deploy / audit
Sovereignty
Your perimeter. Your keys. Your evidence.
The engine is sold as software you operate, not a service that observes your traffic.
Your keys.
Data, policy and the evidence store live in your environment, under your access controls and retention rules.
Exportable proof.
The ledger exports to your SIEM, WORM storage or evidence platform. No proprietary format trap.
An honest boundary
What we produce. What stays yours.
No vendor can certify a deployer's compliance. Dintellinno provides the execution evidence; the legal assessment, operating controls and conformity decision remain with the organisation deploying the system.
Ask for a technical briefingRUNTIMEProduces
Evidence artefacts
- Per-agent purpose and scope manifest
- Signed capability and kernel manifest
- Hash-chained dispatch ledger
- Epoch-ordered replay bundle
DEPLOYERRetains
Compliance decisions
- DPIA and legal basis
- QMS and operating procedures
- Conformity assessment
- Incident response and notification
Bring your auditor
Put the evidence model under review.
We will walk your security and compliance team through the artefacts, the kernel boundary and the limits of the claim.
No certification claims · Evidence-first architecture