E2B vs Morph Cloud (2026)

An agent in a sandbox reaches other systems through a built in MCP gateway that runs inside the sandbox and exposes more than 200 tools from the Docker MCP Catalog (Airtable, GitHub, Browserbase, Exa and others) or custom MCP servers through one interface. Credentials are passed as secrets that resolve at egress instead of living in the sandbox.

Sourcedocs.e2b.dev/mcp-gatewayread 2026-11-03

An agent on Morph reaches outside systems through what runs in its VM. Secrets stored in the Morph account come preconfigured in devboxes, an agent token can let the agent read and write its own devbox's secrets, and volumes serve shared files to any S3 client. There are no connectors, tool catalog or MCP gateway for an agent to call.

Sourcecloud.morph.so/docs/devboxes/agent-tokensread 2026-11-05

There is no workflow logic in E2B itself. The customer brings its own orchestration framework, and E2B provides the machine an agent's steps run on (commands, background processes, code contexts), not a runtime that sequences, branches, retries or routes those steps. Forking a sandbox copies its state, which is compute, not workflow logic.

Sourcee2b.dev/llms.txtread 2026-11-03

There is no workflow logic in Morph Cloud. Branching copies a running instance into many that continue from the same state, and TTLs stop or pause instances on a timer, but sequencing, retrying and routing an agent's steps stay in the customer's own code, which builds any fan out on these primitives.

Sourcecloud.morph.so/docs/concepts/mental-modelread 2026-11-05

A sandbox can start without the customer's code calling it. With auto resume set, a paused sandbox resumes when activity arrives, so an agent served from a sandbox starts on an inbound request, and E2B's guides deploy agent gateways this way, for example OpenClaw answering Telegram. Sandbox lifecycle events are also pushed to the customer's webhook, signed. There is no scheduler.

Sourcedocs.e2b.dev/sandbox/auto-resumeread 2026-11-03

A paused instance wakes without the customer's code calling it. With wake on HTTP, a request to an exposed service resumes the instance, and wake on SSH does the same for SSH sessions and exec calls, so an agent served from a Morph workspace starts when traffic arrives and pauses again when its TTL runs out. Morph's own guide builds agent workspaces this way. There is no scheduler or webhook.

Sourcecloud.morph.so/docs/documentation/instances/wake-onread 2026-11-05

There is no retrieval structure over the customer's content, since E2B runs the agent's code. Files uploaded to a sandbox or volume are storage the agent's code can read, not an index a query returns, and the MCP gateway's tools reach outside knowledge sources owned by others.

Sourcee2b.dev/llms.txtread 2026-11-03

No retrieval index or knowledge base over the customer's content comes with the platform. Volumes and the VM filesystem hold files an agent's code reads, and any retrieval runs as the customer's own software inside the instance.

Sourcecloud.morph.so/docs/documentation/overviewread 2026-11-05

An agent's working state carries across sessions. A paused sandbox resumes exactly as it was, with filesystem and memory, running processes and loaded variables, and is kept until it is killed. Snapshots and forks copy that state, volumes, in private beta, keep files across sandboxes, and code contexts keep interpreter variables between executions, which the agent's code reads to continue its task. This is machine state the developer manages, with no memory layer of stated types or scope that can be reviewed, edited or deleted as memory.

Sourcedocs.e2b.dev/sandbox/persistenceread 2026-11-03

An agent's working state carries across sessions as machine state. A paused instance resumes with its memory intact, and a snapshot captures the whole running machine, processes included, so an instance booted from it carries on where the original stopped. Snapshot TTLs set how long saved states are kept, and volumes hold caches, checkpoints and datasets. This is machine state the developer manages, with no memory layer of stated scope that can be reviewed or deleted as memory.

Sourcecloud.morph.so/docs/developersread 2026-11-05

There is no approval step, consent checkpoint or escalation to a person for work inside an E2B sandbox. Egress control (allow and deny lists for each sandbox, a proxy the customer runs that fails closed, and access tokens on public URLs) limits what an agent's code can reach, but that is isolation the developer configures, not a point where a person reviews the agent's action.

Sourcee2b.dev/enterpriseread 2026-11-03

Work in an instance has no approval step, consent checkpoint or escalation to a person. People can watch and step in by hand, since devboxes are shared live with the organization and open in VS Code, Cursor or a terminal over SSH, and a remote desktop guide serves a Linux desktop in the browser. Agent tokens limit what an agent can do to its own devbox but do not hold an action for review.

Sourcecloud.morph.so/docs/devboxes/sharing-and-collaborationread 2026-11-05

E2B holds SOC 2 Type II, with the report under NDA in its trust center at trust.e2b.dev, and signs HIPAA Business Associate Agreements on Enterprise plans. Its controls protect the sandbox. Every sandbox is its own Firecracker microVM with its own kernel, egress can be allowed or denied for each sandbox, secrets are injected at the egress proxy so no sandbox holds them, and public sandbox URLs can require an access token. Who inside a customer's organization can do what has no published control yet, since E2B lists single sign on, SCIM and role based access as planned.

Sourcee2b.dev/securityread 2026-11-03

Organizations have admin and member roles with invitations, and one account can belong to several organizations. API keys act for the user, agent tokens confine an agent to one devbox and a set of scopes such as snapshots, HTTP services and secrets, and SSH public keys are registered with expiry dates, with an organization view of which keys have access. Morph's terms commit to encryption in transit and at rest, least privilege access and audit logging, and offer third party attestations such as SOC reports on request, with no certification named.

