Deeptech with regulated customers.
You are the customer base — not a vertical we also serve. Qeino's deployment model, Ledger and founder-market fit are shaped to this sector.
A deeptech company whose customers are banks, hospitals, fabs or defence primes inherits its customers' sovereignty bar. A SaaS-hosted engineering assistant fails procurement before the demo.
The compliance surface is the union of the customer base — DORA, MDR, NIS2 and EU AI Act all show up in due-diligence questionnaires. The answer must be the same across all of them.
On-prem or private-tenant inside the deeptech company's own perimeter, mirroring the posture their customers will demand at audit.
The founders have sold into all four sectors above. The Ledger is shaped to survive the questionnaires those buyers actually send.
One posture, four regimes.
How this sector sits against the four regimes that matter.
Inherited high-risk posture from the customer base. In-perimeter operation keeps the deeptech vendor defensible.
Inherited through essential-entity customers. The deployment model is the control.
Inherited where medtech customers are present.
Inherited where financial-services customers are present; ICT third-party risk is addressable by deployment posture.
| Sector | EU AI Act | NIS2 | MDR | DORA |
|---|---|---|---|---|
| Semiconductor | Applies | Applies | Out of scope | Out of scope |
| Regulated medtech | Applies | Applies | Direct | Out of scope |
| Defence-adjacent (EU) | Applies | Applies | Out of scope | Out of scope |
| Deeptech | Inherited | Inherited | Inherited | Inherited |
The bar is rising. The window is short.
Deeptech buyers are now propagating sovereignty requirements upstream. A vendor without an in-perimeter answer is removed from the shortlist at procurement.
Know what is about to break. Inside your perimeter.
Run a Foresight Pilot shaped to deeptech — measured from day one, sovereign by construction.