Your own private cloud, made simple.
Own your data
Simple like an app store
Privacy you can verify
Three steps to your own cloud
Set it up once
Create your account
Pick your apps
Pick what you actually need
Apps that work together
Actual Budget
Privacy configuredPrivacy grade B (A is best, D is worst)Talks to outside services out of the box — MOS turned those parts off for you.
Contacts nothing outside your server in normal use.
Immich
External dependencyPrivacy grade C (A is best, D is worst)Something leaves your server in normal use and there is no in-app setting that stops it. MOS reviewed that and accepted it as the price of the feature. The full assessment says exactly what leaves, who receives it, and why.
Contacts 5 hosts outside your server in normal use, before you turn anything on.
huggingface.coFrom the app*.hf.coFrom the app*.modelscope.cnFrom the apptiles.immich.cloudFrom your browserstatic.immich.cloudFrom your browser
Jellyfin
External dependencyPrivacy grade C (A is best, D is worst)Something leaves your server in normal use and there is no in-app setting that stops it. MOS reviewed that and accepted it as the price of the feature. The full assessment says exactly what leaves, who receives it, and why.
Contacts 6 hosts outside your server in normal use, before you turn anything on.
api.themoviedb.orgFrom the appimage.tmdb.orgFrom the appwww.omdbapi.comFrom the apprepo.jellyfin.orgFrom the app*.mirror.jellyfin.orgFrom the appwww.gstatic.comFrom your browser
Navidrome
External dependencyPrivacy grade C (A is best, D is worst)Something leaves your server in normal use and there is no in-app setting that stops it. MOS reviewed that and accepted it as the price of the feature. The full assessment says exactly what leaves, who receives it, and why.
Contacts 6 hosts outside your server in normal use, before you turn anything on.
api.deezer.comFrom the appauth.deezer.comFrom the apppipe.deezer.comFrom the app*.dzcdn.netFrom the appapi.listenbrainz.orgFrom the applabs.api.listenbrainz.orgFrom the app
ONLYOFFICE
Privacy configuredPrivacy grade B (A is best, D is worst)Talks to outside services out of the box — MOS turned those parts off for you.
Contacts nothing outside your server in normal use.
Paperless-ngx
Private by defaultPrivacy grade A (A is best, D is worst)Runs entirely on your machine. Nothing leaves your server unless you share it.
Contacts nothing outside your server in normal use.
Radicale
Private by defaultPrivacy grade A (A is best, D is worst)Runs entirely on your machine. Nothing leaves your server unless you share it.
Contacts nothing outside your server in normal use.
Seafile
Private by defaultPrivacy grade A (A is best, D is worst)Runs entirely on your machine. Nothing leaves your server unless you share it.
Contacts nothing outside your server in normal use.
Stirling PDF
External dependencyPrivacy grade C (A is best, D is worst)Something leaves your server in normal use and there is no in-app setting that stops it. MOS reviewed that and accepted it as the price of the feature. The full assessment says exactly what leaves, who receives it, and why.
Contacts one host outside your server in normal use, before you turn anything on.
api.iconify.designFrom your browser
Vaultwarden
Your choicePrivacy grade B (A is best, D is worst)Something leaves your server in normal use, and the app has a setting that stops it. MOS left the choice to you because it is a real trade-off. The full assessment says what leaves, who receives it, and where the switch is.
Contacts 2 hosts outside your server in normal use, before you turn anything on.
Any websiteFrom the appapi.pwnedpasswords.comFrom your browser
Missing an app? No problem.
Installing your favorite app is easy
- Paste the repository's GitHub URL into the Apps search; MOS shows what it publishes and installs from there
- Add a community catalog the same way: one repository, many apps, kept on your Apps screen under the publisher's name
- Keep a catalog of your own and share it with friends and family as a single link
- Every app from an added source runs inside the same limits as a catalog app: its own storage, its own addresses, no privileged access
- Updates, backups, restart and uninstall work exactly as for any other app
- No package yet? Ask Claude Code:
/mos:add-app "help me install Miniflux on my MOS server"
Publishing your open-source app in MOS is easy
- Add a
.mos/folder to your repository: one manifest describes routes, storage, setup fields and health, and your Dockerfile builds the app - Packaging is one prompt with the MOS plugin for Claude Code, and a complete example repository documents the format for any other assistant
- No store account, no approval queue, no registry: people install from your repository URL and are offered updates when you publish a newer package version
- Their data stays on their own server, the way your project intended
- Publish one app, or curate a catalog of apps you didn't write
As easy as the phone in your pocket
No need to know the app's name

Know exactly what you're getting

A privacy grade, with receipts

Apps that plug into each other

Updates you approve, not endure

Backups that run themselves

