v0.12.0 — The MOS app platform

My Own Suite is no longer a fixed bundle of pre-wired apps. This release replaces the original suite with the MOS app platform: versioned, signed app packages that you install, update, back up, and remove individually through Suite Manager.

Highlights

• App store architecture — apps are independently versioned, source-addressed packages with a snapshot/preview/build/health-check/activation/rollback pipeline. Installed apps stay pinned to the exact package snapshot they were installed with; updates are reviewed per app before applying.
• Signed official catalog — catalog and advisories require offline Ed25519 signature verification against the public key shipped with the release; invalid signatures fail closed. External Git-sourced packages run through the same pipeline but remain visibly External · Unverified and are rejected if they request privileged access.
• MOS Privacy Posture — per-app privacy assessments with evidence and provenance in Suite Manager and the public catalog (Stirling PDF is the first assessed package).
• One-line cloud install — curl -fsSL https://get.myownsuite.org | sudo bash on a fresh Ubuntu server, with automatic trusted HTTPS and a root-only claim token gating first-owner setup. A zero-configuration USB installer covers own-hardware installs.
• Whole-suite backup & restore — manual full-suite backups to external drives or attached volumes, with journaled, verified restore. Validated end to end: same-machine and replacement-machine restores, mid-restore power loss, and corruption/version/disk refusal drills.
• Managed platform updates — the Updates screen applies platform updates from the Main (default) or Staging branch track. Installed apps deliberately keep running from their package snapshots and update separately.
• Rebuilt public site and docs at myownsuite.org, deployed from this repository.

Full details in CHANGELOG.md.

Upgrading

There is no in-place upgrade from v0.11.0 or earlier. Those releases used the previous repository layout and pre-assembled stack, which this release replaces.

• New installs: use the one-line cloud installer or the USB installer — see myownsuite.org.
• Existing pre-0.12.0 installs: treat them as end-of-line. Export your app data using each app's own export tools, do a fresh 0.12.0 install, and import. MOS whole-suite backups apply from 0.12.0 onward.

Breaking changes

• MOS now lives at the repository root; the previous layout is archived (archive/mos1-main-snapshot).
• The control-plane URL moved from suite-manager.<domain>/setup/ to home.<domain>/suite-manager/.
• The temporary generation label was removed from MOS-owned env vars, paths, services, containers, and backup folders. Prototype environments should be reset, not migrated.
• The app-agent contract is version 9; backup bundles use schema 3 (version 2 restorable, older rejected); releases must ship trust/official-catalog.pub with matching catalog/advisory signatures.
• USB installer owner fields were removed — owner creation now happens in the browser via the claim flow.

Known limitations (beta)

• The Stable release track is visible in the Updates screen but read-only — managed updates cannot apply tagged releases yet and follow the Main/Staging branch tracks instead.
• Backups are manual, whole-suite, and unencrypted; store them on encrypted, access-controlled storage. Restore requires a compatible installed MOS version.
• External packages are unverified; publisher-key verification is not yet implemented.
• MFA/passkeys are not yet available; pre-1.0 MOS is intended for evaluation and non-critical use with independent backups.

Rollback

The previous stable release is v0.11.0 (previous layout, archived). There is no downgrade path from 0.12.0.