Sources

exe.dev sources are first-party; competitor sources are each vendor’s own public pages. All were checked 2026-10-23 (America/New_York). Each docs page also has a Markdown version (append .md), and that’s what this guide’s /mcp endpoint fetches live. The guide is unofficial and isn’t affiliated with exe.dev.

How this guide was sourced

• Docs. The index is https://exe.dev/llms.txt, and every page listed there was read in its .md form.
• Pricing. https://exe.dev/pricing. The .md version of the pricing page returned 404 on 2026-10-23, so the HTML page was used.
• Derived figures. Numbers labeled derived are arithmetic on the prices below.
• Competitors. Only Linux-box alternatives (persistent machines you SSH into) are covered. Every competitor price or spec comes from the vendor’s own page or public API, listed below. Hetzner’s CX23 was shown as “not available” on 2026-10-23. Coder Premium and Ona have no public price, so none is quoted.
• [verify] badges. These mark statements the docs don’t settle, such as RPO/RTO for the streaming disk copy and how the included Work capacity applies across several pools.

exe.dev: Key pages

• Home: https://exe.dev/ (What exe.dev is and how to get started.)
• Documentation: https://exe.dev/docs (Guides for the CLI, VMs, browser access, and more.)
• API/CLI explorer: https://exe.dev/api (Try the exe.dev CLI and HTTPS API in an in-browser emulator.)
• Pricing: https://exe.dev/pricing (Plans for individuals, teams, and enterprises.)
• Blog: https://blog.exe.dev/ (Product updates and engineering notes.)

exe.dev: Introduction

• What is exe.dev?: https://exe.dev/docs/what-is-exe (VMs, on the internet, quickly)
• The exe Architecture: https://exe.dev/docs/architecture (Pools, local NVMe disks, and the proxies in front of your VMs)
• The exe infrastructure: https://exe.dev/docs/infrastructure (Where exe.dev’s servers run)
• Changelog: https://exe.dev/docs/release-notes (Keeping up with exe.dev changes)
• Deploy to exe: https://exe.dev/docs/deploy-to-exe (Step-by-step recipes for shipping software on exe.dev)
• Migrating to exe: https://exe.dev/docs/migrating-to-exe (How to move workloads over onto exe)
• Getting Help: https://exe.dev/docs/getting-help (How to get support for exe.dev)

exe.dev: Features

• exe.dev HTTP Proxies: https://exe.dev/docs/proxy (Publish to the Internet, both privately and publicly)
• Sharing: https://exe.dev/docs/sharing (Share a web app or grant trusted collaborators root access)
• VM pools: https://exe.dev/docs/pools (Reserved CPU and memory that a group of VMs shares)
• Migrating to pools: https://exe.dev/docs/migrating-to-pools (Move a team’s existing VMs into pools after switching to Work)
• Standalone VMs (sandboxes): https://exe.dev/docs/standalone-vms (Sandbox VMs with their own reserved vCPUs and memory, metered by the second)
• Customizing VMs: https://exe.dev/docs/customization (Three ways to customize your exe.dev VMs)
• Private Docker Registries: https://exe.dev/docs/private-image (Boot VMs from private images with, registry-auth, or pull private images inside a running VM with a registry integration.)
• Custom Domains: https://exe.dev/docs/cnames (Use your own domain with exe.dev)
• Login with exe: https://exe.dev/docs/login-with-exe (Use exe.dev’s authentication system in your applications)
• LLM Gateway: https://exe.dev/docs/shelley/llm-gateway (Direct gateway deprecation and migration to LLM integrations)
• Regions: https://exe.dev/docs/regions (Available exe.dev regions)
• API: https://exe.dev/docs/api (Programmatic access via SSH)
• HTTPS API: https://exe.dev/docs/https-api (Programmatic access via HTTPS)
• HTTPS API Local Key Creation: https://exe.dev/docs/https-api-local-key (Create API tokens locally by signing with your SSH key)
• HTTPS API: Run commands on VM: https://exe.dev/docs/https-api-run-on-vm (Run commands inside your VMs over the HTTPS API)
• HTTPS Tokens for VMs: https://exe.dev/docs/https-tokens-for-vms (Bearer tokens for programmatic access to VM HTTPS endpoints)
• VM-scoped SSH keys: https://exe.dev/docs/vm-scoped-ssh-keys (SSH keys limited to a single VM)
• Egress policy: https://exe.dev/docs/internet-access (Restrict a VM’s outbound network access)
• MCP Server: https://exe.dev/docs/mcp (Connect Claude Code and other agents to exe.dev over the Model Context Protocol)
• Receive email: https://exe.dev/docs/receive-email (Receive emails to your VM)
• Send email: https://exe.dev/docs/send-email (Send emails from your VM)
• Invites: https://exe.dev/docs/invites (Trial invites and invite rewards)

