Skip to content
INDUSTRIES

You are the customer base — not a vertical we also serve.

Qeino is built for four customer bases whose engineering signals cannot leave the perimeter: semiconductor and advanced manufacturing, regulated medtech, European defence-adjacent, and deeptech with regulated customers. The deployment model, the Ledger and the founder-market fit are shaped to these four — not retro-fitted from a generic platform.

SECTOR 01

Semiconductor & advanced manufacturing

Read the full sector view →
Trigger

Tape-out, mask-set and fab-slot windows do not move. A late integration signal turns a quarter into a write-off. The cost of a missed slot is measured in months and millions of euros, not story points.

Regulation & sovereignty

EU industrial-sovereignty posture, export controls and customer NDAs preclude sending code, signals or telemetry to third-party SaaS. Foreign-hosted assistants are out of scope by procurement.

Deployment fit

Air-gapped or on-prem inside the design environment. Read-only access to design, verification and integration repositories. Nothing leaves the perimeter — ever.

Founder–market fit

The founders have shipped against tape-out deadlines and lived inside semiconductor delivery cadence. The product is shaped by that pressure, not retro-fitted to it.

No attested figure on file for Semiconductor yet. Numbers appear here only when named, dated and CFO-signed by a pilot customer.
SECTOR 02

Regulated medtech

Read the full sector view →
Trigger

Class IIb and III device submissions, IEC 62304 software lifecycle and notified-body audits do not tolerate late surprises. A traceability gap discovered in week eleven is a submission slip, not a sprint issue.

Regulation & sovereignty

MDR, ISO 13485 and IEC 62304 govern the lifecycle. Patient data and design history files cannot leave the controlled environment under any vendor pretext.

Deployment fit

On-prem inside the QMS-controlled network. Read-only access to design controls, verification evidence and risk files. Every Qeino read is auditable for the notified body.

Founder–market fit

The founders have operated under notified-body review and lived the cost of a late finding. The Ledger's audit posture is built for that scrutiny.

No attested figure on file for Regulated medtech yet. Numbers appear here only when named, dated and CFO-signed by a pilot customer.
SECTOR 03

European defence-adjacent

Read the full sector view →
Trigger

European defence-adjacent programmes — dual-use, security-cleared engineering, sovereign capability build — cannot host engineering signals on foreign infrastructure. A delivery slip is a capability slip.

Regulation & sovereignty

National security clearance regimes, EU dual-use export controls and customer sovereignty clauses require on-soil, on-prem operation. No US or non-EU cloud surface, ever.

Deployment fit

Air-gapped on-prem inside the cleared environment. Read-only against the engineering surface. EU-sovereign by construction; no foreign egress path exists.

Founder–market fit

Qeino is European. The founders understand sovereign procurement and the discipline of building inside cleared environments. Qeino does not represent US defence-adjacent customers and does not operate in that market.

No attested figure on file for Defence-adjacent (EU) yet. Numbers appear here only when named, dated and CFO-signed by a pilot customer.
SECTOR 04

Deeptech with regulated customers

Read the full sector view →
Trigger

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.

Regulation & sovereignty

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.

Deployment fit

On-prem or private-tenant inside the deeptech company's own perimeter, mirroring the posture their customers will demand at audit.

Founder–market fit

The founders have sold into all four sectors above. The Ledger is shaped to survive the questionnaires those buyers actually send.

No attested figure on file for Deeptech yet. Numbers appear here only when named, dated and CFO-signed by a pilot customer.
RESIDENCY & COMPLIANCE

One posture, four regimes.

The same deployment posture answers every regime. Direct where the regulation names the sector, inherited where a deeptech vendor carries its customers' obligations upstream.

Status shown by label, never colour alone. Counsel-reviewed; see the Security page for the underlying control regime.
  • EU-sovereign hostingStatus: Verified
  • Air-gapped or on-premStatus: Verified
  • Read-only by constructionStatus: Verified
  • Counsel-reviewed positionsStatus: Verified
WHY NOW, IN YOUR SECTOR

The sovereignty bar is rising in all four.

European industrial policy, the EU AI Act, NIS2, MDR transition and DORA are not separate stories. They are one story: engineering signals that touch regulated work must stay inside the perimeter of the organisation that owns the obligation.

In semiconductor, the tape-out window does not move. In medtech, the notified body does not soften. In European defence-adjacent, the sovereignty clause is not negotiable. In deeptech, the customers' obligations propagate to the vendor.

Qeino is the answer that survives all four procurement conversations without changing its architecture.

Note: Qeino represents European defence-adjacent customers only. We do not operate in, and do not represent, the US defence-adjacent market.

Know what is about to break. Inside your perimeter.

Run a Foresight Pilot shaped to your sector — measured from day one, sovereign by construction.

Run a Foresight Pilot
Run a Foresight Pilot