Security for self-hosted open-source apps, run by Pilae

Your apps answer only on a private network, run on hardened machines, receive security fixes on a schedule you agree, and every access and change is recorded.

Talk to our teamRequest the security pack

Network
Private mesh, one hardened gate on port 443
Access
Named engineers, least privilege, every session logged
Encryption
TLS in transit, encrypted disks and backups at rest
Framework
Built to ISO 27001 controls

Security controls in every Pilae deployment

The controls below are part of the platform, not an add-on. They apply on your premises and in Pilae Cloud alike.

Private networking

Apps answer only on the Pilae private mesh. The public internet reaches one hardened gate on port 443, and nothing else.

Hardened machines

Minimal operating system, closed ports, key-only SSH, host firewall and automatic security updates for the base system.

Named, least-privilege access

Each Pilae engineer has a personal account with only the rights their task needs. There are no shared logins.

Vulnerability management

Upstream security advisories for every app you run are tracked against your versions, and a fix is planned as soon as it is published.

Patch windows

Security fixes are applied in the maintenance window you agree. Critical fixes are proposed at once, never forced.

Audit log

Every login, approval, command and configuration change is recorded in the console and exportable to your SIEM.

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.

How a security fix reaches your apps

  1. Advisory published

    An upstream project publishes a security advisory or a patched release.

  2. Matched to your estate

    The Pilae Agent checks which of your apps and versions it affects.

  3. Planned and approved

    A plan with a backup and a rollback goes to you. You approve it, or a rule you set does.

  4. Applied and recorded

    The fix is applied in your window, probes confirm the app answers, and the run is written to the audit log.

What your contract includes

Security fixes
Critical fixes planned and sent for approval as soon as the upstream fix is released. Response times per plan.
Access
Named engineers only. The list of people with access to your environment is available on request.
Audit log
Retained for the length of the contract and exported on request.
Incident notification
You are notified of any security incident affecting your data without undue delay, as your data processing agreement specifies.
Security review
Your security questionnaire answered before you sign, with the evidence behind each control.

Questions

Is Pilae ISO 27001 certified?

No. Pilae is built to ISO 27001 controls, and Pilae Cloud is hosted in ISO 27001-certified datacentres. Your security review receives the list of controls and the evidence behind each one.

Can the public internet reach my apps?

No. Apps answer only on the private mesh. The only public entry point is one hardened gate on port 443, and you decide which apps it exposes, if any.

Who at Pilae can access my environment?

Only named engineers assigned to your account, each with a personal account and the minimum rights for the task. Every session and command is recorded in the audit log you can read.

How fast are security fixes applied?

Advisories are tracked for every app you run. A critical fix is planned and sent for approval as soon as the upstream release exists. It is applied in your agreed window, or at once if you approve an emergency change.

How do I report a vulnerability?

Write to security@pilae.com. We acknowledge every report, keep you informed while we fix it, and credit you if you wish.

Related

Send us your security questionnaire.

An engineer answers it with the controls in place and the evidence behind each one.