Two commands. A sovereign node on hardware you own.
No cloud account, no VPS, no ports to forward. The installer stands up the Atmosphere runtime and brings StratosAgent online on the machine in front of you — keys generated locally, meshed peer-to-peer, nothing exposed to the public internet. This is the in-depth install: the exact commands per OS, what each step actually does, what you need, and what's live today.
- Commands
- Two
- Node.js
- 20.19+
- Inbound ports
- Zero
- Keys
- Local · sealed
- Account
- None required
Lives in your terminal
Pick your OS, copy the two commands, and you have a sovereign node. The installer requires Node.js 20.19+ and npm; the same flow works on macOS, Linux, and Windows — only the shell syntax differs.
Two commands. No firewall holes, no inbound ports, nothing exposed to the public internet.
- 1
One installer
A single command brings up the Atmosphere runtime — no firewall holes, no inbound ports, nothing to expose to the internet.
- 2
Your hardware
StratosAgent provisions on the machine you already own. Keys are generated locally and never leave it.
- 3
Meshed instantly
Your node hole-punches into the global mesh and is reachable across every channel — still fully sovereign.
Each step, demystified
The two commands hide a precise sequence. Nothing here phones home for permission, opens a listener, or hands a key to a third party — every step is local or outbound-only.
- 1
Fetch & verify the runtime
The installer downloads the Atmosphere runtime and verifies it before anything runs. No background service is exposed to the network. - 2
Mint local keys
The public operating core generates a per-node keypair on-device when it mints a receipt — try it withstratos trace demo/proj/wf/task1. Keys never leave the machine, and the receipt verifies with the public key alone. - 3
Join the mesh
The mesh transport announces on the public DHT and hole-punches to peers — all outbound, no inbound port ever opened. Broad multi-device meshing is still wiring (see the honest status split below). - 4
Come online across channels
Once meshed, the agent is reachable on the channels you configure — the same StratosAgent behind every front door.
What it does NOT do
- Open an inbound port or run a public listener
- Require a cloud account, VPS, or static IP
- Upload your keys, prompts, or data anywhere by default
- Forward traffic through a relay that can read it
What you need to run a node
Modest. A node is meant to run on the hardware you already own — a laptop is enough to get started. The frontier cloud is optional — your own account, your key.
OS + Node.js
Disk
Local inference (optional)
Frontier key (optional)
What's live the moment you install
The install flow is in early access, opening at launch. Here's the honest split of what comes up live, what needs configuration, and what's still wiring — straight from the status matrix.
Vault & post-quantum keys
- Secrets sealed at rest (AES-GCM)
- Derived keys zeroed after use
- ML-DSA-65 seals on skills & receipts
Mesh transport
- Hyperswarm DHT + hole-punch
- Per-platform bundles built
- Broad multi-device runs still early
Agent channels
- Telegram, Discord, Slack, Matrix, Signal
- Daemon-started adapters
- Owner-gated authority
The installer endpoints shown above are the launch quickstart. Early access is opening at launch— request access and we'll bring you online.
StandaloneHow we label every capability
Full status matrix →- Live
- Running in production, exercised by tests.
- Wired
- Built and connected into the daemon; hardening in progress.
- Standalone
- Built and tested in isolation; live wiring is supervised.
- Mock
- Scaffold / placeholder — explicitly NOT real yet.
Get early access
Run it on your own metal.
Request early access and we'll bring your node online. Or read exactly what's live today before you do.