exe-staging.dev valid

exe.dev

Build apps or SSH into a persistent Linux VM. ssh exe.dev.

For agents: exe.dev provides persistent Linux VMs accessed over SSH, with HTTP proxies, integrations, team and enterprise plans, and a coding agent called Shelley.

linux vmssh accesshttp proxycloud developmentcoding agent

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T13:16:50.324Z. Cached copy · Source on exe-staging.dev

# exe.dev

> Build apps or SSH into a persistent Linux VM. ssh exe.dev.

## Key pages

- [Home](https://exe.dev/) - What exe.dev is and how to get started.
- [Documentation](https://exe-staging.dev/docs) - Guides for the CLI, VMs, browser access, and more.
- [API/CLI explorer](https://exe-staging.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.

## Introduction

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

## Features

- [exe.dev HTTP Proxies](https://exe-staging.dev/docs/proxy.md) - Publish to the Internet, both privately and publicly
- [Sharing](https://exe-staging.dev/docs/sharing.md) - Share a web app or grant trusted collaborators root access
- [VM pools](https://exe-staging.dev/docs/pools.md) - Reserved CPU and memory that a group of VMs shares
- [Migrating to pools](https://exe-staging.dev/docs/migrating-to-pools.md) - Move a team's existing VMs into pools after switching to Work
- [Standalone VMs (sandboxes)](https://exe-staging.dev/docs/standalone-vms.md) - Sandbox VMs with their own reserved vCPUs and memory, metered by the second
- [Customizing VMs](https://exe-staging.dev/docs/customization.md) - Three ways to customize your exe.dev VMs
- [Private Docker Registries](https://exe-staging.dev/docs/private-image.md) - Boot VMs from private images with --registry-auth, or pull private images inside a running VM with a registry integration.
- [Custom Domains](https://exe-staging.dev/docs/cnames.md) - Use your own domain with exe.dev
- [Login with exe](https://exe-staging.dev/docs/login-with-exe.md) - Use exe.dev's authentication system in your applications
- [LLM Gateway](https://exe-staging.dev/docs/shelley/llm-gateway.md) - Direct gateway deprecation and migration to LLM integrations
- [Regions](https://exe-staging.dev/docs/regions.md) - Available exe.dev regions
- [API](https://exe-staging.dev/docs/api.md) - Programmatic access via SSH
- [HTTPS API](https://exe-staging.dev/docs/https-api.md) - Programmatic access via HTTPS
- [HTTPS API Local Key Creation](https://exe-staging.dev/docs/https-api-local-key.md) - Create API tokens locally by signing with your SS
…

Related sites

Other listed sites in Infrastructure. See the whole category →

Machine-readable: GET /v1/resolve?q=exe-staging.dev · GET /v1/domain/exe-staging.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for exe-staging.dev:
1. POST https://agentwebmap.com/v1/sites/exe-staging.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://exe-staging.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/exe-staging.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/exe-staging.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.