Hybrid cloud for open-source apps: on premises and Pilae Cloud

Choose for each app where it runs: on your own hardware or on dedicated machines in Pilae Cloud. One console, one contract, one private network across both.

Start with one workloadBook a 30-minute briefing

Placement
Chosen per app, changed by agreement
Locations
Your premises and any of 10+ Pilae Cloud regions
Network
One private mesh across every site
Contract
One, with Pilae SA under Swiss law

Each app where it belongs, one estate to run

Few organisations have one answer for every system. Patient records stay in the building. The team wiki can live anywhere in Switzerland. Hybrid lets you give each app its own answer without running two platforms.

Per-app placement

Keep sensitive or latency-bound apps on your hardware. Put the rest on dedicated machines in Pilae Cloud.

One private network

A private, encrypted mesh joins your premises and your cloud machines. Apps talk to each other privately, wherever each one runs.

One console

Apps, machines, deployments, backups, logs and audit for every site, in the same control plane.

Same recipes everywhere

An app is installed and updated from the same tested recipe on your hardware and in Pilae Cloud, so moving it is routine.

Backups per location

Each app is backed up daily, encrypted and offsite in the country you chose for it, with a restore test every month.

One contract, one SLA

The availability commitment of your plan and your support terms cover every app we operate, on premises or in the cloud.

One operator for both halves of your estate

A hybrid estate usually means two teams, two toolchains and a network nobody wants to touch. Pilae runs both halves the same way. The Pilae Agent plans changes on your hardware and in the cloud alike. The control plane shows every app on one screen. The private network joins your sites so apps reach each other without a public address.

Keep the sensitive part in the building

Put the apps with the strictest rules on your own premises: the database with patient data, the file share under client confidentiality, the model that reads internal documents. Run the rest on dedicated machines in Pilae Cloud, in the region you choose from our regions. Your contract names the site for each app and each backup.

Clear lines of responsibility

On your premises, your team keeps the room, the power and the hardware. Pilae keeps the operating system, the apps, the backups and the monitoring. Our shared responsibility page sets out each line. To plan your split, start with a scoping call.

How a hybrid estate is set up

  1. Map the apps

    We list each app, the data it holds and the rules that apply to it: residency, latency, sector or client requirements.

  2. Place each app

    Together we decide where each one runs, and the placement is written into your contract.

  3. Build the network

    Your machines and your Pilae Cloud machines join one private mesh, with a hardened gate on port 443 for the apps you publish.

  4. Deploy and connect

    Apps are installed from tested recipes and connected to one single sign-on, whatever site they run on.

  5. Operate as one

    The Pilae Agent and our engineers patch, back up and monitor every site from the same console.

What your contract includes

Placement
The site for each app and for its backups, named in the contract. An app moves only with your written approval.
Availability
A monthly availability commitment with service credits for each app, on every site: 99.5% on Business, 99.9% on Enterprise.
Responsibilities
A shared responsibility matrix: what your team keeps on premises, such as power and hardware, and what Pilae runs.
Monitoring
60-second probes on every app and machine metrics on every site, with alerts to Pilae engineers around the clock.
Moves
Moving an app between your premises and Pilae Cloud is planned, approved and recorded like any other change.

The apps behind it

Questions

What does hybrid mean with Pilae?

Some of your apps run on your own hardware and some run on dedicated machines in Pilae Cloud. Pilae operates both halves with the same agent, the same console and the same contract, and a private network connects them.

Can an app on premises talk to an app in Pilae Cloud?

Yes. Every machine joins the same private mesh, so an app on your premises reaches an app in Zurich over an encrypted private connection. Neither needs to be exposed to the internet.

Can we move an app from our premises to Pilae Cloud later?

Yes, in either direction. The same recipe runs in both places. We plan the move, take a verified backup, restore it on the new site, check it with your team and switch over in your window.

Where are backups kept in a hybrid deployment?

Each app is backed up in the country you chose for it. Backups are daily, encrypted and stored offsite, and restore tests run every month and are recorded in the console.

Do we need two contracts?

No. One contract with Pilae SA covers every app we operate, wherever it runs. Hybrid estates start on the Business plan, whose prices are on the pricing page; multi-site estates are quoted on Enterprise.

Related

Draw your hybrid estate with an engineer.

Thirty minutes to list your apps, decide where each one runs and see how the network joins them.