An Azure alternative for open-source apps, operated on your terms
Azure gives a Microsoft shop virtual machines, Kubernetes, managed databases and Azure OpenAI to build on. Pilae takes the open-source apps your teams adopted off that build list and runs them for you, on your own servers or in Zurich, the EU or further afield, and changes nothing you have not approved.
- Hyperscale cloud, tied to Microsoft 365 and Entra ID
Thirteen jobs, and who does them
| Group | Azure | Pilae |
|---|---|---|
| Deploy | ||
| Keep it current | ||
| Prove it | ||
| See it | ||
| Run it | ||
| In full | 1 of 13 | 13 of 13 |
| In part | 12 | 0 |
When Microsoft Azure fits, and when Pilae does
Azure still fits when
- Your organisation is built around Microsoft 365 and Entra ID, and your engineers already run workloads on Azure.
- You build and run your own software, and want managed services Pilae does not offer, such as serverless functions or large GPU capacity billed by the hour.
- Your workloads have to sit in more regions than the 10+ Pilae Cloud offers, or you need a Microsoft stack running on premises through Azure Local.
Level with Pilae on
- Logs and metrics exported to your stack
Pilae fits when
You want the twelve jobs Azure covers in part done in full, for every app you run, among them:
- Updates applied for you, not just announced
- Restore drills, not just backups
- Monitoring and alerting on the apps
What each one actually covers
Thirteen things an open-source estate needs done. Their column is filled in from azure.microsoft.com.
What each row means is set out once, on the comparison of every alternative.
- What they sell
- Virtual machines, AKS, Azure Database for PostgreSQL, Azure OpenAI and hundreds of other services, each billed per resource
- In Switzerland
- Switzerland North in Zurich for every customer; Switzerland West in Geneva reserved for in-country disaster recovery
- Their certifications
- ISO 27001, SOC 2, BSI C5 and others, listed in Microsoft's compliance documentation
- Their support
- Paid plans, sold separately from usage; under an hour for a critical case from the Standard plan up
- What we sell
- Keycloak, Nextcloud, n8n, Open WebUI and the rest of the catalogue, run by Pilae engineers
- Where ours runs
- Your own servers, Zurich, five EU regions or six more worldwide, hybrid or air-gapped
Show all thirteen rows, Azure beside Pilae
| Capability | Microsoft Azure | Pilae |
|---|---|---|
| Deploy | ||
| One-click deploy from a curated catalogue | Partly | Yes |
| Migration onto the platform, run for you | Partly | Yes |
| SSO and identity wired into each app | Partly | Yes |
| Keep it current | ||
| Updates applied for you, not just announced | Partly | Yes |
| Per-app CVE and advisory tracking | Partly | Yes |
| Changes land in a window you approved | Partly | Yes |
| Staged and checked before production | Partly | Yes |
Half a day with your stack, a written plan, and a fixed price. Plan a move from Azure | ||
| Prove it | ||
| Restore drills, not just backups | Partly | Yes |
| A record of every restore | Partly | Yes |
| A change log an auditor can read | Partly | Yes |
| See it | ||
| Monitoring and alerting on the apps | Partly | Yes |
| Logs and metrics exported to your stack | Yes | Yes |
| Run it | ||
| An agent that operates the estate with you | Partly | Yes |
Pilae vs Microsoft Azure, in words
A tick says whether something is covered. These say how.
Show the eight answers, side by side
| What is being compared | Microsoft Azure | Pilae |
|---|---|---|
| What you are buying | Building blocks on a Microsoft subscription. A self-hosted Nextcloud on Azure is a virtual machine or an AKS cluster, a managed database, blob storage and a load balancer, each priced and configured separately. | Nextcloud itself, running, with its database, storage, backups and updates looked after as one service on one monthly plan. |
| Who operates the app | Your team, or a Microsoft partner you hire. Under Azure's shared responsibility model the app, its configuration and its data stay with you on virtual machines and platform services alike. | Pilae engineers, from first deployment to the alert at three in the morning. You approve the changes; you do not carry the pager. |
| When an update lands | Managed services apply maintenance on Microsoft's schedule or in a maintenance configuration you set. Software you deploy on virtual machines updates when you update it. | The Pilae Agent reads the release, plans the upgrade for your setup, takes a backup first and applies it in your window once you approve. |
| Identity | Entra ID is a strong identity provider. Connecting each open-source app you self-host to it is yours to configure. | Each app wired to your directory, through Entra ID or Keycloak, as part of onboarding. Entra ID stays yours. |
| Proving a backup works | Azure Backup for virtual machines and point-in-time restore on Azure Database for PostgreSQL. Restoring the whole app and checking it runs is a job for your team. | Daily encrypted backups of the whole app, database and files together. Business adds point-in-time recovery for databases; Enterprise adds a monthly restore test recorded in the console. |
| Private AI | Azure OpenAI runs Microsoft-hosted models in the region you pick, under Microsoft's product terms. | Open WebUI in front of open models served by vLLM or Ollama on machines you choose, so prompts and documents stay inside your perimeter. |
| Running on your own servers | Azure Local runs on validated hardware in your building, with disconnected operations for sites that cannot reach Azure. | Whatever servers you already have, or an air-gapped site. Pilae runs the same platform there as in its own regions. |
| Jurisdiction | Microsoft is a US company. It has completed the EU Data Boundary and offers Microsoft Sovereign Cloud, including national partner clouds such as Bleu in France and Delos Cloud in Germany. | Pilae is a Swiss company, and your contract is under Swiss law. In Swiss and EU regions your machines are run by European datacentre operators, and every sub-processor is named in the DPA. |
Where Azure is the right answer
Microsoft Azure is the natural home for an organisation that already runs on Microsoft. Entra ID holds the accounts, Microsoft 365 holds the mail and documents, and Azure adds the infrastructure underneath with the same contract, the same partner and the same admin portal. For a team that builds its own .NET services, it is hard to beat.
The difficulty starts with the open-source apps. A Nextcloud, a GitLab or an n8n on Azure is not an Azure service. It is software your team installs on a virtual machine or an AKS cluster, connects to Entra ID, upgrades, backs up and watches. Microsoft runs the machine underneath; the app is yours. Pilae takes that part off your hands and leaves the rest of your Microsoft estate alone.
Two Swiss regions, one you can choose
Azure has two regions in Switzerland. Switzerland North, in Zurich, is open to every customer and has availability zones. Switzerland West, in Geneva, is access-restricted: Microsoft reserves it for Switzerland North customers that need disaster recovery inside the country, and you apply for it. A Swiss organisation that wants a second copy of its data in Switzerland on Azure starts with that request.
Pilae puts the second copy in the contract instead. Apps run in Zurich or on your own premises, and the daily backups go to a second site in the same jurisdiction, encrypted before they leave the machine.
The EU Data Boundary and the CLOUD Act
Microsoft has done more than most US providers on European data. The EU Data Boundary, completed in February 2025, keeps customer data for its core cloud services inside the EU and EFTA, and Microsoft Sovereign Cloud adds sovereign controls in its public cloud, Azure Local on premises, and partner-run national clouds such as Bleu and Delos Cloud.
None of that changes who owns Microsoft. The CLOUD Act lets US authorities require a US company to produce data it controls wherever the data is stored. In June 2025 Microsoft France’s director of public and legal affairs told a French Senate inquiry, under oath, that he could not guarantee French data would never be handed over without the French authorities’ agreement. The EU Data Boundary settles where the data sits; it does not settle who can be ordered to hand it over.
Pilae’s route is to keep US companies out of the data path. Your apps run on your premises or on dedicated machines run by European datacentre operators in a Swiss or EU region, and the few US services that remain, such as the public network edge, are named in the DPA. Our jurisdiction page lists each one and how to exclude it.
Keeping Microsoft 365, moving the apps
Most teams that come to us from Azure keep Microsoft 365. What moves is the layer of open-source apps around it: the Keycloak that fronts internal tools, the Nextcloud for files that cannot sit in OneDrive, the n8n that automates between systems, the Open WebUI that gives staff a private assistant. Each is wired to Entra ID during onboarding, so nobody gets a new password.
If you are also weighing Microsoft 365 itself, the sovereign workplace page covers the open-source suite that replaces it. Migration is delivered at a fixed price agreed before it starts, and the SLA sets 99.5% monthly availability on Business and 99.9% on Enterprise.
Where Azure stops
Azure stops here
Covered in part by Azure12
- One-click deploy from a curated catalogue
- Migration onto the platform, run for you
- SSO and identity wired into each app
- Updates applied for you, not just announced
- Per-app CVE and advisory tracking
- Changes land in a window you approved
- Staged and checked before production
- Restore drills, not just backups
- A record of every restore
- A change log an auditor can read
- Monitoring and alerting on the apps
- An agent that operates the estate with you
Covered by Azure1
- Logs and metrics exported to your stack
Moving from Microsoft Azure
Find the open-source apps inside your subscriptions
The Nextcloud on a virtual machine, the n8n in an App Service, the Keycloak or GitLab on AKS. Your own code and Microsoft 365 stay where they are.
Keep Entra ID as the front door
Users go on signing in with their Microsoft account. Each moved app is registered in Entra ID before anyone notices it has moved.
Stand the apps up beside Azure
On your own servers or in Pilae Cloud, connected to the same directory, with the Azure copies still serving users.
Copy the data twice
A rehearsal from Azure Database for PostgreSQL and blob storage to learn the timings, then the real move in an agreed window, with the Azure copy kept until every check passes.
Switch off what you no longer pay for
Once the parallel run ends, the Azure resources behind each app are removed and your reservations can shrink at the next renewal.
What you would ask the agent
Pilae Agent plans each change and waits for your approval before anything moves. How the agent works
Two requests, and what it does with each
“Wire Nextcloud sign-on to our Entra ID groups”
Registers the app in your tenant with the redirect you approve, maps the groups to Nextcloud roles and tests a login for each.
“Why is Metabase slow since this morning?”
Pulls the logs, the deploy history and the resource graphs, and comes back with what changed and when rather than with a dashboard.
