Skip to content
AtlasDocs
Sign inGet started
Updated Oct 16, 2026

Use it with Atlas Auth

Protect the program with the Obfuscator and sign its customers in with Atlas Auth. Two things to do in the right order.

Open it now:Obfuscator, ProtectSettings, Builds

Order of work

  1. Build your program with the Atlas SDK as usual (Install and first sign-in).
  2. Run the finished file through the Obfuscator.
  3. Authorize the protected file, not the original, under Settings, Builds. Its hash is different, and only authorized hashes can sign in.
  4. Ship the protected file.

Running-build proof

A program the Obfuscator rewrites when it starts does not match its file, so Atlas cannot compare its running code with the file you uploaded. Keep the running-build proof of such an application on Log only or Off. The hash check still applies.

Why both

Atlas Auth decides who may run your program and ends sessions that misbehave. The Obfuscator makes it hard to change the program so that it skips that decision. Neither is complete alone; What Atlas checks, and when explains what the SDK itself does.

Was this page useful?