Access: public & private
Access is the first choice in the Configuration panel, and the most important one. It decides what a server needs in order to run your protected file.
Public
Section titled “Public”A public file runs on any server that has the Loader installed. Nothing else is required.
Choose Public when you want your code protected from reading and copying, and you’re comfortable with it running anywhere the Loader is present. It’s the simplest option — install the Loader, and the file runs.
Private
Section titled “Private”A private file requires an external key on the server, in addition to the Loader. The Loader by itself is not enough: without the matching key in place, the file will not run.
This gives you a stronger guarantee. Even if someone obtains your protected file and installs the Loader, they still can’t run it without the external key — which you control and place only on the servers you authorize.
Choose Private when you want tight control over exactly which servers can run your code.
Choosing the external key
Section titled “Choosing the external key”When you select Private, you also choose which external key the file should require. You can:
- Pick one of your saved external keys, or
- Paste a 32-character (hex) key directly.
That same key must then be present on the destination server, supplied through an environment variable or php.ini. Setting it up on the server is covered in External keys on a server, and you manage your keys on the Keys page.
At a glance
Section titled “At a glance”| Public | Private | |
|---|---|---|
| Needs the Loader | Yes | Yes |
| Needs an external key on the server | No | Yes |
| Best for | Code that can run anywhere | Code restricted to specific servers |
Private mode is available on paid plans — see Plans & limits.