This is the live MOSS demo, hosted on its own site. It shows the moment someone receives a small app: a link arrives, the host says in plain words what the app can do, and the person tries it or keeps it with no account. It is built as an installable iPhone web app, so it works best in Safari on an iPhone. To try it, open the MOSS menu at the top and choose Add apps, then pick one of the sample apps. Links to bigger apps expire 10 minutes after they are shared.
MOSS (Mozilla Software Suite) is a working demo of a runtime and application standard for owning, using, and managing personal software without cloud hosting. The MOSS runtime provides apps with a set of resources and capabilities attuned to the needs of personal software made by nondevelopers and not for wide deployment. Rather than building an end-to-end service, MOSS presumes people will create personal apps where they prefer, including with AI tools. MOSS solves for where and how these apps run and are owned long-term.
In this model, apps are small, self-contained packages of ordinary web content (HTML, JS, CSS) with a manifest that says what it needs. These apps use a standard application format. The host is anything that opens packages, such as a browser or a phone app, and it provides the sandbox, storage, permissions, sharing and updates.
AI tools now let people make their own software, but running it, keeping it working, updating it and sharing it still takes expertise and ongoing upkeep, or ties the app to the provider that made it.
People who make small apps with AI tools, without being developers, have this problem, along with the people they share those apps with. Today there are three routes.
Build-and-host services such as Lovable, Vercel and Replit build apps and host apps, which means creators are on the hook for maintaining the apps, paying for storage space, and protecting against abuse. Coding tools such as Claude Code and Codex write the code and leave you to use it however you can. To deploy an app takes additional know-how and hosting services. Chat applications like ChatGPT and Claude can host custom build artifacts, but they are tied to that platform. The first two still ask for some expertise and ongoing upkeep, and all three tie the app to a provider.
It matters because model providers may absorb the standalone build-and-host stacks, and lock-in is forming now, while what people make with AI becomes more personal and more valuable to them.
MOSS does not compete at building. It assumes people will build with whatever tools, models and services they like, and offers what comes after: simple, stable use, maintenance, sharing and updates. It works like a PDF or an e-book. The package is self-contained, and any of several hosts can open it.
Apps run on your device and work offline, and Mozilla hosts no app compute. When an app arrives, the host checks it and says in plain words what it can do, and if it needs fixing, it gives you a prompt to paste back to the tool that made it. Sharing sends an independent copy: the software, the data and the permissions are separate, so a recipient gets the app but not your data or credentials. Updates are offered, never forced. The spec is open, so others can adopt it, and software, data and history can all be exported.
Making software is no longer the hard part. Keeping, updating and sharing it is, and people will want an open home for what they make that is not tied to the AI tool that made it, a service that offers far more than they need and a subscription fee, or highly constrained workflow builders.
If that holds, personal software becomes something people own, like a document or a book, and an open format and host become the place it lives, with a reason for people to install and return.