FAQ
Can anyone read my code after it’s protected?
Section titled “Can anyone read my code after it’s protected?”No. Protected files are encrypted and signed; they only run through the Oxrion Loader, which refuses any file that was changed.
Does Oxrion keep a copy of my source?
Section titled “Does Oxrion keep a copy of my source?”No. The .php files you select are sent to the Encoder, protected and sent back. Your source is not stored. Everything else in your project never leaves your computer — in Oxrion Desktop or in the Web Encoder. See Data & privacy.
Do I have to install anything to protect code?
Section titled “Do I have to install anything to protect code?”No. The Web Encoder at encoder.oxrion.com protects PHP in your browser with the same Encoder Token, options and quota as Oxrion Desktop. Install Oxrion Desktop when you also issue licenses, recover source or keep your keys in a Vault — those work offline.
Which PHP versions are supported?
Section titled “Which PHP versions are supported?”PHP 8.1–8.5, 64-bit, on Linux and Windows. You protect once; the same protected files run on every supported version, so customers can upgrade PHP without new files.
Do I need to be online?
Section titled “Do I need to be online?”Only to protect code. Issuing licenses, recovering source and the Vault work offline. Emailing licenses and sending webhooks use the internet, too.
What does the Free plan include?
Section titled “What does the Free plan include?”20 files a month, Recovery and Stamp system notes. Free files run for 30 days and carry a TRIAL note. Server lock, License, Expiry and Stamp custom notes need a paid plan or credits. See Plans, quota & credits.
What’s the difference between quota and credits?
Section titled “What’s the difference between quota and credits?”Quota comes with your plan and renews every month; protecting a file you already protected (with the same content) doesn’t use it again. Credits are bought separately, never expire, and every protection uses one. See Plans, quota & credits.
How do I sell my code with licenses?
Section titled “How do I sell my code with licenses?”Protect it once with the License option, then issue a license for each customer’s host in the Licenser. Send the customer the protected files and their .lic file, which goes in the root folder of the project. See Licenses.
My customer uses both example.com and www.example.com. Do they need two licenses?
Section titled “My customer uses both example.com and www.example.com. Do they need two licenses?”Yes. They are different hosts, so issue a license for each. Both .lic files can sit side by side in the project root.
How do I renew a customer’s license?
Section titled “How do I renew a customer’s license?”Issue a new license for the same host with a later expiry, and have the customer replace the old file. You don’t need to protect the code again. See Licenses.
Can I run protected code from the command line or cron?
Section titled “Can I run protected code from the command line or cron?”Yes — unless it needs a license. Licenses are checked against the host of a web request, so code protected with the License option doesn’t run from the command line.
What happens if I lose a private key?
Section titled “What happens if I lose a private key?”You can’t issue new licenses for files protected with the matching license public key, or recover files protected with the matching recovery public key. Keep a backup of your Vault.
Web Encoder, Desktop or CLI?
Section titled “Web Encoder, Desktop or CLI?”The Web Encoder protects code in the browser and nothing else. Oxrion Desktop does everything, including protecting code, License History and Email & Hooks. The CLI issues licenses and recovers source from a terminal — handy for automation, and it can run fully air-gapped.