Send it. Sign it. Prove it.
One encrypted relay for files and documents. End-to-end post-quantum crypto, RAM-only servers in Germany, and a public transparency log, so you never have to take our word for it.
Your documents.
Continue a request, start signing or send a document securely.
Sign and send, right in your browser.
Drop post-quantum crypto into your stack.
Weighing the options? See how Paramant compares to Zivver, Tresorit, WeTransfer and SFTP →
live today
Three ways in. One crypto core.
Everything below is running now, on the same audited post-quantum core. No roadmap promises on this list.
paramant-corePQ primitives · ML-KEM-768 · ML-DSA-65 · SPHINCS+ · Falcon
-
ParaSend
Send files that vanish.
End-to-end encrypted transfer through a relay that only ever holds ciphertext in RAM. Burned on read. Dedicated relays for finance, legal and IoT traffic.
Send a file -
ParaSign
Sign PDFs in your browser.
A full PDF editor: place text, dates and annotations, manage pages, then sign. Co-signing with routing order. Your key never leaves your device, and every signature comes with a verifiable .psign receipt.
Open ParaSign -
Developers
Build on the core.
Open SDK in JavaScript and Python (Apache-2.0), a /v1 signing API, and a self-host installer. Run your own relay, or the whole OS.
Get an API key Read the /v1 API docs
our policy
Rules you can check. Every one has a proof.
Everyone has a privacy policy. The ParaRules come with a verify link each: a log, a header, a repo. Not a promise.
- 01
We never had it
Encrypted in your browser, held in RAM, burned on read.
verify: architecture - 02
Your browser talks only to us
No third-party requests. No fonts, CDNs, analytics or pixels.
verify: open devtools - 03
You own your keys
Generated on your device, never sent. We see only the public half.
verify: SDK source - 04
EU soil, EU law
Hetzner Germany, Bunny DNS (Slovenia). No US provider in the chain.
verify: dig and headers - 05
Quantum-ready by default
FIPS 203/204 today, not “soon”.
verify: KAT vectors - 06
Verifiable, not trust-me
Open-core, a public CT log, receipts anyone can check offline.
verify: CT log
in development
What’s next. Labeled honestly.
In development means exactly that: not live, no dates promised. It ships when it verifies.
-
In development
Mandate credentials
Prove you may sign or act on behalf of an organization: a scoped, revocable credential, checkable offline.
-
In development
Registered delivery
Send a document and get an offline-verifiable proof of filing, anchored in the public transparency log.