exe.dev

HostedPersistent environment

Build apps or SSH into a persistent Linux VM.

Homepage Docs Pricing

Scanned 8 Oct 2026 · Schema v5 · features v21

From: $15/mo
subscription plus capacity-hour and storage/bandwidth overages
Free tier: No
Card requirement unconfirmed.
Isolation: Virtual machine
hypervisor, or nothing at all
Regions: 9
Oregon, US (not accepting new accounts; some VMs in LAX) · Los Angeles, US · New York, US · Dallas, US · Frankfurt, Germany · Tokyo, Japan +3
Capabilities: 27 / 61
4 partial · 30 fail · 0 not assessed
Agent readiness: 10/11 · 8/11
read · drive, pre-login surface

Advertised for

AI agent environments · GitHub actions runners · Notebooks · Dev staging · Demos

Built for

Developers, then semi-technical builders

· Hero IS the command: title 'exe.dev - ssh exe.dev'
· Programmatic access via SSH + HTTPS API
· Vocabulary: VMs, regions, proxies, Docker registries

01 Pricing subscription plus capacity-hour and storage/bandwidth overages

Tier	EntryPersonal 2 vCPU	Personal 4 vCPU	Personal 8 vCPU	Personal 16 vCPU	Work	TopEnterprise
Price	$15/month	$35/month	$75/month	$155/month	$75/month; eligible new teams $37.50/month for first 3 months	Custom
Includes	2 vCPU / 4 GiB shared across up to 50 VMs	4 vCPU / 8 GiB shared across up to 50 VMs	8 vCPU / 16 GiB shared across up to 50 VMs	16 vCPU / 32 GiB shared across up to 50 VMs	2 vCPU / 4 GiB shared capacity; unlimited team members and SSO	Dedicated hardware, AWS/GCP VPC, custom limits/support
Seats	1	1	1	1	—	—
Transfer	200 GB	200 GB	200 GB	200 GB	100 GB	—
Storage	100 GB	200 GB	400 GB	800 GB	100 GB	—
Instances	50	50	50	50	—	—
Transfer overage	$0.05/GB	$0.05/GB	$0.05/GB	$0.05/GB	$0.05/GB	—
Storage overage	$0.08/GB	$0.08/GB	$0.08/GB	$0.08/GB	$0.08/GB	—

account/team-month plus 2-vCPU/4-GiB unit-hour·Card required: unconfirmed·exe.dev

Overages: Disk $0.08/GiB-month; outbound $0.05/GiB; additional Work or standalone capacity $0.105 per 2-vCPU/4-GiB unit-hour.

02 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Virtual machinehypervisor, or nothing at all

Persistence

Yes

Snapshots / forks

Yes

Resources & limits

Storage

Personal: 100 GiB per 2 vCPU; Work pool allowance scales with capacity. Extra disk $0.08/GiB-month.

Limits & quotas

Personal: 50 pooled VMs sharing 2–16 vCPU / 4–32 GiB; standalone limit 50. Work: 25 VMs/vCPU up to 1,000/pool; standalone limit 100. Capacity is shared, not per VM.

GPU

Access

Deploy interface

sshhttps-apimcp

SDK languages

None

Network & secrets

Egress controls

not documented

Secrets

Yes

Bring your own cloud

enterprise-only

Placement & use

Jurisdiction

USUKJapanGermanyAustraliaSingapore

Advertised workloads

AI agent environmentsGitHub actions runnersNotebooksDev stagingDemos

03 Capabilities 27 pass · 4 partial · 30 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 4/11

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Partially supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 5/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Supported

Custom domainsBring-your-own domain via CNAME/DNS.

Supported

Public preview URLsShareable per-deploy / per-branch URLs.

Supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Not supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Not supported

Email send / receiveSend and/or receive email from the workload.

Supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 4/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Not supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Not supported

SSH accessDirect SSH into workloads.

Supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not supported

Git deployDeploy from a Git repo / push-to-deploy.

Not supported

Private container registryHosted private image registry.

Supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 8/12

Built-in coding agentShips a first-party AI coding agent in the product.

Supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Supported

BYOK for LLMsBring-your-own LLM provider keys.

Supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Supported

Data 0/4

First-party databasePlatform-provided managed database.

Not supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Not supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 0/6

Scheduled tasksCron / scheduled job primitive.

Not supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Partially supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Not supported

Organisation & security 6/9

Built-in authPlatform-provided authentication / IAM for workloads.

Supported

SSO / SAMLEnterprise single sign-on.

Supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Supported

