Keep engineering data inside the agreed boundary.

On-premises

Qeino services and storage run on customer infrastructure. Deployment and update procedures are agreed before the pilot.

Air-gapped

Qeino is designed for isolated environments. The exact inference, update-media and custody path requires technical confirmation.

Controlled EU

Where policy permits, an EU-resident option may be scoped. Availability, tenancy, access and key management require technical confirmation.

Qeino reads authorised work-item metadata, repository activity, test evidence and team communication agreed for the pilot.

Qeino does not

• ✕Move or replace systems of record.
• ✕Send engineering data outside the agreed boundary for model improvement.
• ✕Move customer credentials outside that boundary.
• ✕Take write authority by default.
• ✕Score individual engineers.

Any later action authority is explicit, narrow and revocable by the customer.

The Security Overview covers architecture, data flow, connector scope, identity, deployment, update handling and current assurance work. Completed items are dated. Gaps are named.

Qeino is intended for programme delivery decisions. It is not intended for hiring, dismissal, compensation or individual performance decisions.

Sector and regulatory requirements are reviewed with the customer. Qeino does not claim compliance before the supporting analysis exists.

Review security, continuity, ownership and financial position before placing Qeino on a live programme. We provide current documents and name open gaps.

The pilot does not bypass procurement. It gives procurement evidence before a longer contract.