Code virtualization · anti-tamper · embedded SDK

Ship binaries attackerscan't crack.

Merisar virtualizes selected functions in your Windows binary into a custom VM, seals them with a keyed cross-function integrity mesh, and ships you an SDK so your code calls the same protections directly. Protect in CI, pay per build.

Start free View docs

Windows x64 PE · GCC/MinGW & MSVC supported · no runtime JIT · interpreter-only VM

# in your source:

# SVP_VIRTUALIZE(check_license);

$ gcc -c app.c # your normal build

$ svp build app.exe --profile=hard # one call to the service

→ virtualized: 6/6 functions

→ integrity mesh: k=3, 4 peers

→ bytecode encrypted at rest ✓

app.protected.exe ready

Protection you can measure, not hope for.

Every build is seeded, every integrity check is keyed, every tampered function is detected by its peers. No obscurity — actual mechanisms.

Register-based VM

Marked functions are lifted to a 3-address IR and lowered to our bytecode ISA. Per-build opcode permutation. Decode-on-fetch keystream so stored bytecode isn't plaintext at rest.

k-peer integrity mesh

Each virtualized function keyed-MACs several peers (SipHash). Tamper one and the others silently corrupt their results — no single-function cut, no greppable 'if (patched)' branch.

Embedded SDK

Mark functions in source with SVP_VIRTUALIZE(), call svp_poison(), svp_verify(), and friends directly from your code. Composable with the VM.

Three steps, drops into any CI.

Annotate

Add the SDK and mark functions you want protected: SVP_VIRTUALIZE(check_license);

Compile

Build your binary as usual. Our markers go in a .svpmark section.

Protect

POST the binary + a profile to our build API. Download a hardened binary and keep going.

Keep your IP out of someone else's decompiler.

Pay per build, scale from a hobby project to a shipped product. Free tier to try it; sign up and your first build is ready in minutes.

Create account See pricing