Pactlyra for desktop
On-device work is free here because of where it happens, not because of a plan you are on.
Most "free tiers" are an allowance on somebody else's server, withdrawn when the allowance runs out. Ours is a boundary about where the work happens: on-device is free, cloud execution is paid. That sentence was on this website before there was anything behind it. The desktop application is what makes it true.
What it does today
Open an evidence package — the folder, or the .zip exactly as it downloaded — and it tells you what holds:
- whether each file matches the hash the manifest recorded for it
- whether the certificate still matches its own seal
- whether the event chain is unbroken and in order
- and, if you point it at a document, whether that file is the one that was signed
It does this with the network off. Nothing is uploaded, nothing is logged anywhere, and it never asks who you are. You can check an agreement from a vendor you have no relationship with, including us.
It runs the same code as everything else
The application does not carry its own verification logic. It hands what it read to the same modules the platform runs and the same modules assembled into the verify.mjs inside every evidence package. Three ways to check, one definition — so an answer here and an answer from the command line cannot drift apart.
The window has no address bar, so it is careful
A desktop application that loads web pages is a browser with the part that tells you where you are removed. This one only ever navigates to Pactlyra's own hosts, over https, matched exactly — and any link that wants a new window is opened in your real browser instead, where you can see the address.
The installers are not signed yet
A build you install today will warn you that it is from an unidentified developer, on both macOS and Windows. That is accurate: we do not have an Apple Developer account or a Windows code-signing certificate yet, and we would rather say so here than have you meet the warning after downloading.
If that is a problem for your organisation — and it should be — build it from source, which is the same thing without the middle step.
What is not here
This is verification and the console, not editing. Pactlyra PDF — converting, merging, redaction, OCR, filling — is in build and is the rest of the on-device promise. There is also no automatic update yet, deliberately: an updater pointed at a feed nobody has set up is a background task that fails quietly forever, and this product treats silent failure as a bug.
Get it
The source is in the repository under desktop/, with the build commands in its README. Packaged installers follow once there are certificates to sign them with.
Or check a package without installing anything: download a real evidence package and run the verifier that ships inside it.
Last reviewed 2026-09-21. Pactlyra produces a detailed evidence record for every completed document. Electronic signature validity depends on your jurisdiction, the document type, and how the transaction is carried out; nothing here is legal advice.