• 01Self-protected release
  • 02SHA-256 published
  • 03Tested protection matrix
§ 01 — Windows x64 · .NET 9

Make your .NET application expensive to reverse.

ILVeil layers VM-based method protection, managed IL obfuscation, runtime guards and release verification into one desktop workflow. Application Guard optionally binds licensed features to derived values, execution flow and encrypted resources — not one boolean.

ILVeil protection plan screen showing input selection, protection profile and output settings
Fig. 01 Protection plan — input, profile and effective layers stay visible together.
READY-MADE DLL / EXEPROJECT / SOLUTIONNATIVE AOT AWAREGUI-DRIVEN WORKFLOW
§ 02 — How input becomes output

Five stages between your assembly and the release you ship.

01ORIGINAL IL

Unmodified assembly, or a freshly published project.

02OBFUSCATION

Symbols renamed, strings encrypted, control flow reshaped.

03METHOD VM

Selected methods become custom bytecode behind protected dispatch.

04RUNTIME GUARDS

Anti-debug and integrity checks watch startup and chosen paths.

05VERIFIED OUTPUT

Post-protection checks confirm the build still runs.

§ 03 — Four protection layers

More than renamed symbols.

Use the layers that match your application. Unsupported methods fall back safely instead of being transformed blindly.

01
3AVM7F

VM-based method protection

Selected methods become custom bytecode interpreted through protected dispatch, with per-method mappings and hardened call targets.

  • Branching, switches and recursion
  • Instance fields and call targets
  • Void, value and reference returns
02

Managed IL protection

String encryption, symbol renaming, control-flow transforms and integer masking work as coordinated layers, not one trick.

03

Runtime resistance

Anti-debug and integrity checks can guard startup and selected execution paths, each with an explicit response policy.

04

Post-protection verification

Checks, application records and logs confirm the release still runs — not just that it was transformed.

§ 04 — Two ways to use ILVeil

Protect a binary. Or bind a feature to it.

DEFAULT · NO SOURCE CHANGES

Binary Protection

  • Ready-made DLL / EXE as input
  • No source integration required
  • VM, string encryption, rename, control-flow transforms and runtime guards apply directly
OPTIONAL · SOURCE INTEGRATION

Application Guard SDK

  • Signed capability leases
  • Derived values and flow checkpoints
  • Encrypted embedded resources unlocked by valid flow state

Guard does not scan or understand your business logic automatically. You choose what values, checkpoints and resources a signed capability can unlock. Starter SDK and License Issuer are bundled — see what's included.

§ 05 — Evidence, not slogans

Protected output is tested as software.

12/12calculator protection variants
73/73real UI behavior checks
18/18window and layout states
0build warnings and errors
this release protects itself with ILVeil before publishing
§ 07 — Honest limitation

No client-side protector makes your code impossible to reverse. ILVeil is designed to multiply analysis cost, remove easy bypass points, and preserve application behavior across every layer.

§ 08 — Current release · v2.1.0

Raise the cost of the next bypass.

Self-protected Windows x64 build. Requires the .NET 9 Desktop Runtime.