Trust

Trust center for sovereign post-quantum security

ExeQuantum works with governments and regulated enterprises. This page sets out how EQCore™ is built, the frameworks we map findings to and the verifications still in progress, stated plainly, with nothing claimed that we don't stand behind.

Security posture

Designed to keep your keys and data inside your boundary

EQCore is built to be deployed and run on your own terms - including fully offline. The controls below are part of the product, not an aspiration, with a sovereign, data-residency-preserving architecture that keeps sensitive material within your environment.

Deployment

Sovereign on-premise &
air-gapped

Run EQCore as a sovereign on-premise box or inside a fully air-gapped enclave alongside the cloud SaaS option. No public-cloud round-trip is required to run a scan.

Install integrity

Signed-bundle install

The on-premise bundle is verified at install so you can prove the software you run is the software we signed.

Transport

Per-box TLS issuance

Each deployment issues its own per-box TLS, so transport security is scoped to the box rather than shared across environments.

Egress controls

Central egress guards

Discovery runs behind central egress guards with target-bound scans so traffic stays inside the boundaries you set.

Isolation

Per-tenant isolation

Per-tenant isolation keeps environments separated so data residency and segregation hold across a multi-tenant deployment.

Data residency

Data-residency-preserving

Your keys and data stay within your boundary, written to your own database rather than ours, across every deployment mode.

Compliance frameworks

Findings mapped to the frameworks you report against

EQCore maps cryptographic findings to the governance frameworks public-sector and regulated teams answer to today. These are mappings the platform produces, distinct from any certification ExeQuantum itself holds.

NIST CSF ISO 27001 FedRAMP CMMC Essential Eight (ASD) NACSA

What this means

EQCore produces control-by-control mappings against a defined set of governance frameworks today.

Certifications & recognition

Credentials, stated only once confirmed

We show a credential only when it is held and verifiable, and label each for exactly what it is - a certification, a government recognition or an ecosystem partnership. The compliance frameworks above are what EQCore maps findings to, a product capability, not certifications ExeQuantum holds.

Certification

ISO/IEC 27001

Information security management system.

Government recognition

AUKUS Authorized User

Recognized by the Australian Government as a trusted provider.

Independent assessment

CREST-accredited Penetration Testing

Independent web application security assessment by ValueMentor. Zero non-informational findings. 

Ecosystem partner

Quantum Australia

Part of Australia’s quantum ecosystem.

Sovereignty

An Australian sovereign capability

ExeQuantum is built as a sovereign capability - software you can deploy and run inside your own boundary, including on-premise and air-gapped. That model suits allied and sovereign programmes where data residency and supply-chain assurance matter, with the install-integrity and isolation controls described above.

01

Run it in your boundary

Cloud SaaS, sovereign on-premise or fully air-gapped. The deployment model is yours to choose, so the platform fits within existing data-residency obligations.

02

Verifiable supply chain

Signed-bundle install verified with ML-DSA-65 and minisign means the build you receive is the build we signed - assurance that travels with the software.

03

Built for allied programmes

The sovereign deployment model is well suited to allied defence and national-security programmes. Specific programme and partnership details are set out in our credentials above.

Leadership

The people behind ExeQuantum

Cryptography, security engineering and sovereign infrastructure - the team that builds and ships EQCore.

Samuel Tseitkin

Samuel Tseitkin

Founder & Chief Executive Officer

Dr. Raymond Zhao

Dr. Raymond Zhao

Chief Technology Officer

Audrey Nicoll

Audrey Nicoll

Chief Growth Officer

Prem Kumar

Prem Kumar

Chief Information Security Officer

Benjamin Nicoll

Benjamin Nicoll

Chief Product Officer

Have a question about how we’re built?

Ask us about deployment, install integrity, framework mappings or anything else on this page. We would rather answer a hard question than over-claim.