How Oxrion works

This is the whole journey, start to finish. Read it once and everything else in these docs will have a place to fit. Three steps: subscribe, protect, run.

Step 1 — Subscribe (once)

Go to app.oxrion.com, create an account, and pick a plan. You’ll get one thing that matters: an Encoder Key.

Think of the Encoder Key as the key that powers the tool that protects your code. It carries your plan’s daily limit, and it’s the only thing you’ll paste into the app. Keep it private.

You do this once. Everything after this happens on your own machine.

Step 2 — Protect (on your machine)

Open the Desktop app (or the CLI), paste your Encoder Key, and point it at a PHP file, a folder, or a whole project ZIP.

When you protect a file, you also decide how it should behave in the wild — this is the part that makes Oxrion more than an obfuscator:

• Should it run anywhere, or only on one customer’s domain? → turn on a License.
• Should it run only on one specific server? → lock it with an External Key.
• Do you want to be able to get your source back later? → turn on Recovery.

You press protect. Your code is sent over an encrypted connection, protected in memory, and the result comes straight back. Your source is never stored. What you get is a protected copy with your folder structure intact.

This is the core loop. Ninety percent of using Oxrion is: point the Encoder at code, choose how it’s locked, protect.

Step 3 — Run (on any server)

Copy the protected files to wherever they need to live — your customer’s server, your VPS, a hosting account. That server needs one free thing installed: the Oxrion Loader, a small PHP extension.

Once the loader is there, protected files just run — normal PHP behavior, full speed. If you set a license or a server lock, the loader checks it before running. If someone tampered with a file, the loader refuses it.

Your customer installs the loader once and never thinks about Oxrion again.

That’s the product

You do this	With	Where
Protect your code	Encoder	Your machine (online, uses your plan)
License it to a customer	Licenser	Your machine (offline)
Lock it to a server	Keys	Your machine (offline)
Keep the power to restore it	Recovery	Your machine (offline)
Run the protected code	Loader	The server (free, offline)

Now do it for real:

Quick start — protect your first file →