This is what your overview looks like. Pick a document and see how it works.

Send files safely and get documents signed, for small professional firms.

Free on the Community plan, for good. Paid business plans from €29 a month.

Your documents example

Communityplan

Before you start

Why Dutch matters

Dutch is a fact here, not a flag.

Where a supplier's owner is based decides which law reaches your client files, and who can be ordered to hand them over. That makes it a purchasing question. Here are the three answers.

  • The Dutch names were sold

    The parent of WeTransfer has been Bending Spoons in Milan since July 2024. Zivver has been part of Kiteworks in California since June 2025. Signhost went to Entrust in 2022, SignRequest to Box in 2021, and QuoVadis is on the Dutch trust list today as DigiCert Europe Netherlands. The names stayed Dutch. The owners did not.

  • This one was not

    Paramantis Solutions B.V., Harderwijk, KvK 42115132. Its parent is Paramantis Digital B.V., also Dutch, KvK 42114664. There is no parent company abroad. Dutch law governs the terms you agree to, and a Dutch court hears the dispute.

    Governing law →
  • And neither is the data path

    Servers at Hetzner in Nuremberg, Germany. DNS at Bunny in Slovenia. The encrypted files sit only there. Email still goes through Resend in the United States for now. For a send to named recipients that email carries the link with the token, and the pickup code is emailed too: whoever reads both emails can open the file. An invitation to sign carries half of the document key; the relay hands the other half only to the signed-in recipient. Resend, our email provider, is the one US party in the chain; we are moving to a Dutch provider. Every party with its status: /en/partners.

    The sub-processors →

We are Dutch, and we would rather say so than hide behind a Delaware address.

Ownership sources: the Kiteworks announcement of the Zivver acquisition (17 June 2025); the Bending Spoons announcement of the WeTransfer acquisition (31 July 2024); Entrust on Signhost (2022); Box on SignRequest (2021); the RDI trust service status list, which carries QuoVadis as DigiCert Europe Netherlands B.V. Checked 3 September 2026. The parent of Paramant is named on paramantis.nl, checked 23 September 2026.

What it costs

For your firm: 29 euros a month.

Excluding VAT, so €35.09 a month with 21% VAT. One payment for sending and signing together. You pay per month or per year, and nothing renews by itself.

For your firm

€29 a month, excl. VAT

What you get.

  • 100 signatures a month.
  • 500 transfers a month, up to 30 recipients per send, and links that stay valid for 24 hours.
  • The same encryption as every plan, and servers in Germany. The Data Processing Agreement applies to every plan.

Need more? Mail Mick: privacy@paramant.app

Community

€0 for good

Why half of this is free.

I research how personal data leaks from the apps and clouds people trust. Paramant is what I would want a small firm to have: a way to get a document signed and send a file, with client files that stay in Europe and proof you can check without us.

The Community plan is free, and stays free: 2 signatures a month, 50 transfers a month, one recipient per send, and files up to 500 MB when you hand them over live. No card, and no trial that runs out. That is my contribution to society.

Firm pays for the servers and the work, and keeps the free half free.

Mick Beer, privacy and security researcherFounder of Paramantis Solutions B.V. · Harderwijk, the Netherlands · KvK 42115132
Do not take our word for it

Five things you can check yourself, today.

Trust is not something a website can claim. These five facts are on public record outside this page, and each one comes with a link to where you can look it up.

  • A registered Dutch company

    Paramantis Solutions B.V., Harderwijk. The KvK register (the Dutch Chamber of Commerce) lists the company behind every promise on this page.

    KvK 42115132 →
  • Servers in Germany

    Hetzner in Nuremberg. Which company holds what, and the one exception for email, is written out line by line on the security page.

    Jurisdiction, line by line →
  • A public log

    Every registered key and every transfer leaves an entry in a tamper-evident log anyone can read. Not a claim about transparency: the log itself.

    Open the log →
  • What happens when something goes wrong

    A personal data breach is reported to you within 48 hours; that is in the signed Data Processing Agreement, not in a blog post. Your signature receipts verify without us, so they outlive us.

    Breach notification, clause 8 →
  • Code you can read

    The core and the relay are published. Nine rules, each with a link to the proof, are written down in one place.

    The nine rules →
Two things

Sending and signing.

Both in a plain browser. Nothing to install, for you or for the other side.

  • Send · ParaSend

    A file that disappears.

    • The file is encrypted in your browser before it leaves your device.
    • Our server only holds the encrypted file, in memory and never on a disk.
    • After the last read it is wiped. Nothing is left to leak later.
    • That holds for the web app and the SDKs. The browser extensions still encrypt on our server. We are changing that.
    • In the web app you send a link that the other person opens when it suits them, to one person or, with Firm, to several people at once. With Extra safe you and the receiver are both online and compare a short code, and the file is handed over live. You can also send with the API or the SDK.
    • One recipient per send on Community, up to 30 recipients per send on Firm.
  • Sign · ParaSign

    Get a document signed.

    • Upload the PDF, place the fields and email it to whoever has to sign.
    • They sign with the link from that email, after signing in to the account the invitation went to.
    • You keep a receipt anyone can check offline, plus an entry in the public log.
    • A simple electronic signature under eIDAS. Not a qualified one, and we say so.
The technology, for those who want to know

The core uses ML-KEM-768 for encryption and ML-DSA-65 for signatures, the two standards NIST published in 2024. Sending is hybrid: ML-KEM-768 together with ECDH P-256. How we keep the encryption current

The code is source-available (BUSL 1.1). Want to build on Paramant yourself? There is an SDK, a signing API and an installer for your own server. See the developer docs.