A cloud that arrives finished

There is a moment everyone who has installed software on a server knows. The progress bar finishes. Something is running. And then a page opens asking you to choose a database, invent an administrator password, and answer six questions you were rather hoping the computer already knew the answers to.

That gap — between installed and working — is where most evenings go. MAESTRO is built to close it.

What containers are, in one paragraph

A container is software packed by the people who made it, together with everything it needs, so it runs the same on your machine as on theirs. Nothing gets mixed into the rest of your server; nothing is left behind when it goes. That is genuinely useful. It is also where the awkward question lives: if the container can be thrown away and replaced, what happens to your files?

The one thing we insisted on knowing

Most panels will happily list your containers. MAESTRO answers the question that actually matters: will your data survive? It looks inside each running container and compares what is there now against what the maker shipped. Anything you have written that lives only inside the container — and would vanish the next time it is updated — is named, in plain words, before it is lost rather than after.

When something is at risk, there is a button that takes a copy out to storage that outlives the container, and puts it into your backups from then on.

What else it takes off your hands

• An address, with HTTPS. You type a name. MAESTRO knows which domains you have, makes the subdomain, points it at this machine, waits until the world can see it, and puts a certificate in front of it.
• Passwords you never invent. Anything that needs a secret gets a strong one, generated and sealed in your Vault. Nothing is written into a file for someone to find later.
• Updates nobody notices. The new version starts, MAESTRO waits until it is genuinely healthy, and only then do visitors move across. If it never gets healthy, nothing moves.
• Several copies, one address. Visitors are shared between them. One falls over, the others carry on.
• Bounds. One container can be held to a share of memory and processor, so it cannot starve everything else on the machine.
• It comes back by itself after a crash or a reboot, without you.
• Moving house. Image, data and settings travel to another machine together.

Nextcloud, as the proof

A private cloud is the honest test of all this, because Nextcloud is famous for the setup screen. Ours does not have one.

You give it a name. MAESTRO makes the address, creates a real database beside it, invents the administrator account and a long password, seals that password in your Vault, and starts the two together. When it tells you it is ready, it is ready: you sign in and you are inside your own cloud. No wizard, no database question, and no quietly choosing the simplest storage that will hurt you in a year.

And two things you can ask for while you are there

At the moment you set it up, MAESTRO offers extras — clearly, with what each one costs in memory and which ports it needs, so nothing is switched on quietly behind your back.

Word and Excel in the browser. Tick it, and documents and spreadsheets open and edit right inside your cloud, with several people in the same file at once. Under the surface this is a second container with its own address, because your browser talks to the editor directly as well. You do not have to know that. You do have to know it needs about 2 GB of memory of its own — so MAESTRO checks what your machine has free and says plainly whether it fits, whether it only just fits, or whether it will not be added because it would push something you rely on out of memory.

Chat and calls. Tick it, and your cloud gains messaging and video calls between people — with a relay of its own, so the picture and sound go through your machine and nobody else's.

That second one deserves more room than a paragraph, so it has an article of its own: calls that stay yours — what it takes for two browsers to actually find each other, and why running the relay yourself is the difference between a call that works and one that quietly fails.

The part we refuse to be vague about

Opening a port on your machine is only half the job: your provider has a firewall in front of you that MAESTRO cannot see from inside. So after everything is installed, MAESTRO knocks from the outside — from our servers, over the real internet — and tells you what actually got through. If a port is still closed, you read it on the service's card, in a sentence, rather than discovering it during a call that will not connect.

Installed is not the same as working. We would rather say the difference out loud than let you find it.

← all articles