Network boundary
Traffic flows from your device through the Tailscale network to your Macs. The provider node has no edge: nothing goes there until you connect a provider, and then only the conversations you send it.
What stays on your network
Conversations
Chat history is stored on your Mac, in a local database. It is not synced to any cloud.
Model Weights
Downloaded once, kept on your Macs, never uploaded anywhere else.
Metrics
CPU, GPU, memory, and power readings stay on your cluster, where r1o uses them to run your models.
Configuration
Cluster settings, model preferences, and deployment history, all in local files.
How auth works
Cluster access is mesh membership. The marketing site is separate.
On your private cluster, Tailscale/WireGuard identity is the auth boundary — devices on the tailnet reach asmi and your local services directly. This public website (download / beta) uses Supabase Auth (Apple, Google, or email) only for account and release access — not as the cluster login.
Any device on your Tailscale network gets full access. Add a new Mac to the cluster, install Tailscale, and it is immediately part of the mesh — no config files, no firewall rules, no port forwarding.
Local model or cloud provider
| Feature | Local model | Cloud provider |
|---|---|---|
| Where the model runs | Your Macs | The provider's servers |
| Who sees your messages | Only your Macs | The provider, under its terms |
| Account or API key | None | Yours, for that provider |
| Conversation history | On your Mac | On your Mac, plus what the provider keeps |
| Model weights | On your Macs | The provider's |
| Cost | Your hardware and power | The provider's pricing |