Cross-Platform & Remote Access
Run Atmos on desktop or browser locally, or share this machine via integrated tunneling—separate from Atmos Computer.
Atmos ships on multiple clients (desktop, browser). Remote Access is a third idea: expose the Atmos Server on this machine through an external tunnel so someone opens a public URL in a browser. That is not Atmos Computer, which uses Atmos Relay and does not require Ngrok, Tailscale, or Cloudflare on your laptop.
Two different “remote” mechanisms
| Remote Access (this page) | Atmos Computer | |
|---|---|---|
| Goal | Share this running Atmos instance | Work on another machine’s Atmos Server |
| Transport | Third-party tunnel (Tailscale, Cloudflare Tunnel, ngrok) | Atmos Relay — the server connects outbound to Atmos |
| Who runs the server | The machine you are sitting at | The VPS / remote host you registered |
| Typical client | Browser opens Public URL | Desktop/Web Connect in My Computers |
| Where to configure | Desktop app only → Settings → Remote Access | Settings → Atmos Computer |
| Tunnel apps on your laptop | Yes (provider tools) | No |
Do not mix the two: turning on Remote Access does not register an Atmos Computer, and Connect to a remote Computer does not start Tailscale or ngrok.
Cross-platform clients (local)
Use Atmos on the machine where the server runs:
| Client | How you use it |
|---|---|
| Desktop app | Native app; talks to Atmos on the same machine automatically |
| Web (local) | Browser at your local address (e.g. after installing the local web runtime) |
| Mobile | Planned — follow release notes |
This is normal local use: no tunnel and no relay unless you turn on one of the remote options below.
Remote Access (integrated tunneling)
Remote Access lets you publish this computer’s Atmos so you—or someone else—can open it in a web browser via a Public URL.
How it is designed
- Atmos runs a dedicated secure entry on your machine—not your raw dev port on the open internet.
- You choose a provider: Tailscale, Cloudflare Tunnel, or ngrok.
- The desktop app helps you install or sign in to that provider, then starts the tunnel.
- Atmos shows a Public URL (and optional share link or entry code) in Settings → Remote Access and in the header tunnel menu.
- Visitors open that URL in a browser; Atmos checks the session, then serves the app securely.
Your day-to-day Atmos data still stays on this machine; the tunnel only provides a controlled front door for browsers.
Where to configure
- Use the Desktop app (Remote Access is not available in browser-only local web mode).
- Open Settings → Remote Access.
- Detect providers; follow install or sign-in steps (the app can open a helper terminal).
- Choose private or public mode where offered, set how long the link stays valid, then Start.
- Copy Public URL and open it on another device (your LAN, Tailscale network, or the public internet—depending on the provider).
Provider notes
- Tailscale — virtual private network; good when your devices already share a tailnet.
- Cloudflare Tunnel — HTTPS through Cloudflare; no need to open a port on your router.
- ngrok — quick public HTTPS link for demos and sharing.
You can run one active tunnel per provider type. The header shows running tunnels and reminders before a link expires.
Stop sharing
Stop the tunnel in Settings or the header menu. Links can also expire automatically; renew or recover from the same screen when needed.
When to use which
| Scenario | Use |
|---|---|
| “I’m on my dev laptop; open Atmos from my phone browser on this machine” | Remote Access |
| “My code and agents should run on a VPS; my Mac only runs the UI” | Atmos Computer → Remote Build |
| “I already use Tailscale on this box” | Remote Access (Tailscale) |
| “No tunnel apps—I want the UI to talk to a server in the cloud” | Atmos Computer |
Related
- Atmos Computer — relay-based remote machines (no tunnel)
- Remote Build — register and connect workflow