Qpher

Your documents stay under your rules — on any device, over any network, after they leave your hands.

Encrypted on your device · Signed in your name · Opened only by the people you choose.

NIST post-quantum algorithms
Isolated key service
Encrypted on your device
Fail-closed API policy

WAYS TO USE QPHER

Three ways to use Qpher

Send documents outside your organization, set aside what your family should receive later, or build on the same engine.

Qpher Vault

For you and your organization

Encrypted on your iPhone, signed in your name, shared with any email address — no app to install, no password to set for the recipient.

Qpher Legacy

What matters today, protected for tomorrow.

You encrypt what matters on your device today, choose who should receive it, and arm your policy.

Qpher API

The same engine, for your product

The engine behind Qpher Vault, over REST, with SDKs for Python, Node.js and Go. Start with a free API key.

HOW IT WORKS

How a hand-off works

From your organization to someone outside it, on iPhone or in the browser.

1

Encrypt on your device

Add a document in Qpher Vault; it is encrypted on your iPhone before it is uploaded.

2

Sign in your name

Sign it with ML-DSA in your name before you share it.

3

Share with the people you choose

Share with any email address (the recipient opens it in the browser), see the activity, and revoke access when you are done.

ONE ENGINE

One engine behind Vault, Legacy and the API

Vault, Legacy and the API share one isolated key service.

Keys that stay in one place

Private keys are generated and used only inside Qpher's isolated key service. No API can export them.

Hand-offs across organizations

Sharing outside your organization re-wraps the document's key for the recipient; the document itself is not re-encrypted.

A portable, signed copy

A portable, tamper-evident encrypted copy; to open it again, come back to Qpher with the same email.

FOR DEVELOPERS

The same engine over REST

SDKs for Python, Node.js and Go. Server-side mode: Sent to Qpher over TLS, processed in memory, never stored.

import requests

response = requests.post(
    "https://api.qpher.ai/api/v1/kem/encrypt",
    headers={
        "x-api-key": "qph_abc123...",
        "Content-Type": "application/json",
    },
    json={
        "plaintext": "SGVsbG8gUXVhbnR1bSBXb3JsZA==",
        "key_version": 1,
    },
)

data = response.json()["data"]
print(data["ciphertext"])  # base64-encoded quantum-safe ciphertext

Hand off your next document under your rules

Start with Qpher Vault on iPhone, bring your organization in through Qpher Console, or build on the API.

Ask Qpher AI