Skip to main content
QuantumAPI

EU-Sovereign · Post-Quantum Transformation

Post-Quantum on Both Sides. Built in Europe.

ML-KEM keeps your data confidential. ML-DSA keeps it verifiable. Keys, tokens and signatures, quantum-safe by default — the sovereign alternative to Okta and 1Password.

  • ML-KEM + ML-DSA
  • NIST FIPS 203/204/205
  • Hosted in the EU
  • GDPR Compliant
Dossier · QAPI/SEC-2026open

The Problem

Sound familiar?

If any of these ring a bell, you are in the right place.

↓ Evidence01 — 04
01Exposure

Credentials scattered everywhere

API keys, passwords, and tokens spread across .env files, Slack messages, and spreadsheets — one leak away from a breach.

github.com/acme/api/.envpublic
1DATABASE_URL=postgres://prod-rw:aT9m█████████@db.acme.io
2STRIPE_SECRET=sk_live_51HxqA2cN████████████
3AWS_SECRET_KEY=████████████████6b3f
4SLACK_BOT_TOKEN=xoxb-2147483647-████████
5# pushed 4h ago · readable by anyone with repo access
▲ exposed · 4 secrets in plaintext
02Cost

Paying per user for Auth0 or Okta

100 users = €2,000+/month. Enterprise IAM tools price growing teams out of the market.

Auth0 · Enterprise · 100 seats
€2,000+
/ month, billed yearly
× 12 months€24,000 /yr
× 10 years€240,000
+ growth penalty↑ unbounded
03Jurisdiction

Your data is on US servers

Schrems II, GDPR, and NIS2 require EU data residency. US-hosted services put you at regulatory risk.

Data Residency Audit▲ Fail
us-east-1 · Virginia38.9° N · 77.3° W
us-west-2 · Oregon45.5° N · 122.7° W
Required: eu-only
Schrems IIGDPR Art. 44NIS2
04Timeline

Encryption that will not last

RSA and ECC will be broken by quantum computers. NIST standardised replacements in 2024 — most stacks have not caught up.

Algorithm LifespanNIST · 2024
RSA-2048~ 2030
ECC P-256~ 2032
AES-128shrinking
ML-KEM-768quantum-safe
Most stacks still ship column A.
End of fileContinue · Remediation
The numbers4 measurements
01
8
NIST-standard algorithms
FIPS 203 · 204 · 205, published 2024
02
< 2ms
p99 encrypt latency
Measured in production · Q1 2026
03
100%
EU-resident infrastructure
Hosted in the EU
04
€0
per seat, forever
No user, secret, or key fees
The Stack3 products · 1 platform

Three layers. Bought separately, built together.

01Available now

QuantumKeys

Encryption-as-a-Service

A REST API that encrypts, signs, and verifies with NIST post-quantum algorithms. Drop into any backend, any language. Quantum entropy on the hot path. SDKs in TypeScript, Python, .NET, Rust.

Learn more
02Included

QuantumVault

Key & Secret Management

A vault for keys, secrets, certificates, and rotation policies — encrypted at rest with the same PQC primitives that power the API. Every operation audited; every secret scoped to a tenant.

Learn more
03Available now

QuantumID

Identity Platform

OIDC and SAML federation with PQC-signed tokens. Bring Entra ID, Okta, Google Workspace — or roll your own. Authentication that survives the cryptographic transition.

Learn more

Start Encrypting in 60 Seconds

No PhD required. A single API call replaces hundreds of lines of cryptography code.

  1. 1

    Create a free account

    Sign up and get 100,000 API calls per month. Free during the beta, no credit card required.

  2. 2

    Generate an API key

    Create a scoped API key from the portal with granular permissions per resource.

  3. 3

    Make your first encryption call

    POST your plaintext and receive ML-KEM-768 quantum-safe ciphertext in milliseconds.

POST /v1/encrypt
curl https://api.quantumapi.eu/v1/encrypt \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "algorithm": "ML-KEM-768",
    "plaintext": "sensitive-data"
  }'

// Response

{ "ciphertext": "MIIBIjANBgkqhkiG9w...", "keyId": "k_7fG2" }
Inside the boxSix entries

Six things we don't compromise on.

A spec sheet, not a brochure.

01Cryptography

NIST-standard algorithms

Every algorithm we ship is a NIST-published standard, finalised in 2024. No experimental ciphers, no proprietary constructions. If it isn't in the FIPS catalog, it isn't in our stack.

  • FIPS 203 · ML-KEM
  • FIPS 204 · ML-DSA
  • FIPS 205 · SLH-DSA
02Entropy

Quantum-sourced randomness

The bits that seed every key come from a physical quantum process — not a deterministic PRNG. Generated by Quantum Blockchains in Wrocław, Poland; cached locally with a CSPRNG fallback.

  • Quantum Blockchains · Poland
  • ANU QRNG · backup
  • CSPRNG · fallback
03Sovereignty

100% EU infrastructure

Every byte stored, every key generated, every request handled — inside European jurisdiction. Hosted on EU infrastructure.

  • Hosted in the EU
  • Data stored in the EU
  • European jurisdiction
04Developer experience

API-first, by design

A small REST surface, predictable verbs, OpenAPI spec on launch day. CLI for ops, SDKs for the languages your team already writes. Infrastructure-as-code and CI integrations on the way.

  • REST · OpenAPI 3.1
  • CLI · qapi
  • SDK · TS · Python · .NET · Rust
  • Terraform provider · in progress
  • Azure DevOps extension · in progress
  • GitHub Actions · in progress
05Access control

Multi-tenant, by default

Tenants, organisations, groups, users — four nested boundaries with explicit inheritance. No accidental cross-tenant leaks. Every secret carries the policy of the org that owns it.

  • 4 levels · Tenant → User
  • Granular RBAC
  • Policy per resource
06Compliance

Auditable, end to end

Every operation — encrypt, decrypt, rotate, revoke — recorded in append-only audit logs. Designed to support your GDPR and NIS2 obligations.

  • GDPR · DPA-ready
  • NIS2 · in scope
  • ISO 27001 · roadmap

Quantum-Resistant Algorithms

All algorithms follow NIST FIPS 203, 204, and 205 standards.

Key Encapsulation (KEM)

ML-KEM-512
FIPS 203
ML-KEM-768default
FIPS 203
ML-KEM-1024
FIPS 203

Digital Signatures

ML-DSA-44
FIPS 204
ML-DSA-65default
FIPS 204
ML-DSA-87
FIPS 204
SLH-DSA-128s/f
FIPS 205

+ AES-256-GCM for authenticated symmetric encryption (FIPS 197)

Who’s behind QuantumAPI?

QuantumAPI is a personal project by a software engineer in Dublin, Ireland — the security infrastructure I wish had existed when I was building products myself.

Victor Zaragoza Lluch

Dublin, Ireland

hello@quantumapi.eu

Victor Zaragoza

Creator

Victor built QuantumAPI to solve problems he faced while building previous SaaS products: the cost and complexity of enterprise IAM tools, and the lack of accessible post-quantum cryptography for European companies.

The last step

Build like 2035 is already here.

100,000 API calls a month, free while in beta. No credit card. No per-seat fees. Quantum-safe from the first request.

Victor Zaragoza Lluch · 2026
QuantumAPI — Post-Quantum Encryption & Identity