How Torzen works

1. 1

   Upload a file

   In the panel you choose an EXE, DLL, Mach-O or ELF file. To protect functions by name, add a symbol file: PDB, dSYM or DWARF.

2. 2

   Choose what to protect

   Select functions and a protection level, or pick a saved profile. You can pass the same settings to the API as a JSON file.

3. 3

   Queued processing

   The file enters the queue. On the Pipeline and Foundry plan it uses the priority queue. You follow progress in the panel, or check the job status through the API.

4. 4

   Download the protected file

   You download the result from the panel or through the API. Uploaded files, symbols and results are deleted from the service after 7 days.

curl https://app.torzen.re/api/v1/protections \
  -H "Authorization: Bearer $TORZEN_TOKEN" \
  -F "file=@build/Release/app.exe" \
  -F "symbols=@build/Release/app.pdb" \
  -F "settings=@torzen.json"

curl https://app.torzen.re/api/v1/protections/prt_7Hq2Lx \
  -H "Authorization: Bearer $TORZEN_TOKEN"

{ "id": "prt_7Hq2Lx", "status": "done", "queue": "priority" }

curl -L https://app.torzen.re/api/v1/protections/prt_7Hq2Lx/file \
  -H "Authorization: Bearer $TORZEN_TOKEN" \
  -o dist/app.exe

{
  "functions": [
    {
      "name": "LicenseManager::validate",
      "level": "virtualization"
    },
    { "name": "net::*", "level": "mutation" }
  ],
  "strings": "encrypt",
  "integrityChecks": true
}

API documentation

Source languages: C, C++, Rust, Delphi.

Build

5 protections per day

Release

10 protections per day

Pipeline

30 protections per day

Foundry

50 protections per day

Compare plans