Files

SysAdmin 0a0075ce66 docs(naming): adopt OS / Enhanced product-line framing + align with existing repos

Two product lines, named to make scope obvious to buyers:
- 🔒 SilverMetal OS — we ship the operating system or ROM
  (Linux, Pixel, Samsung-unlocked, Motorola-unlocked)
- 🛡️ SilverMetal Enhanced — we harden the OS the device already runs
  (Windows, macOS, iOS, generic Android)

Repo alignment:
- SilverVPN already exists as a SilverLABS product (server + MAUI client +
  Linux client + tunnel service). stack/vpn/ is now an integration pointer
  rather than a re-scaffold; per-platform READMEs reference it.
- SilverApple is deprecated; SilverMetal Enhanced — iOS supersedes it.
  Migration step added as roadmap milestone 3I.1.
- SilverDROID name clash explicitly noted as unrelated (it's the SilverSHELL
  AppStore Android client, not an Android ROM).
- SilverChat may overlap with SilverVPN.Client.Chat; alignment decision
  added as roadmap milestone 1.1.1.

Roadmap restructured: phases now track the OS/Enhanced split.
Platform matrix re-sectioned and decision flowchart updated.
README rewritten around the two-product-line framing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-25 03:30:45 +01:00

2.9 KiB

Raw Blame History

SilverLABS Application Stack

The cross-platform spine of SilverMetal. These apps replace the cloud services your device normally talks to. Same brand, same account, same data on every platform — whether the user picked a 🔒 SilverMetal OS flavour or a 🛡️ SilverMetal Enhanced flavour.

Components

Component	Status	Purpose
`browser/` — SilverBrowser	v1 (Linux MVP)	De-Googled, telemetry-free browser
`vpn/` — SilverVPN	Existing — see `SilverLABS/SilverVPN`. This directory tracks integration only	Always-on, no-logs VPN with our infrastructure
`sync/` — SilverSync	v1 (Linux MVP)	Private replacement for iCloud/Google/OneDrive
`chat/` — SilverChat	v1.1 — may overlap with `SilverVPN.Client.Chat`; alignment decision pending	E2EE messenger
`duress/` — SilverDuress	v1.1	Duress password / panic-wipe
`keys/` — SilverKeys	v1.1	Zero-knowledge password + 2FA manager
`shared/` — common code	ongoing	Account SDK, crypto primitives, branding

Account model

Users get a SilverLABS account number (Mullvad-style — random, no email, no name). One account → all Stack apps. Payment is processed separately (SilverDotPay / cryptocurrency option) with no link back to the account number.

Cross-platform build philosophy

Each app is built natively per platform — no Electron sprawl where avoidable:

Linux: native .deb + Flatpak
Android: native APK / AAB (or MAUI where SilverVPN already provides it)
Windows: native MSI / EXE (signed)
macOS: universal binary .pkg (notarised)
iOS: App Store

Where a single codebase (e.g., MAUI as SilverVPN already does, or Tauri/Rust core for Browser/Sync/Keys) lets us hit multiple platforms with thin native UI shells, we use it. We avoid Electron unless the cost of native is unjustifiable.

v1 ship order

For SilverMetal OS — Linux v1:

SilverBrowser — ungoogled-chromium-derived, our defaults, our update channel
SilverVPN integration — existing product, integrated into our ISO with always-on defaults and kill-switch
SilverSync — Nextcloud-backed (server side), client-side encryption, native Linux client

These three ship with SilverMetal OS — Linux v1. v1.1 adds Chat, Duress, Keys.

Server side

Server components live in separate repositories:

SilverLABS/SilverVPN — already exists; includes server stack
SilverLABS/silver-sync-server (to be created) — Nextcloud + Radicale + Baïkal stack
SilverLABS/silver-chat-homeserver (to be created OR may live under SilverVPN) — depends on v1.1.1 alignment decision
SilverLABS/silver-account (to be created) — account-number issuance + auth gateway

Self-hostable counterparts are documented for users who don't want to use SilverLABS infrastructure.

2.9 KiB Raw Blame History