Agentic Index
boxd vs Morph Cloud (2026)
Both vendors last verified
Both can copy a running machine with its memory and processes, so an agent can try several paths from the same state, and they wrap that in different products. boxd forks a running KVM machine in under 200ms and sells each machine as a persistent computer with coding agents preinstalled, 128 integrations whose credentials stay outside the machine, TypeScript automations on schedules and events, and a live desktop where an agent drives a browser and a person can step in. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Morph Cloud snapshots, branches and restores whole VMs in under 250ms through its Infinibranch technology, and wraps them in devboxes that people and CLI agents share across an organization, open in VS Code or Cursor and expose as preview URLs, with instances that pause on a TTL and wake on HTTP or SSH. boxd bills in euros per second and runs in Frankfurt or New York or self hosted, while Morph bills in compute units at $0.05 each, with $40 and $250 monthly plans, and offers no choice of region. Choose boxd when agents need integrations and a browser on the machine, and Morph Cloud when the job is branching VM state and sharing workspaces with a team.
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. boxd and Morph Cloud are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,165 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose boxd if
- Agents should act in GitHub, Linear, Slack or Stripe through integrations whose credentials never enter the machine.
- Automations should run from the machine on schedules and on integration events such as a new issue or pull request.
- An agent should drive a real browser on the machine's desktop while a person watches and steps in.
- You need to choose where machines run, in Frankfurt or New York, or self host on your own KVM hosts.
- Machines should hibernate on their own after four idle hours and resume on the next request with processes intact.
Choose Morph Cloud if
- Your team works in shared devboxes started from templates, opened in VS Code or Cursor and shared live across the organization.
- An agent inside a devbox should manage only that devbox through a scoped agent token.
- GitHub Actions runners and S3 compatible volumes should draw on the same compute account as your agent VMs.
- You prefer a fixed monthly plan, $40 for 1,000 compute units, to pure usage billing.
- Instances should pause on a TTL and wake when an HTTP request or SSH session arrives.
| Feature | b boxd |
M Morph Cloud |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
boxdIntegrations & Tool Calling Agents on a machine act in outside systems through 128 integrations, including GitHub, Linear, Slack, Notion, Jira, Salesforce, HubSpot, Stripe and Zendesk, each with typed tools such as creating an issue or sending a message. A person connects an account once through the provider's consent screen, personally or as a shared connection for the whole organization, and the platform then makes each call on the machine's behalf, so the credential never enters the machine. The in machine run CLI and the @boxd/run SDK call these tools, and scripts reach any other API, database or cloud account with ordinary libraries. Sourcedocs.boxd.sh/guides/integrations/connectionsread 2026-11-05 |
||
|
Morph CloudIntegrations & Tool Calling 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 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
boxdWorkflow Orchestration Background jobs give automations a managed lifecycle. A script that registers a schedule or trigger runs as a job that survives reboots, waits for a missing connection instead of failing, and restarts with exponential backoff for up to five attempts before it is marked failed. boxd's fan out pattern has a coordinator create one machine per worker, run a coding agent headless in each and let a lead agent merge the reports, and a fork brings a machine's jobs along paused so nothing runs twice. The sequencing, branching and hand offs in that pattern are code the customer writes against the SDK, and boxd has no workflow graph, step model or multi agent runtime of its own. Sourcedocs.boxd.sh/guides/automations/jobsread 2026-11-05 |
||
|
Morph CloudWorkflow Orchestration 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 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
boxdTriggers & Channel Coverage Work reaches a machine on schedules, events and inbound requests. An automation registers durations or cron expressions with every() and subscribes to integration events with .on(), such as a new Linear issue or a pull request through the boxd GitHub App, and 36 integrations emit triggers. The platform holds the next due time and wakes a hibernated machine shortly before it, holds events that arrive while a machine wakes for up to 15 minutes, and fires a missed cron slot once on wake. A hibernated machine also wakes on the next HTTPS request, so an agent served from it answers webhooks at its own address. Sourcedocs.boxd.sh/guides/automations/scriptsread 2026-11-05 |
||
|
Morph CloudTriggers & Channel Coverage 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 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
boxdKnowledge Grounding & RAG No retrieval index, vector store or knowledge base over the customer's content comes with the platform. Files on a machine's disk, standalone disks that outlive a machine and data sets saved into a snapshot are storage the agent's code reads, not an index a query returns. Tools such as Notion, Confluence or Google Drive are searched through their own integrations, and any grounding layer is something the customer installs on the machine. Sourcedocs.boxd.sh/llms.txtread 2026-11-05 |
||
|
Morph CloudKnowledge Grounding & RAG 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 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
boxdMemory & State Persistence Machines keep their working state between sessions. A machine on standby resumes in under a millisecond and a hibernated one wakes with its memory and processes intact, and coding agent sessions live on the persistent disk, so a job delegated in the morning can be resumed interactively later. Forks, checkpoints and snapshots copy or rewind that state. Automations also get object(name), a named JSON store written on every assignment and restored on the next run, meant for cursors, dedup sets and counters. All of it is machine and script state the developer manages, with no memory layer of stated scope and lifetime that a buyer can review, edit or delete as memory. Sourcedocs.boxd.sh/guides/automations/scriptsread 2026-11-05 |
||
|
Morph CloudMemory & State Persistence 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 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
boxdHuman Oversight & Guardrails A person can step into an agent's work while it runs. Every machine has a live desktop in the browser where its owner watches the agent's browser, takes over the keyboard to enter a password, solve a captcha or fix a form, and hands control back without stopping the agent. The preinstalled coding agents are told to share that desktop link whenever they need someone, so a login or approval happens in the browser the agent already opened. There is no approval gate, pause primitive or policy that holds an agent's action until a person reviews it. Sourcedocs.boxd.sh/guides/desktopread 2026-11-05 |
||
|
Morph CloudHuman Oversight & Guardrails 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 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
boxdSecurity, Identity & Governance Organizations have three roles. Members use shared machines and create org billed ones, admins also invite and remove members, change roles, set defaults, create teams and revoke org API keys, and the single owner can demote admins. Admin invites need an interactive login, so an API key or a token minted inside a machine cannot send one. People sign in with GitHub or Google, with SAML single sign on offered to enterprise customers on request. A DPA is available, and SOC 2 Type II and ISO 27001 are both in progress, not held. Each machine is a KVM microVM with its own kernel, and egress allowlists and host bound secrets are enforced on the host, outside the machine. Sourcedocs.boxd.sh/guides/organizationsread 2026-11-05 |
||
|
Morph CloudSecurity, Identity & Governance 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 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
boxdObservability & Auditability Automations are visible and the agent's own steps are not. The console's Automations page lists every background job with its triggers in plain English, the integrations it uses, its state, last run and last error, plus a generated write up and flow diagram for each script, and run logs prints or follows a job's log from inside the machine. Regional uptime and incidents appear on a public status page. A coding agent's prompts, tool calls and outputs are not traced by the platform, and no audit trail of member actions is offered. Sourcedocs.boxd.sh/guides/automations/jobsread 2026-11-05 |
||
|
Morph CloudObservability & Auditability 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 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
boxdDeployment & Data Residency Each machine runs in Frankfurt or New York, picked per machine from the CLI, console or SDK or set as an organization default, and its disk, memory, snapshots, checkpoints and backups stay in that region on Latitude.sh bare metal. Scale customers can have boxd operate the cluster inside their own cloud account, and the same release self hosts on AWS, Google Cloud or any KVM host, free up to 16 worker vCPUs and licensed above that, with air gapped installs supported. boxd gives conflicting accounts of its US region, with New York live in some places and coming soon with a waitlist in others. Sourcedocs.boxd.sh/guides/regionsread 2026-11-05 |
||
|
Morph CloudDeployment & Data Residency 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 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
boxdPrebuilt Agents, Templates & Packs Machines arrive with Claude Code, Codex and OpenCode installed and configured through an instructions file that teaches each agent the platform, plus three preinstalled skills covering the in machine CLI, automations and the desktop, and a CLI skill for the laptop. Guides walk through development workspaces, preview environments, CI runners, personal assistants, sandboxes, agentic SaaS, RL environments and agent swarms, and connectors exist for open source tools such as TanStack AI, Pydantic AI, Harbor and Scale AI AgentEnv. These are configured third party agents and recipes a developer builds from, not prebuilt agents of boxd's own. Sourcedocs.boxd.sh/use-cases/coding-agentsread 2026-11-05 |
||
|
Morph CloudPrebuilt Agents, Templates & Packs 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 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
boxdModel Flexibility & Routing The customer decides which agents and models run. Claude Code and Codex use the customer's own subscription, signed in once and served to every private machine in the organization, or an API key stored as a secret, OpenCode signs in on each machine, and any other agent or model that runs on Linux can be installed. boxd adds no model of its own and does not route between providers, and it does not use customer data to train or improve any model. Sourcedocs.boxd.sh/use-cases/coding-agentsread 2026-11-05 |
||
|
Morph CloudModel Flexibility & Routing 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 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
boxdAPIs, SDKs & MCP Extensibility Outside code drives the platform through TypeScript and Python SDKs, a gRPC API whose full api.proto service definition is public for generating stubs in any language, and a CLI that returns JSON from its commands. Each region has its own API endpoint, and organization API keys keep working after the person who created them leaves. The SDKs cover machines, forks, snapshots, checkpoints, disks, egress, secrets, domains, organizations and teams, and a filesystem API reads and writes files inside a machine from code. Sourcedocs.boxd.sh/reference/grpc-apiread 2026-11-05 |
||
|
Morph CloudAPIs, SDKs & MCP Extensibility 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 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
boxdTesting, Debugging & Optimization There are no test cases, scoring or quality gates for an agent's behavior. The platform is where evaluations run, not how they are scored. Forks give every reinforcement learning rollout or benchmark trial a byte identical starting state, Moyai ran 279,577 Harbor benchmark machines on it, and a reproducibility check compares two forks run with the same seed, but rewards, datasets and scoring belong to the customer's own framework. Sourcedocs.boxd.sh/use-cases/reproducible-rl-environmentsread 2026-11-05 |
||
|
Morph CloudTesting, Debugging & Optimization 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 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
boxdBrowser & Computer Use Agents drive a real browser on the machine's own desktop. Every machine ships a browser automation CLI built for agents, backed by Chromium with anti bot fingerprinting and a persistent profile so logins stick, and scripts get the same browser through Playwright. A machine can also drive a Chrome window on the user's laptop over the DevTools protocol, for sites that only accept the user's own network, and the preinstalled agents get a browser tool for it automatically. Any GUI app installed on the machine opens on the same desktop. Sourcedocs.boxd.sh/guides/launch-a-browserread 2026-11-05 |
||
|
Morph CloudBrowser & Computer Use 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 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | b boxd |
M Morph Cloud |
|---|---|---|
|
Entry price Lowest public entry point |
Pay as you go with €30 of free credit, at €0.039 per active vCPU hour and €0.012 per GiB hour of memory in use. | Free Developer tier with compute bought as Morph Compute Units at $0.05 each, where one MCU covers a vCPU hour with 4 GB of RAM and 16 GB of disk. |
|
Pricing confidence How public the numbers are |
Public, exact | Public, exact |
|
Billing Primary billing axis |
Per second active vCPU, memory in use and disk written | Morph Compute Units per hour, set by the largest of vCPUs, RAM per 4 GB and disk per 16 GB, plus snapshot and volume storage |
|
Variable cost Workload / overage exposure |
High variable cost | High variable cost |
|
Free tier / trial Try before you buy |
Free tier
|
No free tier
|
|
Buying motion Self-serve vs sales call |
Mixed | Self-serve |
|
Pricing verified When this pricing was last checked |
Morph Cloud is sold by Morph Labs, Inc. of San Francisco, which is not the company behind morphllm.com. Morph's terms offer third party attestations on request without naming one, and boxd's SOC 2 Type II and ISO 27001 certifications are still in progress. boxd gives conflicting accounts of its US region.
More comparisons with boxd or Morph Cloud
Other matchups in agent infrastructure platforms
Not the pairing you were after? These compare a different set of agent infrastructure platforms on the same 14 capabilities.