Windows desktop application
Enterprise-style .NET protection from a desktop workflow people can actually operate.
ILVeil combines managed protection, Native AOT publishing, activation management, and release-facing diagnostics in a calmer desktop experience for teams shipping compiled .NET applications on Windows.
Custom IL protection, preservation controls, and release-safe operator flow.
Native AOT, trim, strip, and packaging decisions coordinated from one desktop surface.
Activation, edition handling, protected builds, and stack-trace support stay visible.
Capabilities
Structured around release operations, not just around one obfuscation switch.
ILVeil is positioned as a desktop .NET obfuscator and .NET protection product, but the actual value is broader: protection, publish flow, licensing, and supportability are handled in a single workflow.
Managed protection
Protect compiled .NET assemblies with a custom IL layer, string protection, preservation logic, and rename-map output.
Native AOT publishing
Coordinate release builds with Native AOT, trim, and strip options from the same desktop application.
Activation management
Use a built-in activation surface for Free, Pro, and signed commercial license flows.
Protected builds tracking
Keep release outputs, launch targets, and protected application records visible after the build completes.
Support-oriented outputs
Preserve stack-trace deobfuscation support and release diagnostics needed for post-ship issue handling.
Desktop-first experience
Designed for operators who want a GUI-driven process instead of putting every protection step behind a terminal flow.
Why this layout exists
A calmer product face for a security-heavy tool.
The public site is intentionally softer than the product category usually is. Instead of a loud “security dark theme,” the page now leans into a light corporate palette, clearer content rhythm, and calmer decision points.
Cleaner grid, softer contrast, clearer hierarchy, and less “hacker tooling” mood.
Shorter hero copy, calmer cards, and more whitespace around product claims.
The page frames ILVeil as a release workflow, not just as an obfuscation checkbox list.
Workflow
One practical release sequence.
Select the target
Choose a project, solution, DLL, EXE, or frontend build and keep release context visible from the start.
Apply protection policy
Set managed protection options, preservation rules, Native AOT targets, and packaging decisions.
Publish and validate
Run the build pipeline, inspect logs, and keep post-protection visibility through records and audits.
Ship with supportability
Use edition policy, activation, and deobfuscation support as part of the production handoff.
Screenshots
Desktop views from the product itself.
Editions
Public-facing edition structure that reads clearly.
Free
Good for evaluation and smaller protected outputs
Includes the desktop workflow, managed protection baseline, Native AOT path, and the public release experience.
- Desktop protection workflow
- Managed protection baseline
- Native AOT publish support
- Up to 3 logical user-managed assemblies per run
Pro
Commercial desktop usage with fewer operational limits
For paid usage, Pro removes the Free managed assembly cap and supports normal commercial release workflows.
- Signed product-license flow
- Commercial release usage
- No Free assembly cap
- Evaluation and licensing by request
Enterprise
Reserved for organization-level onboarding
Use this path for larger teams that want direct licensing discussion, rollout planning, or broader terms.
- Team onboarding discussion
- Commercial coordination
- Direct contact workflow
- Handled through support email
FAQ
Public distribution model.
Is the source code public?
No. This repository is only the public release site and release package host. The source repository remains private.
Is this a CLI package?
No. ILVeil is presented here as a Windows desktop GUI application. Public delivery is through GitHub Releases and GitHub Pages.
Can GitHub Pages look corporate?
Yes. GitHub Pages can host a polished static product site. The limitation is backend logic, not visual brand quality.