Row by row, in plain English
Where AkiProtect matches the established competitors, where it goes further, and where it does something none of the others do. Honest, not marketing.
01
Compression (LZ77, LZ4, LZNT1, LZMS)
AkiProtect goes deeper
All four protectors compress payloads. AkiProtect ships four codecs — the standard LZ77 and LZ4, plus two Windows-native codecs (LZNT1 via ntdll, LZMS via cabinet.dll) that add essentially zero code to the runtime stub. Themida, VMProtect and Enigma each bundle their own one or two proprietary codecs. More codec choices mean more shapes of compressed output, which means fewer signature matches across your release history.
02
Code virtualization (VM)
Industry parity
All four have a VM. Themida pioneered the multi-architecture model (FISH/TIGER/DOLPHIN). VMProtect is single-VM but very mature. Enigma has its own VM. AkiProtect's VM is a 9-register custom design with the opcode mapping randomized per build using Windows CSPRNG — so two copies of the same source binary, built ten seconds apart, execute completely different bytecode. The same crack does not work twice.
03
Multi-pass virtualization
AkiProtect goes deeper
Stacking the VM transformation on top of itself multiplies reverse-engineering effort. Themida supports it via combined Mutation + Virtualization. AkiProtect lets you apply up to 8 independent VM passes, each with its own opcode map. VMProtect and Enigma are single-layer virtualization — you can mark more functions for virtualization, but they all go through the same VM tier.
04
Block layout permutation
Unique to AkiProtect
After encryption, AkiProtect reorders the payload blocks via an Ulam-spiral permutation and binds groups of blocks with SHA-256 integrity hashes. Modifying a single byte of the packed file invalidates a group hash and the runtime silently refuses to load. None of the other three protectors in this comparison ship this technique. It directly defeats the classical dump-patch-repack workflow.
Industry parity
All four protectors map the payload PE manually in memory after unpacking, instead of letting the OS loader see it. That's table stakes for a modern protector. Where they differ is which PE features the manual mapper supports: TLS callbacks, structured exception handling, SAFESEH, CFG, load-config. AkiProtect's loader supports all of them and is validated by a 90+ entry test corpus shipped with the source.
AkiProtect goes deeper
All four protectors run runtime anti-debug checks. AkiProtect ships six probes (IsDebuggerPresent, PEB NtGlobalFlag, Dr0–Dr3 hardware breakpoint scan, RDTSC timing, exception filter trick, NtSetInformationThread thread hiding) — and every single one is individually togglable. If one probe trips a false positive on a customer's machine (a profiler your QA uses, say), you switch off that one without weakening the other five. Competitors tend to bundle the probes into a single on/off setting.
07
Anti-tamper (self-checksum)
Industry parity
All four protectors hash their own runtime code at startup and refuse to run if it was modified on disk. AkiProtect pairs FNV-1a with SHA-256 across the .text section. Behaviour is identical across vendors: tampered binary exits silently with no diagnostic. Pure parity here.
08
Anti-dump (header wipe)
Industry parity
After the loader maps the payload into memory, all four protectors wipe the most useful PE structures (DOS header, NT headers, section table) from the mapped image. A process dump captured later is no longer a directly-loadable executable. Implementations differ in detail; the end-user effect is the same. Parity.
Industry parity
All four protectors XOR-encode string literals at build time and decode them at runtime. AkiProtect's stealth stub uses a constexpr XOR seeded with __DATE__/__TIME__ plus __COUNTER__ so every build has a different mask. Themida and VMProtect have similar mechanisms. Parity in result.
AkiProtect goes deeper
AkiProtect's stealth stub has no static import directory at all — every Win32 API is resolved at runtime by walking the PEB loader list directly. Themida and VMProtect obfuscate imports but typically still leave a handful of kernel32 entries visible in the table. Enigma generally leaves the import table intact. A reverse engineer reads the import table first to predict what your binary will do; with AkiProtect there is nothing there to read.
11
ARM64 (PE32+ ARM64) support
AkiProtect goes deeper
AkiProtect ships ARM64 as a first-class target alongside x86 and x64 — the same source tree, the same protection options, the same runtime stub. Windows-on-ARM is now standard on new Surface, Snapdragon laptops, and several enterprise SKUs; if you ship there, your protector has to follow. VMProtect and Enigma do not currently ship ARM64; Themida added it only in recent versions and as an extra-cost option.
Industry parity
All four protectors ship a command-line builder for CI pipelines. AkiProtect's CLI is the same binary that the GUI invokes in-process — so a CI build produces byte-identical output to a desktop build from the same project file. The audit log and JSON report are the same on both sides. Parity in availability; the GUI/CLI binary identity is the small AkiProtect win.
13
Per-developer perpetual license
Industry parity
All four protectors sell per-developer licenses with the right to use the purchased version forever. AkiProtect's tiers (Personal, Professional, Business) all include 12 months of updates plus a perpetual license to the version you bought. Differences across vendors are in price tiers and bundled support, not the licensing model itself. Parity.