BYOCRuns inside the customer's own cloud account.

Partially supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Partially supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

04 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

10/11

8 full · 2 partial · 91% of applicable checks

llms.txt
Supported
“Structured docs index fetched successfully, 12,684 bytes.”
llms-full.txt
Supported
“Comprehensive docs fetched, 382,794 bytes; retained as pointer plus individual docs.”
robots.txt AI policy
Partially supported
“robots.txt: 'User-agent: * / Allow: /' — permissive but no AI-UA-specific allow”
JSON-LD
Not supported
“0 application/ld+json blocks on homepage”
Sitemap
Supported
“Non-trivial sitemap fetched, 12,930 bytes.”
Meta tags
Supported
“title + og:title/description/image/url/type all present”
Markdown negotiation
Partially supported
“Homepage and docs Accept:text/markdown responses remain HTML; linked .md pages provide clean markdown.”
Content efficiency
Supported
“2451 readable characters / 12859 HTML bytes; exceeds 5%.”
Docs discoverable
Supported
“Docs first-class (/docs 200, /docs.md 200, footer + nav links)”
Machine-readable pricing
Supported
“Structured Personal/Work/Enterprise table including capacity, allowances and overages.”
No anti-bot wall
Supported
“Public homepage, pricing and linked docs fetched without challenges.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

8/11

4 full · 4 partial · 73% of applicable checks

Public API
Supported
“/docs/api (SSH) + /docs/https-api documented”
OpenAPI spec
Not supported
“/openapi.json 404; no openapi/swagger in docs”
MCP server
Supported
“https://exe.dev/docs/mcp documents Model Context Protocol endpoint https://exe.dev/mcp; well-known discovery not required.”
SDK packages
Not supported
“No client SDK advertised; 'npm/sdk' mentions refer to in-VM usage, not exe.dev SDKs”
Auth documented
Supported
“/docs/https-api-local-key + /docs/https-tokens-for-vms document token auth”
Self-serve credentials
Partially supported
“Local SSH-key-signed token creation documented; account/billing is a human step (Phase 2 to attempt)”
Webhooks
Not supported
“No first-party lifecycle event webhooks documented; integrations consuming third-party webhooks do not qualify.”
CLI tool
Supported
“SSH-native CLI: ssh exe.dev with ls/new/rm/restart”
Error model
Partially supported
“Errors documented incl. '### Rate limited (429)'; no confirmed JSON error schema”
Rate limits documented
Partially supported
“'### Rate limited (429)' section present; full limits/headers not confirmed”
Agent config files
Partially supported
“Published agent skill documented at /docs/agent-skill; one configuration surface.”

05 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 3

Claude Code Anthropic
Supported
“The default exeuntu image ships with claude, codex, and pi pre-installed.”
Source exe.dev
Codex CLI OpenAI
Supported
“The default exeuntu image ships with claude, codex, and pi pre-installed.”
Source exe.dev
Pi earendil-works
Supported
“The default exeuntu image ships with claude, codex, and pi pre-installed.”
Source exe.dev

Plausible compatibility 12

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

Aider
Amp
Antigravity
Devin
Droid
Gemini CLI
Goose
Hermes Agent
Kilo Code
Kiro CLI
OpenCode
Qwen Code

06 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 0

No attestations found on the public surface. Empty means nothing is advertised, after checking, not that nothing was checked.

Regions 9

Oregon, US (not accepting new accounts; some VMs in LAX)PDX
Los Angeles, USLAX
New York, USNYC
Dallas, USDAL
Frankfurt, GermanyFRA
Tokyo, JapanTYO
Sydney, AustraliaSYD
SingaporeSGP
London, UKLON

Legal

Privacy notice Terms of service

07 Company & presence Facts only, not scored

Company

Headquarters: Bay Area
Founded: —
Team size: Small team; five people named
Hiring: unknown

Funding

2026-04-22Series A · $35 millionblog.exe.dev

Notable people

David Crawshaw: Tailscale co-founder and former CTO
Josh Bleecher Snyder: Go compiler/runtime contributor
Philip Zeyliger: formerly Airtable, Cloudera, Google and D. E. Shaw

Activity

Last release: Maintained release notes; no versioned release inferred exe.dev
Last blog post: 2026-10-08 — An Agent Over Your Shoulder blog.exe.dev

Presence 4

Links found on the public surface scanned; not an exhaustive search.

08 Sources & method How this entry was produced

Public surface only

Everything here was read from exe.dev's unauthenticated pages, docs, pricing and repository on 8 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Persistent environment products →