Security checks · Trust Center · Post-quantum

Security your customers can see.

Qopanza checks your app, code, cloud and database, tells you exactly what to fix, and turns what it finds into a Trust Center and answered security questionnaires, so proving you are secure stops holding up your deals.

The scan needs no account and takes about 30 seconds.

OverviewExample
81/ 100
+9 this week3 fixed · 1 new · checked today
  • WebsiteNo problems
  • Domain & email1 medium
  • GitHub1 high
  • Code & librariesNo problems
  • Cloud · AWS, CloudflareNo problems
  • Database · Supabase1 medium

Built on open standards

  • FIPS 203 ML-KEM
  • FIPS 204 ML-DSA
  • FIPS 205 SLH-DSA
  • CycloneDX 1.6 CBOM
  • SOC 2 · ISO 27001 control mapping

01 Scan · free

Start with what a stranger can see.

Built with Lovable, Bolt or Cursor? Paste your site’s address and see every leaked key, open database and missing protection your app hands to each visitor. No account needed.

  • Leaked API keys
  • Open databases
  • Published source code
  • Missing protections

Your site’s address

Free · No account · Results in seconds

Tested on 38 apps with planted problems: every one found, no false alarms. How it works

02 Watch

One score across everything you run.

Connect what you use, read-only. Qopanza checks it every day, scores each area, shows what changed this week, and tells Slack or your webhook the moment something serious appears. Every problem comes with the exact fix.

Website
Leaked keys, open databases, security headers and published source maps.
Domain & email
SPF and DMARC, so nobody sends mail as you, and certificates before they expire.
GitHub
Branch protection, secret scanning, push protection, Dependabot and organization two-factor.
Code & libraries
Every library your code installs, against the published vulnerability databases.
Cloud
AWS, Azure, Google Cloud, DigitalOcean, Cloudflare, Oracle and IBM: public storage, open admin ports, missing MFA.
Database
Supabase tables anyone on the internet can read or change.
Encryption
The cryptography in your code that a quantum computer will break.

Every check maps to SOC 2 and ISO 27001 controls, so the same results feed your compliance report.

03 Prove

Proof that closes the deal.

Before they sign, your customers ask how you keep their data safe. Answer from the same evidence that keeps you secure.

A Trust Center you can send

A public page of what is checked and what passes, with dates, and your own policies in your words. You choose what it shows. It never shows your score or an open problem.

Questionnaires, drafted from evidence

Upload the buyer’s spreadsheet. Each answer is drafted from your checks and policies with the evidence beside it; what the evidence does not cover is left for you, never guessed. Approve, and send back their own file.

Northwind vendor review · 64 questionsExample

Is multi-factor authentication required for administrative access?

Yes. Two-factor sign-in is required on our GitHub organization and on the AWS root user, as checked by Qopanza on November 6.

From Qopanza checksApprove

How often are backups tested?

Nightly backups to a second region; a full restore is tested every quarter.

From your policiesApprove

Do you hold a current SOC 2 Type II report?

Needs your inputNot in your evidence, so not guessed.

Post-quantum, built in

Ready for the day RSA breaks.

Traffic recorded today can be decrypted once a large quantum computer exists. NIST finalised the replacements in 2024, and governments have set deadlines running into the early 2030s. Qopanza takes you from a list of what you use to a migration you can prove.

  1. Find

    Every algorithm, wherever it is used

    Source code, dependencies and TLS endpoints, inventoried and ranked by quantum risk, with a CycloneDX CBOM to hand an auditor.

  2. Replace

    Post-quantum, through one API

    ML-KEM, ML-DSA and SLH-DSA, or hybrid X25519 + ML-KEM-768, from nine languages, with migration plans you approve and track.

  3. Prove

    On the record

    Every key operation in a hash-chained audit log you can verify, and attestations that show customers where you stand.

For developers

Post-quantum encryption in a few lines.

Call the API from the language you already use. Qopanza holds the keys, rotates them and records every use, or you keep them yourself in zero-knowledge mode.

  • Python
  • TypeScript
  • Go
  • Rust
  • Java
  • C#
  • Ruby
  • PHP
  • C++
Read the API docs

