DESKTOP APP
The Paramant desktop app is no longer maintained
The last build is from March 2026. Paramant runs in your browser instead, with nothing to install and nothing to keep up to date.
What happened
The desktop app was a native build of the Paramant messenger. It ran in its own window instead of a browser tab.
The last release is v0.2.1, published on 28 March 2026. Nothing has been released since, and there is no build pipeline that would produce a new one. Treat it as an archive, not as a product.
What Paramant does today is document signing and encrypted file transfer. Both run in your browser, on servers in Germany, and there is nothing to download.
Free for everyone, paid for organisations
Every plan gets the same encryption, the same post-quantum signatures and the same public proof log. Pay for volume, never for security. And pay per organisation, not per user.
The Community plan is free, forever. It is not a trial and not a funnel. Organisations pay for the higher limits, not to unlock features. See the plans.
Who is behind it
Paramant is built by Paramantis Solutions B.V. in Harderwijk. The Community plan is free and stays free; the business plans pay for the servers and keep it that way. About Paramant.
What we checked, and when
Checked on 2 September 2026 against the files this site serves. The source repository is private, so there is no public commit log to link to. What you can check is the files themselves, with the commands in the right-hand column.
| Last release | v0.2.1, 28 March 2026. It shipped two files: the Linux .deb and an Android .apk. No release has followed it. |
|---|---|
| Versions | The .deb is v0.2.1. The .rpm, the AppImage and the Windows .exe are still v0.2.0, from 26 March 2026. There is no single version number that covers all four. |
| .deb signature | None, and it used to have one. The archive holds only debian-binary, control.tar.gz and data.tar.gz. A signed Debian package carries a fourth member: _gpgbuilder from dpkg-sig, or _gpgorigin from debsigs. Neither is there. Check it with ar t paramant_0.2.1_amd64.deb. |
| .rpm signature | None. rpm -qpi PARAMANT-0.2.0-1.x86_64.rpm reports Signature : (none). Only the digests are present. |
| AppImage signature | None. The .sha256_sig and .sig_key sections exist but are filled with zeroes, which is what the build tool leaves behind when nothing signs the file. |
| .exe signature | Authenticode, self-signed. One of the four carries a signature. Subject and issuer are both CN=Mick Beer, O=PARAMANT, C=NL, so it vouches for itself and proves nothing to someone who does not already have the certificate. Windows SmartScreen still warns. |
| Checksums | The four files served here match the published release artifacts byte for byte. The list is at /dl/SHA256SUMS. |
The signature was lost between the two releases, and that is worth stating plainly. The v0.2.0 package was signed with dpkg-sig: ar t lists a _gpgbuilder member holding a clearsigned manifest, signer 6EF8E5ACC444949E5A2EAA65CCE2378929A49B97, which is exactly the key the v0.2.0 release notes name. Those notes were accurate. The v0.2.1 package, the one this page serves, has no such member. So this is a regression in the build, not a claim that was never true, and it went unnoticed because nothing checked it.
Archive: the March 2026 installers
Check a file before you open it:
curl -sO https://paramant.app/dl/SHA256SUMS sha256sum -c SHA256SUMS --ignore-missing
On a phone there is nothing to install and nothing to check. Open paramant.app and add it to your home screen. That is the current version, not a build from March.