Quick start

This is the shortest path from a readable PHP file to protected code running on a server. Leave every protection option off for this first run; you can add them later.

1. Get your Encoder Token

Sign up at the Oxrion Console and press Generate token. Copy the token (it starts with oxe_) or download it — it is shown only once.

A Free account is enough to follow along: it protects up to 20 files a month. Files protected on Free run for 30 days. See Plans, quota & credits.

2. Protect a file

Pick one:

• In your browser — open the Web Encoder, paste your token, drop a .php file and press Protect. The protected file downloads as a .zip. Nothing to install; see Web Encoder. Then skip to step 3.
• In Oxrion Desktop — download it from oxrion.com/download, open it and follow the steps below. See Install Oxrion Desktop for details. You’ll want Desktop later anyway to issue licenses and recover source.

In Oxrion Desktop

1. Open Encoder in the sidebar.
2. Paste your token into Encoder Token. (Later you can save it in the Vault so you don’t have to paste it again.)
3. Under What do you want to protect?, choose PHP file / ZIP and pick a .php file.
4. Under Output folder, choose where the protected copy should go. It must be outside the folder you are protecting.
5. Press Protect.

Oxrion first checks your token and quota, then protects the file. When it finishes you see Protection complete and the protected file is in your output folder.

3. Install the Loader where the code will run

Protected files need the free Oxrion Loader on the server that runs them. On that machine:

curl -fsSL https://get-loader.oxrion.com | sh      # Linux

irm https://get-loader.oxrion.com/win | iex        # Windows

Then run oxrion-loader install and restart your web server. See Install the Loader for the full guide.

4. Run it

Copy the protected file to that server (from the Web Encoder, unzip it first) and load it — open it in the browser, or run it with php. It runs exactly like the original.

That’s the whole product: code nobody can read, running with a free extension.

Now make it real

Each of these is an option you turn on when you protect. See Protection options for all of them.

• Bind it to a license — so it runs only on a customer’s host, until a date you choose.
• Lock it to a server with Server lock — so it runs only where your external key is present.
• Keep a way back — so you can always restore your source.