Skip to main content

quantacipher

Zero-Trust Post-Quantum Encryption SDK for Python
NIST ML-KEM (Kyber-1024) · AES-256-GCM · Native Rust Extension · Dual-Mode

PyPI version PyPI downloads Python Versions License: MIT Built with PyO3

Platform · API Docs · GitHub


What is this?

quantacipher is the official Python SDK for the QuantaCipher platform — a zero-trust, API-first post-quantum encryption system.

Under the hood, it runs a Rust cryptographic engine compiled to a native Python extension via PyO3. All encryption and decryption happens 100% locally inside your Python process. Plaintext never leaves your runtime. The QuantaCipher API Gateway only ever sees ciphertext.

No external crypto dependencies. No C++ build steps. Pure native performance.


Installation

pip install quantacipher

Requires Python 3.8+. Pre-built wheels are available for Linux, macOS, and Windows.


Initialization

Get an API key from your QuantaCipher Dashboard.

from quantacipher import QuantaCipher

sdk = QuantaCipher(
    api_key="qz_live_your_key_here",
    # gateway_url is optional — defaults to https://api.quantacipher.com/v1/ingest
)

Mode 1 — Vault Mode (Permanent Sealing)

Seal data forever. No decryption possible. Designed for HIPAA audit logs, compliance records, and tamper-proof audit trails.

How it works:

  1. An ephemeral Kyber-1024 keypair is generated locally inside the Rust engine
  2. Data is encrypted using the ephemeral public key (KEM shared secret → AES-256-GCM)
  3. The private key is immediately and permanently discarded from memory
  4. The QZ_VAULT_V1:... ciphertext is returned — undecryptable by anyone, including QuantaCipher
import json

audit_log = json.dumps({
    "user_id":   "U-00987",
    "action":    "FUNDS_TRANSFER",
    "amount":    50000.00,
    "timestamp": "2026-07-25T10:30:00Z",
})

# Encrypt locally — private key is gone the moment this returns
ciphertext = sdk.encrypt_vault(audit_log)
# → "QZ_VAULT_V1:BASE64_KYBER_CT:BASE64_NONCE:BASE64_AES_CT"

print(ciphertext[:60], "...")

Encrypt and send to the gateway in one call:

receipt = sdk.vault_data(audit_log, metadata={"source": "payment_service", "type": "hipaa"})

print(receipt["id"])               # "qz_rcpt_1753429812_abc123"
print(receipt["bytesSecured"])     # 156
print(receipt["encryptionScheme"]) # "Kyber-1024 + AES-256-GCM"
print(receipt["timestamp"])        # ISO 8601

There is no decrypt_vault. This is the guarantee — not a bug.


Mode 2 — Secure Mode (End-to-End Encryption)

Encrypt data your users need to read back. You hold the keys. QuantaCipher never sees them.

How it works:

  1. A persistent Kyber-1024 keypair is generated locally — you store the private key
  2. Data is encrypted using the public key — only the holder of the matching private key can decrypt
  3. Only ciphertext travels over the network
  4. Decryption happens locally — private key never leaves your application

Step 1 — Generate a Keypair

keys = sdk.generate_keypair()

# keys["publicKey"]  → base64 Kyber-1024 public key  (safe to share)
# keys["privateKey"] → base64 Kyber-1024 private key (NEVER share — store securely)
# keys["algorithm"]  → "Kyber-1024"
# keys["version"]    → "1.0"

print("Store the private key securely. QuantaCipher never has it.")

Step 2 — Encrypt

document = json.dumps({
    "patient_id":  "P-00123",
    "diagnosis":   "Confidential Medical Information",
})

ciphertext = sdk.encrypt_secure(document, keys["publicKey"])
# → "QZ_SECURE_V1:BASE64_KYBER_CT:BASE64_NONCE:BASE64_AES_CT"

Step 3 — Decrypt (locally)

plaintext = sdk.decrypt_secure(ciphertext, keys["privateKey"])
doc = json.loads(plaintext)
# doc["diagnosis"] == "Confidential Medical Information"

Wrong key = immediate rejection:

wrong_keys = sdk.generate_keypair()
try:
    sdk.decrypt_secure(ciphertext, wrong_keys["privateKey"])
except Exception as e:
    print(e)  # QuantaCipher Error: Kyber decapsulation failed (wrong key?)

Encrypt + send to gateway:

receipt = sdk.secure_data(document, keys["publicKey"], metadata={"user_id": "U-001"})
# receipt["id"], receipt["bytesSecured"], etc.

Low-Level API (without class)

For simple use cases, you can call the core functions directly without instantiating the class:

from quantacipher import generate_keypair, vault_encrypt, secure_encrypt, secure_decrypt

keys = generate_keypair()
ct   = secure_encrypt("Hello, quantum world!", keys["publicKey"])
pt   = secure_decrypt(ct, keys["privateKey"])
# pt == "Hello, quantum world!"

API Reference

QuantaCipher(api_key, gateway_url=None)

Instance Methods

Method Description
generate_keypair() Generate a Kyber-1024 keypair locally → dict
encrypt_vault(plaintext) Vault Mode encryption (ephemeral key, no decrypt) → str
encrypt_secure(plaintext, public_key_b64) Secure Mode encryption → str
decrypt_secure(ciphertext, private_key_b64) Secure Mode local decryption → str
vault_data(plaintext, metadata=None) Vault Mode + send to gateway → dict (receipt)
secure_data(plaintext, public_key_b64, metadata=None) Secure Mode + send to gateway → dict (receipt)
send_to_gateway(ciphertext, metadata=None) Send any ciphertext for a receipt → dict

Payload Format

All QuantaCipher ciphertexts are portable string tokens — versionable and cross-runtime compatible:

QZ_VAULT_V1  : <base64 Kyber-1024 CT> : <base64 AES-GCM nonce> : <base64 AES-GCM CT>
QZ_SECURE_V1 : <base64 Kyber-1024 CT> : <base64 AES-GCM nonce> : <base64 AES-GCM CT>

A ciphertext encrypted by the Python SDK can be sent to a JS application or the gateway interchangeably — the format is runtime-agnostic.


License

MIT — see LICENSE


Release files for quantacipher 2.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for quantacipher 2.0.3
File Interpreter ABI Platform
quantacipher-2.0.3-cp310-cp310-manylinux_2_34_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.34+ x86-64 Details

Release files / quantacipher-2.0.3-cp310-cp310-manylinux_2_34_x86_64.whl

Download URL quantacipher-2.0.3-cp310-cp310-manylinux_2_34_x86_64.whl
Size 475.6 kB
Tags CPython 3.10 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
1f9ea3dbadf1a5ae8fc65e531b724046e85321960ddf720b97fb561d92bebd30
BLAKE2b-256 checksum
How to use checksums
13b0bbfc2b356ba25f93b7eee4ee2ff3c98a85417ea60ed77b25a8c20a078646
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 28, 2026.

Transparency log

Release history Release notifications | RSS feed

2.0.6

1 release file

2.0.5

1 release file

2.0.4

1 release file

This release

2.0.3 This release

1 release file

2.0.2

1 release file

2.0.1

1 release file

2.0.0

1 release file

0.3.4

1 release file

0.2.0

3 release files

0.1.1

2 release files

0.1.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page