exe.dev: Integrations

• What are Integrations?: https://exe.dev/docs/integrations (Integrate exe.dev with other tools and services)
• HTTP Proxy Integration: https://exe.dev/docs/integrations-http-proxy (Inject headers into HTTP requests from your VM)
• Integration catalog: https://exe.dev/docs/integrations-catalog (Services available through exe.dev catalog integrations)
• GitHub Integration: https://exe.dev/docs/integrations-github (Connect your GitHub account to exe.dev for private repo access)
• LLM Integration: https://exe.dev/docs/integrations-llm (Configure managed, API-key, ChatGPT-backed, or custom HTTPS model providers)
• AWS Workload Identity Federation: https://exe.dev/docs/integrations-aws-wif (Configure exe.dev Identity Federation so VMs can assume AWS IAM roles)
• GCP Workload Identity Federation: https://exe.dev/docs/integrations-gcp-wif (Configure exe.dev Identity Federation so VMs can impersonate Google Cloud service accounts)
• Reflection Integration: https://exe.dev/docs/integrations-reflection (Discover metadata and integrations from inside the VM)
• Anthropic Workload Identity Federation: https://exe.dev/docs/integrations-anthropic-wif (Call the Claude API from exe.dev VMs without an Anthropic API key)
• Attaching Integrations: https://exe.dev/docs/integrations-attach (Attach integrations to VMs using direct attachment, tags, or auto-attach)
• OpenAI Workload Identity Federation: https://exe.dev/docs/integrations-openai-wif (Call the OpenAI API from exe.dev VMs without an OpenAI API key)
• Tailscale Workload Identity Federation: https://exe.dev/docs/integrations-tailscale-wif (Put exe.dev VMs on your Tailscale network, or let them call the Tailscale API, without copying keys onto them)
• Slack Integration: https://exe.dev/docs/integrations-slack (Send messages from your VM to a Slack channel)
• Slack Bot Integration: https://exe.dev/docs/integrations-slack-bot (Run a full two-way Slack bot from your VM, with the tokens held off-VM)
• Discord Integration: https://exe.dev/docs/integrations-discord (Send messages from your VM to a Discord channel)
• Discord Bot Integration: https://exe.dev/docs/integrations-discord-bot (Drive your own Discord bot from a VM, with the bot token held off-VM)
• VM-to-VM Integration: https://exe.dev/docs/integrations-vm-to-vm (Let one VM call another over HTTPS, with a generated key injected at the edge)
• Token-Mint Integrations: https://exe.dev/docs/integrations-token-mint (Exchange a vaulted credential for a short-lived token your VM can use)
• Container Registry Integrations: https://exe.dev/docs/integrations-oci-registries (Mint short-lived pull tokens for OCI registries (quay.io, ghcr.io, atcr.io, pkg.dev))

exe.dev: Enterprise

• Enterprise exe: https://exe.dev/docs/enterprise (exe.dev for companies, with custom limits, dedicated hardware, and contract pricing)
• Single tenant hardware: https://exe.dev/docs/enterprise-single-tenant (Servers that run your team’s VMs and no one else’s)
• BYOC: https://exe.dev/docs/enterprise-byoc (Bring your own cloud, and run exe.dev on servers you own)
• SLA: https://exe.dev/docs/enterprise-sla (Enterprise uptime and support commitments, and service credits)

