One console instead of a dozen tools
Running self-hosted apps yourself usually means a server list in a spreadsheet, credentials in a wiki and backups nobody has checked. The Pilae console replaces all three. It shows every app you run, where it runs, what version it is on, when it was last backed up and what changed last.
The console works the same for apps on your premises, in Pilae Cloud or across both. One screen, one set of roles, one audit trail.
Approvals where your team already works
The Pilae Agent writes a plan for every update, migration and fix. The plan lands in the console, with the backup it will take and the rollback. The approver reads it and decides. Approvals also work by email and in chat, and each one is recorded against the person who gave it.
Access control your security team can sign off
Staff sign in through your identity provider, Keycloak or Microsoft Entra ID. Our identity service sets up the connection during onboarding. Roles decide who can see and approve what. When someone leaves, disabling their account in your directory removes their access to the console.
Every login, approval and change is written to the audit trail. Your auditors can read it in the console or receive it in your SIEM. The security page lists the controls behind it, and the shared responsibility model sets out who does what.
Backups and health, in plain sight
Each app shows its last backup, where it is stored and the result of its monthly restore test. Monitoring feeds probe results and machine metrics into the same screen. Our backup page covers the schedule and retention, and your contract sets the recovery objectives. To see the console on your own stack, book a scoping call.