Building with an AI coding agent? Claude, Cursor and Codex can call Qopanza directly. Connect it

pip install qopanza
import os
from qopanza import QopanzaClient

client = QopanzaClient(api_key=os.environ["QOPANZA_API_KEY"])

# ML-KEM-768 + AES-256-GCM, with a key Qopanza manages for you
sealed = client.encrypt(plaintext=b"card ending 4242")

client.decrypt(**sealed)  # b"card ending 4242"

Pricing

Start free. Pay when you are ready to prove it.

Free

$0

See where you stand.

  • App security scan, every problem named
  • Your Overview, from the sites you scan
  • Trust Center preview and one questionnaire
  • Post-quantum API, keys and crypto scanning

App Security

—

Fix the leaks in your live app.

  • Everything in Free
  • Every finding in full: where, what and why
  • Step-by-step fixes for your host
  • Hand the fixes to your AI coding tool

Enterprise

Custom

For regulated organisations.

  • Everything in Pro
  • Enforced single sign-on
  • Custom limits and terms
  • A contract and a security review

Secure checkout with Stripe · Billed monthly, cancel any time · Prices in US dollars

Security you can check

A security company should be easy to verify.

  • Standard algorithms, not homemade ones

    ML-KEM, ML-DSA and SLH-DSA come from liboqs, the Open Quantum Safe project's widely used library. Nothing here invents its own cryptography.

  • Keys never stored in the clear

    Private keys are stored encrypted under a separate master key, and every decryption is recorded against the API key that asked for it.

  • Or never held at all

    In zero-knowledge mode you generate the keys and register only the public half. Qopanza can inventory and police them, and cannot decrypt anything.

  • Every use on the record

    Key operations go into a hash-chained audit log, so a changed or deleted entry is detectable. You can verify the chain yourself.

How we handle your data, in plain words: our security page and privacy policy.

Questions

Before you start.

More in the FAQ, or email support@qopanza.com.

What does the Trust Center show my customers?

Only what you choose: which parts of your setup Qopanza checks and when, how many of the mapped SOC 2 and ISO 27001 controls pass, your post-quantum status, and your own policies in your words. Never your score, and never an open problem. It is a record of what automated checks observed, not a certification.

How are security questionnaires answered?

Upload the spreadsheet a buyer sent. Each question is drafted from your Qopanza checks, your written policies and answers you approved before, with the evidence beside it. Anything the evidence does not cover is marked for you rather than guessed. You approve every answer and download the buyer's own file, filled in.

What is post-quantum cryptography?

Ordinary software cryptography, built on maths problems a quantum computer is not known to solve. It replaces RSA and elliptic curve, which a large quantum computer would break, and runs on the servers, laptops and phones you already have. NIST standardised it in 2024 as ML-KEM, ML-DSA and SLH-DSA.

Quantum computers aren't here yet. Why act now?

Because data can be recorded today and decrypted later, and because migrations take years. Anything that must stay private past the early 2030s is already at risk, and the first step, knowing what cryptography you use and where, is one most organisations have not taken.

Do I have to replace all of my encryption?

No. Symmetric encryption such as AES-256 holds up; what breaks is the public-key part: RSA and elliptic-curve key exchange and signatures. Qopanza's inventory shows exactly which uses are at risk, and the hybrid mode keeps a classical algorithm alongside the post-quantum one while you move.

Can Qopanza read my data?

With managed keys, encryption and decryption happen on our servers: your data passes through over TLS, is not stored, and every decryption is recorded in your audit log. If that is not acceptable, use zero-knowledge mode: you keep the private key, Qopanza only ever sees the public half, and it cannot decrypt anything.

Is the API really free?

Yes. Encryption, signing, key management and crypto scanning are free, with rate limits. Paid plans add continuous discovery and CI gating, migration plans, audit evidence and the app security fixes.

What is the app security scan?

A free tool for apps built with AI tools such as Lovable, Bolt and Cursor. It reads what your live site sends to every visitor and names every leaked API key, open database and missing protection, with no account needed. App Security shows where each one is and exactly how to fix it.

See what your app shows a stranger.

Thirty seconds, free, no account. Then decide what to fix, and what to show your customers.