Sourcecloud.morph.so/web/legal/terms-of-serviceread 2026-11-05

The record covers the sandbox, not the agent. Every lifecycle event is available through an events API and delivered as a signed webhook, sandbox metrics report CPU and memory use, template builds keep logs, and on Enterprise OpenTelemetry metrics and logs export to the customer's OTLP endpoint. Prompts, tool calls, retrieved knowledge and outputs cannot be inspected step by step in E2B, since the agent's reasoning runs outside the sandbox, and there is no audit log of user actions apart from the runtime.

Sourcee2b.dev/enterpriseread 2026-11-03

The machine is measured and the agent is not. Each instance reports point in time CPU and memory use, usage and quota APIs break consumption down by service, command output streams back from exec calls, organizations can review which SSH keys have access, and the GitHub Actions console streams live events and logs for CI runs. Nothing traces or logs the steps an agent takes.

Sourcecloud.morph.so/docs/api-reference/get-instance-metrics-instance-instance-id-metrics-getread 2026-11-05

Three deployment modes share the same SDK, CLI and API. E2B Cloud defaults to Google Cloud us-west1, and AWS us-west-2 and us-east-1 and Google Cloud europe-west1 and asia-southeast1 are available on request on every plan. With BYOC on AWS, Google Cloud or Azure on Enterprise, the data plane runs in the customer's own cloud account. E2B Embed packages the Apache-2.0 runtime for a single node self hosted install, and a private cloud option is in development.

Sourcedocs.e2b.dev/faq/egress-ip-rangesread 2026-11-03

Morph Cloud runs as a hosted service with no choice of region and no self hosted or customer cloud option, even though Morph's terms refer to region availability.

Sourcecloud.morph.so/docs/documentation/overviewread 2026-11-05

Starting points ship with the platform, including sandbox templates for Claude Code, a desktop, Docker and web app stacks, a cookbook of examples ready to run, setup guides for more than thirty agents and frameworks, and open source reference apps, Surf, a computer use agent, and Fragments, a builder that turns a prompt into an app. These are environments and examples a developer builds from, not a browsable catalog of agents a customer adopts.

Sourcedocs.e2b.dev/llms.txtread 2026-11-03

Starting points come as templates and guides. Devbox templates bundle a base snapshot, build steps and integrations and can be shared with teammates by a short alias, and guides set up Claude Code workspaces, a browser based Linux desktop, Docker BuildKit, build caches and GitHub Actions runners. These are environments a developer builds from, not prebuilt agents a business adopts.

Sourcecloud.morph.so/docs/examples/claude-coderead 2026-11-05

Compute is what E2B provides for agents, with the customer bringing its own model and orchestration framework. Sandboxes connect to any LLM and to agents and frameworks such as Claude Code, Codex, the OpenAI Agents SDK, the Vercel AI SDK, LangChain, CrewAI, Mastra and Google ADK. E2B imposes no model, so model choice stays with the customer.

Sourcee2b.dev/llms.txtread 2026-11-03

The customer chooses the agents and models that run on Morph. Any CLI agent can run in a devbox, Morph's guide installs Claude Code with the customer's own Anthropic key, and model calls happen in the customer's code. Morph supplies the machines, not the models.

Sourcecloud.morph.so/docs/examples/claude-coderead 2026-11-05

Outside systems can call E2B through Python and JavaScript/TypeScript SDKs, a CLI, a REST API described by a published OpenAPI 3.1 specification, and custom sandbox templates the customer builds, tags and versions. A public MCP server serves E2B's documentation to agents.

Sourcee2b.dev/llms.txtread 2026-11-03

Morph Cloud is driven through a REST API with a public OpenAPI specification, Python and TypeScript SDKs and the morphcloud CLI, which cover images, snapshots, instances, branching, devboxes, volumes, organizations, secrets, usage and SSH keys, and the CLI accepts plugins. Morph offers no MCP server.

Sourcecloud.morph.so/docs/api-referenceread 2026-11-05

There are no fixtures, scoring, quality gates or comparison of agent runs. E2B is where evaluations and reinforcement learning run, not how they are scored. It lists reinforcement learning among its workloads and runs NVIDIA NeMo Gym environments in sandboxes, but the datasets, reward functions and scoring belong to the customer's framework.

Sourcee2b.dev/llms.txtread 2026-11-03

There are no test cases, scoring or quality gates for an agent's behavior. Morph presents faster agent evaluations and capturing the exact state of a failed CI run as uses of snapshots and branching, with the datasets and scoring left to the customer's own harness.

Sourcecloud.morph.so/docs/developersread 2026-11-05

Agents control real desktops hosted by E2B. E2B Desktop sandboxes are Ubuntu machines with an XFCE desktop and preinstalled applications, and the Desktop SDK gives the agent screenshots, mouse, keyboard and scroll, with a live VNC stream so a person can watch. A cloud browser can also run in a sandbox, and Surf is E2B's open source computer use agent built on it.

Sourcedocs.e2b.dev/use-cases/computer-useread 2026-11-03

No browser or desktop for an agent to drive comes with the platform. Morph's remote desktop guide installs an XFCE desktop with VNC and a noVNC web client so people can use it in the browser, and an agent that needs a browser installs and drives one itself inside the VM.

Sourcecloud.morph.so/docs/examples/remote-desktopread 2026-11-05