Looked after, so you don't have to think about it
The critical parts are tested by millions
MOS architecture →Your data is encrypted
How the vault works →Your whole suite in one backup
Back up and restore →HTTPS, like magic
How the padlock works →Updates you approve
How updates work →Every connection disclosed
How apps are assessed →Where should your cloud live?
USB installer
- A spare mini-PC or old laptop to dedicate — its disk is erased
- A free USB writer such as Rufus or balenaEtcher
- Best privacy: nothing leaves your home, and it costs only electricity
One command
- A small rented server, about $20–25 a month
- Reachable from anywhere you allow
- Your own domain in one step, or the address MOS generates for you
Managed hosting
- Nothing to set up yourself
- MOS-provisioned and maintained
- A paid subscription — pricing announced at launch
- Planned — not yet available
You might feel right at home
Fair warning: self-hosting is addictive
Ask anyone who does it. The first time you move a piece of your life off a Big Tech service and into something you own, you'll want to do it again. And you'll want to show off your stack. This little tool makes both easy: map what you use today, pick the open-source apps that replace it, and share the plan with friends to compare notes.
- Runs entirely in your browser — no account, nothing to install
- Your plan never leaves your device
- Export as PNG, WebP or SVG, or share a link others can remix
pairs excellent app discovery with a powerful NAS-first system, where storage pools, permissions and networking come before the first app. A natural fit for technical operators, a high bar for everyday use.
showed how friendly a home server could be. Its release pace later slowed as its maker’s visible focus moved toward ZimaOS and hardware.
shows how polished self-hosted app management can become. Its core platform moved from open source to source-available, and the demand for a free, fully open-source alternative remains.
MOS brings those lessons together: an app-first private cloud for ordinary hardware, open all the way down, with no project account or license service needed to keep it running. It is still an early beta, and an invitation tohelp shape the alternative.
Honest answers
Do I need to be technical?
Short answer: a little, for the install. Home servers are notoriously fiddly and MOS removes most of that, but you still have to get it onto a machine. On a cloud server that means following a six-minute video and pasting one command. On your own hardware it means writing the image to a USB stick with a free tool such as Rufus or balenaEtcher and booting a spare machine from it. If you can follow a video guide with a little patience, you can do this.
Once you're in, the hard part is over. Everything happens in the browser, and installing an app is pick, Install, open: the settings are chosen for you, the address and the padlock are arranged, and the next backup covers it. How to get started lays out both paths side by side.
Is it really free — what does it actually cost?
MOS and every app in the catalog are free and open source: no license keys, no subscriptions, no paid tier.
The only cost is the machine it runs on: a little electricity at home, or about $20–25 a month for a rented cloud server. A managed option, where you pay MOS to run it all for you, is coming for people who'd rather not touch a server at all.
Where does my data actually live?
On the machine you installed MOS on. Nothing passes through a MOS-owned cloud, the platform has no telemetry, and there is no sign-up with us: we don't know that you installed it.
The one exception is this page, which counts anonymous visits with analytics we host ourselves. Your suite has none. The privacy policy lists every connection your server makes.
How do my apps stay up to date?
- UpstreamThe publisher releases a version
- MOS
Our review agent Norn tests the release - A human reads its results and signs
- Promoted to the stable track
- MOS
- Your serverYou review, then press the button
Not on their own: nothing changes on your server until you press the button. Behind the scenes we watch each catalog app's releases. A new version gets its package rebuilt, the releases in between read for breaking changes, its privacy assessment redone, and the result tested on a real server: a fresh install, an update from the version you'd be coming from, and a backup-and-restore drill, with every outside connection the app makes recorded. Only then is it signed into the catalog, and a version that breaks something is held back instead.
Your server checks that signed catalog every few hours and shows an Update available badge, so a fix for your password manager never waits for a MOS release. You see what changes first, including whether the privacy grade moved, then you press the button. MOS builds the new version before stopping the old one, and if the update fails it puts the app back or tells you exactly where it stopped. How updates work.
Can I install an app that isn't in the catalog?
Yes. Any GitHub repository with a small .mos folder is an app source: paste its URL into the Apps search and MOS shows what it publishes, and what each app asks for, before anything is built. One repository can carry one app or a whole catalog, so a collection someone curates is added once and browsed like the rest.
These apps are labelled External · Unverified everywhere, because we haven't reviewed them and won't pretend otherwise, and MOS runs them with fewer permissions than catalog apps. Building one runs the publisher's own instructions on your server, so it's your call; MOS makes sure it's an informed one.
No package yet? It is a manifest plus a Dockerfile, with a complete example repository to copy, or one prompt with the MOS plugin for Claude Code: /mos:add-app writes the package for you. Bringing your own apps walks through it.
What if I want to leave?
Everything runs on standard open-source apps with standard data formats, and your backups are plain restic repositories, encrypted with your recovery key before they leave the server.
If MOS vanished tomorrow, that key and the restic command-line tool would still open every backup you have, on any machine. The way out does not run through us.
It's beta — is it safe to use?
MOS is version 0.23.1 and improving quickly. Every change runs an automated test suite before it lands, the whole install-to-apps flow is driven on real machines before a release, and every image is pinned to an exact digest. The changelog is public.
Trust is the product, so here's the honest part: pre-1.0 releases can include breaking changes. Treat MOS as ready for evaluation and non-critical use for now: keep an independent copy of anything you can't afford to lose, and take a backup before you update. The button is right there.