exe.dev: Shelley

• What is Shelley?: https://exe.dev/docs/shelley/intro (Our coding agent)
• Unique Features: https://exe.dev/docs/shelley/unique (How Shelley differs from other coding agents)
• Bring Your Own Key: https://exe.dev/docs/shelley/byok (Use your own API keys with Shelley)
• AGENTS.md: https://exe.dev/docs/shelley/agents-md (Guidance files for Shelley)
• Upgrading Shelley: https://exe.dev/docs/shelley/upgrading (Keep Shelley up to date)

exe.dev: Teams

• Teams: https://exe.dev/docs/teams/overview (Shared VM management for your organization)
• Managing Members: https://exe.dev/docs/teams/members (Create a team, invite people, manage roles)
• Team VMs: https://exe.dev/docs/teams/vms (How VMs work within a team)
• Sharing controls: https://exe.dev/docs/teams/sharing-controls (Restrict who can share team VMs publicly or with external users)
• Shelley: https://exe.dev/docs/teams/shelley (How Shelley credits work for team members)
• Team SSO: https://exe.dev/docs/teams/sso (Set up Google OAuth or OIDC for your team)

exe.dev: Billing

• Overview: https://exe.dev/docs/billing/overview (Personal, Work, and Enterprise plans, and how exe.dev bills)
• Personal plan: https://exe.dev/docs/billing/personal (One account’s shared capacity, from 2 to 16 vCPU)
• Work plan: https://exe.dev/docs/billing/work (One team subscription with included pool capacity and hourly metering)
• Subscriptions: https://exe.dev/docs/billing/subscriptions (Changing capacity, switching plans, and cancelling)
• Usage: https://exe.dev/docs/billing/usage (Included disk and bandwidth, and how usage beyond them is measured)
• Individual plan (legacy): https://exe.dev/docs/billing/individual (The earlier single-account plan, for existing subscribers)
• Team plan (legacy): https://exe.dev/docs/billing/team (The earlier per-member team plan, for existing subscribers)

exe.dev: FAQ

• What is the host key for exe.dev?: https://exe.dev/docs/faq/host-key (How to verify you’re connecting to exe.dev)
• How do I use a specific SSH key for exe.dev? How do I manage multiple exe.dev accounts?: https://exe.dev/docs/faq/ssh-key (Configure SSH to use a specific key)
• How do I connect VSCode to my VM?: https://exe.dev/docs/faq/vscode (Open your VM in VSCode)
• How do I copy files to/from my VM?: https://exe.dev/docs/faq/copy-files (Transfer files with scp)
• How do I write my VM’s SSH destination?: https://exe.dev/docs/faq/ssh-destination (my-vm.exe.xyz or vm+my-vm@vm.exe.xyz)
• Can I run docker images?: https://exe.dev/docs/faq/docker (Running Docker on exe.dev VMs)
• How do you pronounce “exe”?: https://exe.dev/docs/faq/pronunciation (The official pronunciation)
• How do I access GitHub? How do I set up a minimal GitHub token?: https://exe.dev/docs/faq/github-token (GitHub access and fine-grained tokens)
• How do I connect from one VM to another?: https://exe.dev/docs/faq/cross-vm-networking (SSH, Tailscale, and other tricks)
• How do I set up tab completion for VM names?: https://exe.dev/docs/faq/tab-completion (Autocomplete exe.xyz VM hostnames in your favorite shell)
• How does exe.dev work?: https://exe.dev/docs/faq/how-exedev-works (behind-the-scenes look)
• ssh exe.dev sometimes asks me to register: https://exe.dev/docs/faq/heisen-connect (how to solve heisen-connection issues)
• I found an undocumented command! Can I use it?: https://exe.dev/docs/faq/undocumented (Using undocumented commands)
• How do I run Next.js, Vite, or other JS dev servers on my VM?: https://exe.dev/docs/faq/nextjs-and-friends (Configure allowedDevOrigins (Next.js) or server.allowedHosts (Vite) so the dev server accepts requests from your exe.dev hostname.)
• How does exe.dev measure disk usage?: https://exe.dev/docs/faq/disk-usage (Disk usage is measured as ext4 filesystem usage.)
• Teach your coding agent to exe.dev: https://exe.dev/docs/agent-skill (Agent skill and docs for coding agents)

