Releases
Download Klarion
One installer for every edition. Without a licence it runs as Klarion Free: the whole analysis engine, for non-commercial work, with no account and no expiry. A licence unlocks the automation in place.
1.2.2
Windows25.2 MBNo account needed5 Sept 2026Windows 10 1809 or later, 64-bit. Fixes five defects that could make a whole function come out wrong: a stripped ARM binary was decoded as ARM even when it is Thumb, calls into a shared library showed no name on recent Linux builds, functions ran past their end into the next one, a tail call was pasted in whole instead of shown as a call, and a segment's zero-fill tail was decoded as code. Measured against a public benchmark of exact control-flow recovery, this more than doubles the functions Klarion reproduces exactly. Carries the Visual C++ runtime, so it needs nothing installed first. Twelve architectures with an assembler for each, a decompiler for seven of them, PDB and DWARF 2 through 5, C++ class recovery, binary diffing, patching, and projects.
Downloadsha256:d25174e46efc19694569a7247b99da28a220b9b80e5e62d3cd7ae6c63c57accc
Verify before you run it
PS>Get-FileHash .\klarion-setup.exe -Algorithm SHA256
$sha256sum klarion-setup.exe
Compare the result with the checksum above. People verifying a reverse-engineering tool’s integrity is the norm, not paranoia. A tool you use to decide whether something is malicious has to be something you can check yourself.
Windows will warn you about this build
“Windows protected your PC”
This build is not yet code-signed, so SmartScreen shows a blue dialog saying it stopped an unrecognised app. Nothing is wrong with the file. The warning is about the certificate, not the contents: an unsigned installer from a company Microsoft has not seen before is exactly what SmartScreen exists to flag, and it would flag this one whether or not it were safe.
To run it anyway: More info, then Run anyway. Before you do, verify the SHA-256 above. That check is worth more than a signature, because it tells you the bytes are the ones we published, whereas a signature only tells you who compiled them.
We would rather say this plainly than have you meet the dialog unprepared and conclude the download is malicious. A signing certificate is on its way; when a signed build is published this notice disappears on its own, because the page reads it from the installer rather than from a paragraph someone has to remember to delete.
This build may not start at all
“vcruntime140.dll was not found”
We packaged this installer without the Microsoft Visual C++ runtime. It is not part of Windows, and every part of Klarion needs it, so on a machine that does not already have it nothing opens — you get a dialog naming a missing DLL before Klarion runs at all. That is our mistake, not anything wrong with your machine.
If that happened to you, install Microsoft’s Visual C++ Redistributable (x64) and Klarion will start. You may already have it from some other application, which is why this affects some machines and not others.
The next build carries the runtime beside the application, so it needs nothing installed and this notice disappears with it. If you downloaded Klarion, could not open it, and gave up — sorry. That one is on us.
Requirements
- Operating system
- Windows 10 1809 or later, 64-bit
- Memory
- 8 GB, 16 GB for large binaries
- Disk
- About 400 MB installed
- Other platforms
- Windows only at present
Air-gapped
A licence that never needs a network.
A large part of this work happens on machines that are not allowed to reach the internet, and a licensing system that assumes otherwise is useless in exactly the environments that need the tool most.
Klarion verifies a signed file against an Ed25519 public key compiled into the application. The private half never leaves our server, and the machine holding the file makes no network request: not at activation, not at start-up, not ever.
Issue a licence file- 01
Print the fingerprint
On the air-gapped machine: Help ▸ Licence, under Offline activation. It prints one string. On a machine with no window, klarion-cli licence fingerprint prints the same one. No network.
- 02
Carry it out
Type or copy it onto a machine that has a browser, sign in and paste it into your account page.
- 03
Take the file back
You get a signed licence file, wrapped at 64 columns so it can be retyped if that is what the room allows.
- 04
Drop it in
Help ▸ Licence, and paste it into the Activate box — or klarion-cli licence install <file>. The application verifies the signature locally and starts. That is the whole of it.
The part nobody else writes down
Revocation cannot reach a machine that never connects. A file signed for an air-gapped box keeps working there until it expires, whatever we do on our side. That is a property of offline licensing rather than a gap in ours, and no amount of engineering changes it, so it is written into the format specification and said here rather than discovered later.
Our licence signing public keyObligation
LGPL relinking kit
Object files and build scripts sufficient to relink Klarion against a modified version of the LGPL libraries it uses. No account, no sign-in. The obligation runs to anyone who received the binary, not to customers, and putting it behind a login would defeat it.
Request the relinking kitSent by return, to anyone who asks, with no account and no questions. The obligation runs to whoever received the binary, not to customers.