A breach becomes an IT incident, not a company-ending event. Encrypt the data, not the network. When an attacker gets in, the files they reach stay encrypted, because the keys are not on the systems that were breached. No key server to deploy, no appliance, no service in the middle.
| Edition | PolyLock™ Enterprise |
| File type | .ple |
| Feature set | Organization |
| Encryption domain | Its own. Files encrypted by this edition open in this edition |
| Platforms | iPhone, iPad, Mac, Android, Windows, Linux, BSD. On Android, the organization features follow later |
| Server required | No key server, no appliance, and no firewall ports to open |
| Deployment | Four steps, no server: seats from your app store, one signed organization bundle behind your own sign-in |
| Recovery | Declared recovery ways chosen by you. No administrative backdoor |
| Status | Coming October 2026 |
| Intellectual property | Patent pending |
Departments and the organization hold declared ways of their own on the company's files.
Offers, contracts and payroll sent ahead, encrypted until the moment they take effect.
Each supplier opens its own part of a project, and not the others'.
A misconfigured bucket or a lost laptop holds files that are still encrypted.
Sensitive files that also require a sign-in with the company's identity provider.
Four steps. PolyLock™ adds no server to your environment. Today this covers iPhone, iPad, Mac, Windows, Linux and BSD; the organization features on Android are still to come.
Through the store that already serves the device: Apple Business Manager for Apple devices, and our store for Windows, Linux and BSD. No license server.
One signed file: your policy, your organization’s ways in, your members. Signed by two of your own custodians, on your own machine. We do not see it.
Where your people already sign in: an intranet share, SharePoint, a page behind your identity provider.
From the store, or pushed by your device management. About two minutes per person.