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

Protect selected .NET methods and assemblies before you ship them.

ILVeil layers managed VM protection, generated native runtime variants, IL obfuscation, runtime guards and release verification into one desktop workflow. Application Guard can bind licensed features to derived values, execution checkpoints and encrypted resources for software that needs more than a single feature flag.

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

Choose the protection layers your build needs.

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

01
3A→VM→7F

VM-based method protection

Selected methods become custom bytecode behind protected dispatch. High-value static methods can also use a generated native runtime variant with deployment-bound key material.

  • 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 — Test results from this build

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
11/11Native VM Runtime Variant smoke scenarios
§ 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.2.0

Start with the code you need to keep harder to inspect.

ILVeil is intended for Windows .NET software vendors protecting licensing logic, proprietary algorithms, desktop applications, game clients and Native AOT releases. Requires the .NET 9 Desktop Runtime.