Open-source apps for heads of IT, operated for you by Pilae

Your team decides what runs and when it changes. Pilae does the patching, the backups, the monitoring and the incident response, and puts every commitment in the contract.

Start with one workloadBook a 30-minute briefing

Your role
Decide what runs, approve each change
Our role
Operate, patch, back up, monitor, answer alerts
Availability
99.5% on Business, 99.9% on Enterprise, with service credits
Where
On premises, Pilae Cloud, hybrid or air-gapped

The questions a head of IT asks first

Moving a service off a SaaS vendor is a decision you will answer for. These are the questions we hear in the first meeting, and how Pilae answers each one.

Who watches the estate at night?

Probes check every app every 60 seconds, and alerts reach Pilae engineers around the clock. Response follows your plan: support hours on Starter and Business, around the clock on Enterprise.

Who keeps the apps up to date?

The Pilae Agent reads each upstream release, writes a plan with a backup and a rollback, and waits for your approval before it applies anything.

Can we restore when it matters?

Daily encrypted offsite backups in the country you choose, and a restore test every month with the result recorded in the console.

Does it fit our identity setup?

Apps sign in through your identity provider. Business and Enterprise plans include single sign-on for every app that supports it, with any vendor licence it needs named in the proposal.

Where does it run?

On your own servers, on dedicated machines in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU, or both. Air-gapped sites are covered on Enterprise.

What if we want to leave?

The apps are open source or source-available, your data stays in open formats, and every plan includes a written exit plan.

Control without a platform team

Self-hosting gives you control over where data lives, what it costs and when it changes. It also gives you a queue of release notes, certificates, backups and alerts that somebody has to handle every week. For most IT departments that somebody does not exist, which is why the SaaS contract won in the first place.

Pilae takes the queue. The Pilae Agent plans each update and waits for your approval. Monitoring probes every app every 60 seconds, and alerts reach our engineers around the clock. Backups run daily and are tested every month. Your team keeps the decisions: which apps run, where, and when they change.

One contract instead of many

Each SaaS service brings its own contract, its own renewal date and its own terms. With Pilae, the apps you run sit under one agreement with one SLA, one data processing agreement and one written exit plan. Adding an app is a change to the contract, not a new procurement.

When you are ready to look at costs, pricing explains how plans are put together, and managed operations sets out what our engineers do day to day.

Where to start

Most heads of IT start with one service that costs too much or holds data they would rather keep close: file sharing, chat, the service desk on Zammad, code hosting on Forgejo or GitLab, automation or an AI assistant. The leaving SaaS page shows how a first move runs, and onboarding explains what the fixed price covers.

What changes for your team

Your engineers stop doing the repetitive operations work and keep the decisions.

  1. Choose the apps

    Pick from the catalogue, or ask for an app it does not list yet. We assess it and tell you what running it involves.

  2. Onboard at a fixed price

    We install the apps, connect your identity provider, set up backups and monitoring, and migrate your data from the service you are leaving.

  3. Approve, do not operate

    Updates, fixes and migrations arrive as plans. Your team approves them from the console, by email or in chat, or writes rules that approve routine ones.

  4. Review in one place

    Apps, machines, deployments, backups and the audit trail sit in one console. You see what changed, who approved it and whether it worked.

What you get in writing

Availability
Monthly availability commitment with service credits, 99.5% on Business and 99.9% on Enterprise, as set out in the SLA.
Maintenance windows
Agreed per app. Emergency security changes are proposed for approval, never forced.
Backups and restores
Daily encrypted offsite backups in your chosen country, and a monthly restore test recorded in the console.
Support
Response times per plan. Business adds priority support; Enterprise adds around-the-clock incident response and a named engineer.
Exit
A written exit plan in every contract: your data back in open formats, and a documented handover to your team or another provider.

The apps behind it

Nextcloud

Files, calendars and shared documents for the whole organisation, on storage you can point at in a room you control.

Replaces Google Drive, Dropbox, SharePoint

Keycloak

Single sign-on for everything else you run, with your own directory as the source of truth and no per-seat bill between you and it.

Replaces Okta, Microsoft Entra ID

Mattermost

Team chat, channels and calls on a server in the country you choose, with the message history stored in your own database.

Replaces Slack, Microsoft Teams

Zammad

Helpdesk and ticketing across email, web forms, chat and messaging, run on your own hardware or in Switzerland and the EU, with every customer conversation in your own database.

Replaces Zendesk, Freshdesk, OTRS

Forgejo

Git hosting, code review, issues, packages and CI in one service, run in Switzerland, the EU or your own datacentre, with CI runners on machines of their own.

Replaces GitHub, GitLab.com, Bitbucket

GitLab

Git repositories, merge requests, CI/CD pipelines and registries in one application, run on your own hardware or in regions you choose, with runners on machines you place.

Replaces GitHub Enterprise Cloud, GitLab.com, Azure DevOps

Passbolt

A team password manager built on OpenPGP, where every shared credential is encrypted for each person who may read it, run in Switzerland, the EU or your own datacentre.

Replaces 1Password Business, LastPass, Keeper

n8n

Workflow automation your own team writes, running next to the systems it talks to instead of reaching them across the internet.

Replaces Zapier, Make

Open WebUI

A chat interface over models you host, so prompts and the documents people paste into them never leave your network.

Replaces ChatGPT Team, Microsoft Copilot

Questions

Do we need to hire people to run open-source apps with Pilae?

No. Pilae operates the apps: updates, security fixes, backups, monitoring and incident response. Your team approves changes and decides what runs. The time your engineers spent on routine operations goes back to projects.

Can our own engineers still work on the machines?

Yes, if you want them to. On premises the machines are yours, and access is agreed in the contract. Every session, theirs and ours, is recorded in the same audit trail.

What does it cost?

Starter and Business have public monthly prices on the pricing page, and Enterprise is quoted. Onboarding is fixed in writing before you commit.

How long does a move off a SaaS service take?

It depends on the service and the volume of data. We give you a migration plan with dates during onboarding, run the new app alongside the old one, and switch over when your team is ready.

What happens if Pilae stops operating our apps?

The exit plan in your contract sets out the handover. The apps are open source or source-available, your data is in open formats, and your team or another provider can run them from where we left off.

Related

Bring your list of SaaS contracts.

Thirty minutes with an engineer: we go through the services you pay for, say which ones an open-source app can replace, and what running it with Pilae involves.