MAESTRO
← Blog

“Installed” is not the same as “finished”

Install almost any serious self-hosted app and the first thing it does is tell you off. Nextcloud is refreshingly honest about it — there's a whole Security & setup warnings page listing everything that isn't quite right: memory limits too low, no caching, background jobs at the wrong time, missing migrations, proxy headers it doesn't trust.

The traditional answer is a documentation page and an afternoon. Ours is: MAESTRO reads that list and fixes it, without being asked.

The install doesn't end when the files land

Every recipe can now carry a tuning phase, and it runs automatically the moment an installation succeeds. For your private cloud that means, in about half a minute:

Then it asks the app one more time what it thinks, and shows you the answer. Not our opinion of whether it worked — the app's own verdict.

What it will not do

Two things stay your call, and MAESTRO says so rather than deciding for you: enforcing two-factor authentication for all your users, and email settings when the server has no mail of its own. Those are policy, not plumbing. Everything that has one correct answer gets that answer automatically; everything that depends on what you want stays with you.

Run it again whenever

Upgraded the app? Changed something and now it grumbles? Press Tune next to it in the Apps room — or just say “my cloud is showing warnings” to the assistant. It re-applies the lot and reports back.

Because an installation that finishes with a page full of complaints isn't finished. It's just started.

Try it now

One command puts MAESTRO on your server. Recipes are free — the AI that fixes things is the paid part.

curl -sL try-maestro.pro/install.sh | sudo bash

← all articles