Skip to main content

Miren Cloud

You install Miren on your own server and you own the whole thing. Run it standalone and it works great on its own, but it's an island: your apps are only reachable where your network reaches, backups are yours to arrange, and it's just you managing it.

Miren Cloud is the connective tissue you can opt into. It doesn't take over your infrastructure. It sits alongside your clusters and adds the things that are a pain to build yourself.

What you get by connecting​

A public front door for your apps. Claim a subdomain like mycluster.run.garden and your apps get a real address. With Miren Anywhere, they stay reachable from the internet even when your cluster has no public IP, so a home lab or a box behind NAT can serve real traffic.

Your team. Bring other people in and control who can do what with role-based access, instead of sharing one set of credentials.

Multiple environments. Run separate clusters for production, staging, and preview work under one account, and switch between them from the CLI.

You still own everything​

Connecting to Miren Cloud is additive, not lock-in. Miren runs fully standalone, and if you'd rather keep it that way you can install with cloud turned off:

sudo miren server install --without-cloud

A standalone cluster reaches the network however you've wired it, and none of the cloud features above apply. You can always connect later.

Getting connected​

When you run miren server install, Miren registers the cluster with Miren Cloud and walks you through creating your account. To connect a server you installed standalone, register it after the fact:

miren server register -n my-cluster

Then log in from whatever machine you work on:

miren login

The Getting Started guide covers the full install-and-first-deploy flow. For everything the CLI can do with clusters, see the miren cluster reference.

Explore​