Documentation

1. Introduction

exe.dev HTTP Proxies — Publish to the Internet, both privately and publicly
Sharing — share it like it's hot
Customizing VMs — Three ways to customize your exe.dev VMs
Private Docker Registries — You can run a docker registry to distribute your own images. Or connect to an outside one.
Custom Domains — Use your own domain with exe.dev
Login with exe — Use exe.dev's authentication system in your applications
LLM Gateway — LLM tokens included
Regions — Available exe.dev regions
API — Programmatic access via SSH
HTTPS API — Programmatic access via HTTPS
HTTPS API Local Key Creation — Create API tokens locally by signing with your SSH key
HTTPS Tokens for VMs — Bearer tokens for programmatic access to VM HTTPS endpoints
Receive email — Receive emails to your VM
Send email — Send emails from your VM

What are Integrations? — Integrate exe.dev with other tools and services
HTTP Proxy Integration — Inject headers into HTTP requests from your VM
GitHub Integration — Connect your GitHub account to exe.dev for private repo access
Attaching Integrations — Attach integrations to VMs using direct attachment, tags, or auto-attach

What is the host key for exe.dev? — How to verify you're connecting to exe.dev
How do I use a specific SSH key for exe.dev? — Configure SSH to use a specific key
How do I connect VSCode to my VM? — Open your VM in VSCode
How do I copy files to/from my VM? — Transfer files with scp
Can I run docker images? — Running Docker on exe.dev VMs
How do you pronounce "exe"? — The official pronunciation
How do I access GitHub? How do I set up a minimal GitHub token? — GitHub access and fine-grained tokens
How do I connect from one VM to another? — SSH, Tailscale, and other tricks
How do I set up tab completion for VM names? — Autocomplete exe.xyz VM hostnames in your favorite shell
How does exe.dev work? — behind-the-scenes look
ssh exe.dev sometimes asks me to register — how to solve heisen-connection issues
I found an undocumented command! Can I use it? — Using undocumented commands
How do I run Next.js, Vite, or other JS dev servers on my VM? — Configure allowedDevOrigins (Next.js) or server.allowedHosts (Vite) so the dev server accepts requests from your exe.dev hostname.
Teach your coding agent to exe.dev — Agent skill and docs for coding agents

Intro — an open source reactive notebook
Dev, Test, Prod: Choose One, Two, or Three — You can build, test, and deploy on exe.dev.
Flue — Run Flue agentic apps on exe.dev
Forgejo — Self-hosted Git forge with exe.dev SSO
Gitea — Self-hosted Git forge with exe.dev SSO
Openclaw — Openclaw, formerly known as Moltbot, formerly known as Clawdbot
Running Agents — use exe.dev VMs as a sandbox
Running a self-hosted GitHub Actions Runner — log in easily into your CI environment
Spinning up a Marimo Notebook — an open source reactive notebook

Lock-in on exe.dev — It's just a computer. Of the Linux sort.
Persistent disks, not serverless — exe.dev is serverful, not serverless
Put your agent in a VM and let it be — Agent security is unsolved; a virtual machine is pragmatic
The GUTS Stack — Go, Unix, TypeScript, SQLite
Why exe.dev? — EXE is just a computer.