Mesopod

Closed beta · Free for personal use

Run your self-hosted apps without the ops.

Mesopod runs Immich, Vaultwarden, Jellyfin and the arr stack on your own machine. Pick an app, fill in a short form, and a few minutes later it's up at a proper HTTPS address on your home network. It restarts itself if it crashes, and updating is one click.

Every app you run, and whether it's healthy.
Every app in the catalog is a short form to fill in.
Your machine connects out to us, so there's nothing to port-forward.

What you get

Already running Docker Compose?

Point an app at the folders you already have and nothing gets copied or moved. Mesopod handles routing and certificates itself, so there's no reverse proxy to look after and no ports to forward.

Underneath it's k3s. Everything Mesopod creates is an ordinary Kubernetes object you can inspect with kubectl, and it keeps running without us.

The catch for now is that you can't bring your own containers, so you're limited to the fourteen apps in the catalog.

How it works

  1. 01

    Connect a machine

    Add a cluster in the console and run the command it gives you on a Linux box, a Mac or a Windows 11 PC. It sets up everything Mesopod needs and connects out to us.

  2. 02

    Pick an app

    Choose one from the catalog, fill in a few settings and deploy.

  3. 03

    Open it

    Go to app.yourhome.mesopod.app on any phone or laptop at home. On a Mac set up with OrbStack's own Kubernetes, only that Mac can open it for now.

What works today

Linux · Debian/Ubuntu, x86_64 or arm64 macOS · k3d on OrbStack or Docker Desktop Windows 11 · WSL2 new

What's missing

It's an early beta. Here's what it doesn't do yet.

  • Remote access. Use Tailscale for now; there's a guide.
  • Backups. Take a snapshot before you move anything important over. Here's how.
  • Custom domains. Every address ends in mesopod.app.
  • Editing settings in place. Changing an app's settings redeploys it, though your data is kept.
  • GPU passthrough and VPN sidecars. Neither is supported yet.
  • Your own containers. Only the fourteen catalog apps for now.
  • Open source. Not yet; see the questions below.

Questions

Why Kubernetes and not Docker?
Because it already handles restarts, recovery after a reboot and isolation between apps, which we'd otherwise have to build on top of Docker. We use k3s, which is a single binary, and you won't have to touch it.
What can you see on my machine?
The apps you've asked us to run, the settings you entered and whether each app is healthy. We store secrets encrypted. When an app deploys, our server decrypts its secrets in memory and seals them to your machine's key, so only your machine can open them once they leave us. Never your photos, your files or anything stored inside the apps.
Why is part of it in the cloud?
So that nothing in your house has to be reachable from the internet. Your machine opens an outbound connection to us, and you can use the console from anywhere.
What happens if you shut down?
Your apps keep running. You'd lose the console, but nothing on your machine needs us to stay up.
Is it open source?
Not yet. You can read the install script at the URL you run it from, and the permissions of the outpost, the part that runs on your machine, are documented. Everything it creates is a plain Kubernetes object you can inspect.
What does it cost?
Nothing for personal use, and we plan to keep it that way.

Cohort 1

We're looking for five people.

Next week you'd install it on a 30-minute call while we watch, so we can see where it trips you up. Then you'd spend two weeks in a small Discord with the two of us, and we'll fix what you run into, usually within a day.

Request an invite