A realistic path to digital independence

Your own private cloud, made simple.

Imagine a personal Netflix, Spotify and Google suite, built from open-source apps you own and control. No subscription, no tracking, no terms changing on you.

Beta · 0.23.1 · free & open source
$curl -fsSL https://get.myownsuite.org | sudo bash

That's the whole install on a fresh Ubuntu 24.04 server. Own hardware? Flash a USB stick.

Own your data

It lives on a machine you control — at home or on a server you rent — and only you hold the keys. Nobody mines it, nobody sells it, and you can walk away with all of it whenever you like.

Simple like an app store

Set it up once. From then on, adding an app is like installing one on your phone: pick it, tap Install, open it. The database, the address and the padlock are handled for you.

Privacy you can verify

MOS has no telemetry and never reports back to us. Every app in the catalog is privacy-graded before it gets in, with the evidence published, so you know what an app sends out before you install it.

How it works

Three steps to your own cloud

First time or seasoned self-hoster, it's the same three steps.

1

Set it up once

Pick where MOS lives: a spare computer at home, or a cloud server you rent. A short guided setup does the rest.

2

Create your account

Open your new private cloud in the browser and sign up like any app. Nothing to configure by hand.

3

Pick your apps

Install what you want from the catalog. MOS runs each one, keeps it updated, and backs it all up.

The app catalog

Pick what you actually need

Established open-source projects, each chosen by MOS for one everyday job and packaged so it runs, connects, and updates without setup. Start with one and add more whenever you're ready.

Apps that work together

Install Seafile, install ONLYOFFICE, press Connect — MOS grants the secret, wires the network, and your documents open in the browser editor. No config files.

Beyond the catalog

Missing an app? No problem.

MOS is built to welcome any open-source app. A repository that carries a small MOS package installs straight from its GitHub URL, as one app or as a whole catalog of them.

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"
How external installs work →See a community catalog →

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
Start from the example repository →Manifest reference →
A quick tour

As easy as the phone in your pocket

No need to know the app's name

Type what you want to replace, like Dropbox, or what you want to do, like photos, and the catalog finds the open-source app for it. One tap installs it; the database, the address and the padlock are sorted behind the scenes.

The MOS App Catalog

Know exactly what you're getting

Every app has a plain-language page: what it does, what it replaces, what it asks of your machine, and how private it is.

An app's detail view with a one-click Install action and its privacy posture grade

A privacy grade, with receipts

Every catalog app is assessed before it gets in and wears an A-to-D grade. Tap it to see why, dimension by dimension, backed by published evidence.

The privacy posture dialog showing an app's A-to-D grade and per-dimension verdicts

Apps that plug into each other

Connect Seafile to ONLYOFFICE and every document in your file cloud opens for editing in the browser. One button, and no keys to copy between admin panels.

Two apps shown as a plug and socket with a one-click Connect action

Updates you approve, not endure

See what an update changes before it happens, including whether the privacy grade moved. You press the button, and if it fails MOS puts the old version back.

The update review dialog listing what an app update changes before it is applied

Backups that run themselves

On a schedule, to a drive you plug in or to storage online, encrypted with a recovery key only you hold. Under the hood is restic, the battle-tested open-source backup engine, so the archive opens anywhere. One button brings the whole suite back.

Backup and restore page in Suite Manager
Kept safe

Looked after, so you don't have to think about it

Self-hosting only pays off if the thing hosting your life is careful. Here is the short version; the docs tell the whole story.

The critical parts are tested by millions

Ubuntu, Docker, Caddy, Let's Encrypt and restic do the heavy lifting; MOS adds the glue and the friendly screens. If those names mean nothing to you, that's fine. If they do, you know why they're here.

MOS architecture →

Your data is encrypted

On your own hardware, everything sits in a standard LUKS vault that the machine's own security chip opens at boot. If the machine goes missing, its disk is unreadable anywhere else.

How the vault works →

Your whole suite in one backup

Every app and everything in it, on a schedule, to a drive you plug in or to storage online, encrypted with your recovery key before it leaves the server. Plain restic archives your key opens anywhere, and one button brings it all back.

Back up and restore →

HTTPS, like magic

A real, browser-trusted padlock on your home network, minutes after first start. Nothing to buy, no port to open, no terminal to touch. Don't believe us? The docs explain exactly how.

How the padlock works →

Updates you approve

Apps and the platform each show what changes before you press the button, and a failed update puts things back. Ubuntu's own security patches install themselves.

How updates work →

Every connection disclosed

MOS has no telemetry and never reports back to us. If an app depends on an outside service, its page says exactly which one and why before you install, evidence included. Your server checks the catalog's signature before trusting a word of it.

How apps are assessed →
Choose your platform

Where should your cloud live?

A computer at home, a cloud server you rent, or (soon) one we run for you. Honest about what each one needs.

Own hardware

USB installer

Download the image, write it to a USB stick, boot a spare machine from it. One confirmation, a few minutes of copying, and the screen shows your suite's address.

  • 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
Go to the install guide →
Cloud server

One command

Sign up with a provider, deploy a small Ubuntu 24.04 server, paste one command into its browser console and wait about ten minutes. Done. Nothing to install on your own computer, and a six-minute video walks you through every click.

  • 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
Go to the install guide →
Coming soon

Managed hosting

Buy from MOS: one click provisions and runs a cloud server for you. No terminal, no VPS account.

  • Nothing to set up yourself
  • MOS-provisioned and maintained
  • A paid subscription — pricing announced at launch
  • Planned — not yet available
We'll announce it here.
Who it's for

You might feel right at home

If any of this sounds like you, MOS was built with you in mind.

  • You want to leave Google, Apple, and Microsoft — without giving up the conveniences you actually rely on.
  • You're a creator or freelancer who won't have your work quietly fed into AI training sets.
  • You're tired of paying for “free” services with your privacy.
  • You want your family's photos and private moments to stay private.
  • You're done with ecosystems that are easy to enter and hard to ever leave.
  • You'd love a home lab, but with no experience it looks like it would eat your evenings and weekends before anything works.
Free planning tool

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
Why MOS exists

Easy self-hosting, without giving up ownership

MOS is not the first project to make open-source apps installable from a catalog. The projects before it each solved a different part of the problem.

Why ownership matters
TrueNAS SCALE

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.

CasaOS

showed how friendly a home server could be. Its release pace later slowed as its maker’s visible focus moved toward ZimaOS and hardware.

Cloudron

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.

Questions

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?
  1. UpstreamThe publisher releases a version
    1. MOSNornOur review agent Norn tests the release
    2. A human reads its results and signs
    3. Promoted to the stable track
  2. 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.

Open source matters

Built on great open-source work

My Own Suite stands on top of some of the best open-source tools available today. Huge credit to the teams and communities behind them. This would not exist without their work.

MOS itself is licensed under theGNU Affero General Public License v3.0 only: free to use, change, share, and host commercially, with modified hosted versions kept open to their users.

Built with

A project by

Beta · 0.23.1Early software

This is a working prototype, not a finished product. Expect some rough edges.