IMAVELABIN COMPILATOR

BUILD. LICENSE. SHIP.

All your app.
One EXE.

Publish your .NET Windows app as one self-contained executable. Add licensing inside your application, protect your code with optional obfuscation, and sell through your IMAVELA CRM.

Windows x64 · Command line · Five computers per license

BIN COMPILATOR · EXAMPLE WORKFLOW
Crm.BinCompilator.exe
  --project MyApp.csproj
  --output C:\releases\MyApp
  --entry MyApp.exe
  --dotnet dotnet
THE STRICT OUTPUT CONTRACTMyApp.exe

One executable. No loose DLLs.
No second EXE. No content folder.

Publish from your project with the official .NET SDK.

BUILT FOR THE LAST MILE

Make delivery
more predictable.

01

A self-contained Windows app.

Bundle the runtime and supported dependencies with your application, so your users receive one executable.

02

A strict output check.

Reject loose DLLs, extra executables and unexpected folders before the release replaces your previous output.

03

Sign with your certificate.

Optionally apply Authenticode signing and timestamping with your own signing certificate and Windows SignTool.

04

Licensing, built in.

Insert a startup activation check automatically, or integrate the SDK DLL for your own activation screens and premium features.

05

Make code harder to inspect.

Optionally obfuscate private symbols and strings with Obfuscar before bundling. Keep a checksum and release report for each delivery.

06

Protect the previous release.

Build in an isolated staging folder. Validation must pass before your destination is replaced.

SMALL PRICE. USEFUL EVERY RELEASE.

One license.
Five computers.

Choose monthly flexibility or save 10% with annual billing.

MONTHLY

Keep it flexible.

4.90 USD / month

Billed monthly. Taxes are additional.

  • Five activated Windows computers
  • Strict single-EXE publishing
  • Embedded or automatic licensing
  • Optional obfuscation and signing
  • Manual software update checks

Internet access is required for activation and each compilation. Your published applications do not require a Bin Compilator subscription to run. Selling and managing their licenses requires your own IMAVELA CRM subscription.

READY WHEN YOU ARE

Download. Activate. Publish.

Download the portable Windows x64 executable, then run the activation command. Approve the computer from your IMAVELA account or ask your license administrator to approve its code.

Download Bin Compilator

Windows x64, a supported .NET project and the .NET SDK are required. Signing also requires your own certificate and SignTool.

1 / ACTIVATE THIS COMPUTERCrm.BinCompilator.exe --activate2 / SEE YOUR LICENSECrm.BinCompilator.exe --license-status3 / EXPLORE THE COMMANDSCrm.BinCompilator.exe --help

YOUR SOFTWARE. YOUR CUSTOMER EXPERIENCE.

Two ways in.
One licensing service.

Manage products, sales, subscriptions and activated computers in your CRM. Choose the integration that fits your application.

01 / AUTOMATIC

Add activation at build time.

Publish a supported C# .NET 8+ Windows project with your CRM portal and product ID. The compiler inserts the check inside your app, before it starts.

--license-portal https://your-website.com
--license-product app-your-software

A built-in approval dialog and startup verification. No separate launcher.

02 / EMBEDDED SDK

Make it part of your interface.

Reference Imavela.Licensing.dll to build your own activation screen, check paid features and revalidate access during long-running sessions.

await licensing.RequireActiveAsync("export");

Windows .NET 8+, encrypted local credentials, and live entitlement checks.

The SDK integration guide is included. Your CRM subscription and payment-provider fees are separate. Obfuscation helps discourage analysis; it does not make software impossible to modify.

BEFORE YOU BUILD

A few useful details.

Is this a code protection tool?

Use --obfuscate for optional Obfuscar protection of private symbols and strings. This is separate from single-file packaging and Authenticode signing. Test reflection, serialization and UI bindings after obfuscation. No local protection can guarantee that software cannot be inspected or modified.

Can I package any Windows executable?

The tool publishes supported .NET projects using the official SDK. It needs your project and build dependencies; it is not a generic wrapper for arbitrary executables.

What happens when I change computers?

Your license administrator can revoke an old computer from Software Licenses to free a slot. Run --activate on the replacement and approve it. You can also run --deactivate on a computer you are retiring.

Does it update itself automatically?

Run --check-update to look for a new version and --download-update to download and verify it. Updates are never silently launched.

Do my customers need a license?

Your customers do not need a Bin Compilator subscription. If you add application licensing, they activate a license for your product in your CRM. You manage its sale, renewal, computer allowance and revocation. Your application and dependency licenses still apply.