Security and control
Control you can prove.
Your keys, a signed installer, a record of every release and a way back. Each named with its status.
Five controls
What protects your model.
- 01Keys held by youIn Cloud, your data sits on your own volumes, with keys you hold.Planned
- 02Signed installerInstalled from signed, versioned templates, on your machines or ours.Planned
- 03Audit recordEvery release, its test result and who approved it. A full request audit log follows.Planned
- 04RollbackBack to the last good release, at any time, by the owner. Designed for 60 seconds.Design
- 05Safety railsAsks for approval before any outside action. Trained to refuse misuse. Defense work only through cleared partners, never weapons targeting.Planned
What exists today: a scoring harness with pinned data and seeds, sealed test sets kept apart from training, training on local machines and on H200 GPUs, and every result published at benchmarks.eigna.ai. The five controls above are planned or a design target.
Where your data goes
Mode by mode, word for word.
| Compared | Eigna Local | Eigna Hybrid | Eigna Cloud |
|---|---|---|---|
| In one line | Data never leaves. | Data stays in the region you choose. | Data stays in the region you choose. |
| Your data | On your machines. | Sensitive work on your machines. Main-expert prompts go to our GPU pool in your region over mutual TLS, with no prompt logs by default. | On your own volumes in the region you choose, with keys you hold. |
| Learning | An encrypted training snapshot goes to a GPU we rent in a region you approve, and is deleted after the run. | From approved work only. The training path is confirmed in your offer. | From approved work only. The training path is confirmed in your offer. |
| Other clients | Your data never trains anyone else’s model. | Your data never trains anyone else’s model. | Your data never trains anyone else’s model. |
For the regulator
Easier to explain to your board and your regulator.
You can say who owns the model, what changed, when, and why. Designed to support your compliance work, not to replace it.
- 01
- A named owner for every model
- 02
- A signed Model Deed
- 03
- Sealed tests for every release
- 04
- Every release recorded and reversible
EU AI Act high-risk duties apply from 2 December 2027 (Annex III) and 2 August 2028 (Annex I), Regulation (EU) 2026/1744.
Keys held by you
The key stays with the owner.
Your model and your data, under keys you hold, on your machines or on your own volumes. Client-held keys are planned with the run modes.
Questions and answers
Does our data train anyone else’s model?
No. Client data never moves between clients. Only examples you approve train your model.
Who holds the keys?
You do. In Cloud, your data sits on your own volumes, with keys you hold. Client-held keys are planned with the run modes.
What is recorded?
Every release, its test result and who approved it. A full request audit log is planned.
Start
Send us your security questions.
We answer the questionnaire in writing: data handling per mode, keys, installer, audit and what is still planned.