exe.dev: Editorials

• Lock-in on exe.dev: https://exe.dev/docs/lockin (It’s just a computer. Of the Linux sort.)
• Persistent disks, not serverless: https://exe.dev/docs/serverful (exe.dev is serverful, not serverless)
• Put your agent in a VM and let it be: https://exe.dev/docs/boxes (Agent security is unsolved; a virtual machine is pragmatic)
• The GUTS Stack: https://exe.dev/docs/guts (Go, Unix, TypeScript, SQLite)
• Why exe.dev?: https://exe.dev/docs/why-exe (EXE is just a computer.)

exe.dev: Other

• Help & Community: https://exe.dev/docs/community (Join our Discord)
• Privacy Notice: https://exe.dev/docs/privacy-notice (How exe.dev handles your data)
• Terms of Service: https://exe.dev/docs/terms-of-service (Terms and conditions for using exe.dev)
• Sub-processors: https://exe.dev/docs/sub-processors (Third parties that process personal data on behalf of exe.dev)

exe.dev: Long Tail

• What are long tail docs?: https://exe.dev/docs/what-are-long-tail-docs
• Repo buttons: https://exe.dev/docs/repo-buttons (Add “Deploy on exe.dev” and “Build with Shelley” buttons to your README)
• Suggest links: https://exe.dev/docs/suggest-links (Pre-filled command runners at https://exe.dev/suggest)
• Updating coding agents on an exe.dev VM: https://exe.dev/docs/upgrade-codex (How to update Claude Code, Codex, and Pi on the exeuntu image)

Competitors (vendor pages, checked 2026-10-23)

• Fly.io resource pricing: https://fly.io/docs/about/pricing/
• Hetzner Cloud Cost-Optimized: https://www.hetzner.com/cloud/cost-optimized
• DigitalOcean Droplet pricing: https://docs.digitalocean.com/products/droplets/details/pricing/
• Linode/Akamai public price API: https://api.linode.com/v4/linode/types
• Linode/Akamai pricing page: https://www.linode.com/pricing/
• Vultr pricing: https://www.vultr.com/pricing/
• AWS Lightsail pricing: https://aws.amazon.com/lightsail/pricing/
• GitHub Codespaces billing: https://docs.github.com/en/billing/concepts/product-billing/github-codespaces
• GitHub Codespaces timeout: https://docs.github.com/en/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces
• Ona (formerly Gitpod) overview: https://ona.com/docs/ona/getting-started
• Ona archive and auto-delete: https://ona.com/docs/ona/environments/archive-auto-delete
• Coder pricing: https://coder.com/pricing
• Daytona pricing: https://www.daytona.io/pricing
• Daytona sandboxes: https://www.daytona.io/docs/en/sandboxes.md
• Tailscale Funnel: https://tailscale.com/kb/1223/funnel
• Tailscale pricing: https://tailscale.com/pricing
• Cloudflare Tunnel: https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/

Other first-party references

• exe.dev public repo (agent skill, plugins, ssh config generator): https://github.com/boldsoftware/exe.dev
• exeuntu default image: https://github.com/boldsoftware/exeuntu
• exe.dev MCP server: https://exe.dev/mcp
• Shelley credits: https://exe.dev/user/shelley
• Discord: https://discord.gg/jc9WQUfaxf

Branding

The nixfred hexagon logo is copied unchanged from the nixfredOS repo brand/ folder.