Private by default, not by configuration
Most self-hosting incidents start with an app exposed to the internet that nobody meant to expose. With Pilae, every app answers only on Pilaeās private mesh. Your staff reach it through the mesh or through one hardened gate on port 443. A new app is private until you decide otherwise.
The same controls apply on your premises and in Pilae Cloud. Your security team reviews one design, not two.
Patching that follows the advisories
Open-source projects publish security fixes in the open. The Pilae Agent tracks those advisories for every app and version you run. It plans the fix, takes a verified backup and waits for your approval. You see what changes, when, and how it rolls back.
Evidence for your auditors
Every access, approval and change is written to the audit log in the console. Your auditors get a record of who did what and when. Pilae is built to ISO/IEC 27001 controls, and Pilae Cloud is hosted in ISO 27001-certified datacentres. The measures annex of our data processing agreement lists each control. For how we meet the Swiss data protection act, see nLPD compliance.
Responsible disclosure
If you find a vulnerability in a Pilae service, write to security@pilae.com. We acknowledge every report and tell you what we fix and when. Please give us reasonable time to fix it before you publish.