Server survival

When your server dies,
your site doesn't.

MAESTRO keeps a warm copy of your server on a second machine. The night it dies, you press TAKE OVER from your phone — the site is back before your coffee. At 8am you read exactly what happened, in your language.

Set up my standby → See how it works

your terminal

$ ssh prod $ poweroff Connection to prod closed. the primary is gone.

yourshop.com

● 200 OK — still serving

Visitors never saw the server die. The warm copy answered.

🔔 prod is not responding — it has a warm standby of yourshop. Take over?

Kill the server. The site never notices. Backups tell you what was lost, after. Monitors tell you it's down. MAESTRO is the button the alert should have led to.

Nothing to hide. A single-file Python agent, zero dependencies, plain-JSON recipes — read every line before you run it. Your data never leaves your two machines.

$ curl -sL try-maestro.pro/install.sh | sudo bash # install it on both machines

Three things, and it survives

No clustering to configure, no DR project to run. MAESTRO turns a multi-day high-availability setup into an evening for one person.

01🛟 A warm twinMAESTRO keeps an up-to-date copy of your app — data, database, passwords — on a second machine you own. It just waits, minutes behind, ready.

02👁 It watches, day and nightThe watchman notices the moment your server stops answering and tells you — email or Telegram — so nobody has to be staring at a dashboard at 3am.

03⚡ One button, and you're backPress TAKE OVER on the standby. The whole app comes up there, the database restored from its own consistent copy, and the address follows — in about a minute.

All your servers, one calm screen

Every machine you run, each with its warm standby and its one button. This is the whole picture — the thing you glance at and know everyone is safe.

🟢 yourshop🛟 Standby ready · synced 2 min agobackup proven · today 03:00

🟢 clinic-app🛟 Standby ready · synced 9 min agobackup proven · today 03:00

🟢 client-crm⏳ Syncing the first copy…backup proven · today 03:00

Who runs on it

You, one important boxAn indie SaaS, a small shop, the app your business runs on. One server, no ops team, and a backup you've never actually tested. MAESTRO gives it a second life.

You, other people's boxesA freelancer or a one-person MSP holding client servers. When one dies it's your 3am and your reputation. Give every client a warm standby and yourself one panel with one button.

You, a fleet you rent outA hoster or a mobile datacenter. Sell “survives a dead server” as your own feature — MAESTRO is the standby-and-takeover engine under your brand.

You pay for the server you protect

Not for a bad night, not for “incidents” — a calm, predictable price per protected server. The second machine that catches it is yours and costs you nothing here.

Guardian · free

€0

One protected server and its standby — the whole survival chain, forever. Try a takeover before you ever pay.

Peace of mind

€9 / server / mo

Unlimited standbys, nightly backups, a daily report in your language. For your own handful of servers.

For MSPs

€39 / mo

Up to 10 protected servers (then €4 each), team seats, client-grouped dashboards. Liability, cut.

Hosting / OEM

from €499 / mo

Your brand, your support, our engine. Sell survival to your customers, priced per standby pair.

Freemium, not a trial — survival is insurance, and insurance you can't test is worth nothing. See the full pricing →

Set up your standby tonight.

Sleep tonight. It takes one evening and a second machine — even a €4 VPS will do.