Connect an environment
An environment is one machine running SkyPilot, joined to your hosted console through a private tunnel. Connecting takes three steps and one line on your box.
1. Create the environment in the console
Sign in at app.slipstreamcompute.com and click Connect. Give the environment a name (e.g. prod-cluster) and pick a mode:
- Attach existing SkyPilot — you already run a SkyPilot API server. The tunnel fronts it at
http://localhost:46580(SkyPilot's default). - Deploy SkyPilot for me — the installer also installs SkyPilot and starts the API server before connecting.
Slipstream provisions an isolated Cloudflare Tunnel and shows you a one-time command. The token in it is displayed once — copy it now.
2. Run the one line on your machine
On the box that runs (or will run) SkyPilot, paste the command the console gave you. Attach mode looks like:
curl -fsSL https://slipstreamcompute.com/install.sh | sh -s -- \ --token <YOUR_TOKEN> --attach http://localhost:46580
Deploy mode swaps the last flag for --deploy:
curl -fsSL https://slipstreamcompute.com/install.sh | sh -s -- \ --token <YOUR_TOKEN> --deploy
The script installs cloudflared if needed (Homebrew on macOS; a direct binary on Linux), then registers it as a background service so the connection survives logout and reboot. It needs sudo to install that service. The connection is outbound-only — no inbound ports are opened and there's no VPN.
3. Confirm it's connected
Back in the console, the environment flips to ● Connected within a few seconds (status comes from Cloudflare's live tunnel state). Click Open dashboard on the row to load your SkyPilot dashboard, proxied through the tunnel behind single sign-on.
Managing the background service
The connector runs as a system service. To inspect or control it on the box:
# Linux (systemd) sudo systemctl status cloudflared sudo systemctl stop cloudflared sudo systemctl start cloudflared # macOS (launchd) sudo launchctl list | grep cloudflared
Done with this machine? See Disconnect & remove.
← All docs