We built a post-quantum signing API (Dilithium3 / ML-DSA-65, FIPS 204).
The problem: if you're signing sensitive data through a third-party API, that API sees your data.
Zero-Exposure Signing (ZES) fixes this. Your client hashes the data locally (SHA-256 in browser, SHAKE-256 in the Python SDK), and only the 32-byte digest goes to our API. We sign it with Dilithium3 and return the signature. We never see the original data.
Try it in your browser — click the ZES Mode tab. No signup, no API key needed for the demo.
SDK: `pip install cyclecore-pq`
```
from cyclecore_pq import zes_sign, CycleCoreClient
client = CycleCoreClient("pq_live_YOUR_KEY")
result = zes_sign(client, b"sensitive data")
```
Free tier: 1,000 ops/day. We're a small team — happy to answer questions about the crypto, the architecture, or PQC migration in general. Cheers!
dev_PQC-focus•1h ago
The problem: if you're signing sensitive data through a third-party API, that API sees your data.
Zero-Exposure Signing (ZES) fixes this. Your client hashes the data locally (SHA-256 in browser, SHAKE-256 in the Python SDK), and only the 32-byte digest goes to our API. We sign it with Dilithium3 and return the signature. We never see the original data.
Try it in your browser — click the ZES Mode tab. No signup, no API key needed for the demo.
SDK: `pip install cyclecore-pq`
``` from cyclecore_pq import zes_sign, CycleCoreClient client = CycleCoreClient("pq_live_YOUR_KEY") result = zes_sign(client, b"sensitive data") ```
Free tier: 1,000 ops/day. We're a small team — happy to answer questions about the crypto, the architecture, or PQC migration in general. Cheers!