Agent Sandboxesagentsandboxes.org
Head-to-head

HopX vs Novita Agent Sandbox

Answer in brief

Choose HopX for pay-per-second microVM sandboxes with desktop automation and no session limits; choose Novita Agent Sandbox for cheap per-second code execution and browser-agent runs with pause/resume on a single US region. HopX uses Firecracker microVM isolation; Novita Agent Sandbox uses Not documented isolation.

By the Agent Sandboxes editors · Updated

Key differences between HopX and Novita Agent Sandbox

  • Session length: No cap (HopX) versus 1 h free / 24 h paid (Novita Agent Sandbox).
  • SDKs and interfaces: Only HopX lists REST API and MCP server.

What they have in common

  • Both are hosted platforms.
  • Neither is open source.
  • Both can pause and resume a sandbox.
  • Both list Python, TypeScript and CLI.

HopX vs Novita Agent Sandbox at a glance

AttributeHopXNovita Agent Sandbox
What it isFirecracker microVM sandboxes from Bunnyshell with template-based sizing, memory-preserving pause, VNC desktop automation, an MCP server and $200 of free credits.Pay-per-second stateful sandboxes from the Novita GPU cloud, with pause/resume, snapshots, templates and secrets, billed by vCPU-second and GiB-second.
TypeHosted platformHosted platform
IsolationFirecracker Linux microVM per sandbox with hardware-level kernel isolation (homepage); the docs overview says only "isolated computing environments"Not documented beyond "system-level separation" and an isolated runtime and filesystem per sandbox; hypervisor or container runtime not named
Open sourceNoNo
Self-host / BYOCNot documented / Not documentedNot documented / Not documented
SDKsPython, JavaScript/TypeScript, CLI, REST API, MCP serverPython, JavaScript/TypeScript, CLI
Cold start (vendor claim)Homepage: about 100 ms startup from prebuilt snapshots (vendor claim)Product page: instances launch "in under 200ms on average" (vendor claim); resume from pause "typically takes about one second"
Max sessionNo expiry unless timeout_seconds is set; the homepage says sandboxes can run for hours, days or weeks; set_timeout resets the timer from now and the sandbox is destroyed, data included, on expiryProduct page: 1 hour maximum per session on the free tier, 24 hours on the paid tier, custom for Enterprise; the docs describe a creation-time lifetime timeout plus an idle timeout, each of which can pause instead of kill
PersistencePause preserves full state including memory, variables and running processes and resumes where it left off; stop keeps the filesystem only; templates package environments and sandboxes launch from prebuilt snapshots; no user-created snapshot API documentedPausing preserves filesystem and memory and stops compute billing, with optional auto-resume; snapshots save a sandbox as a reusable environment for new sandboxes (v2 region); templates define starting environments; killed sandboxes keep nothing
Snapshots / pauseNot documented / YesYes / Yes
GPUNot mentioned in docs or pricingNot mentioned for sandboxes; the sandbox docs and pricing list vCPU and RAM only (GPUs are documented as separate Novita products)
NetworkingPer-sandbox internet_access flag (false creates an isolated sandbox); default not stated; the security page lists "optional egress controls per sandbox", but the docs do not describe an allow-list; exposed ports get region-scoped URLsInternet access on by default; can be disabled per sandbox (allow_internet_access=False) or restricted with allow_out and deny_out lists of domains, IPs and CIDRs; any port can be exposed through the sandbox's public HTTPS URL; secrets are injected into HTTPS headers only for allowed hosts
PricingPay per second with no plans, minimums or idle charges: vCPU $0.000014/s, memory $0.0000045/s per GiB, storage $0.00000003/s per GiB (about $0.050 per vCPU-hour and $0.016 per GiB-hour); examples on the page: 8 hours at 2 vCPU/4 GB about $1.50; enterprise custom SLAs and volume discounts via salesPer second: vCPU $0.0000098 per vCPU-second (1-8 vCPU), RAM $0.0000032 per GiB-second (512 MiB to 8 GiB in 512 MiB steps); persistent storage for paused sandboxes, templates and snapshots $0.00009/GB-hour beyond 60 GB free; 20 GB ephemeral disk per running sandbox. Examples: 2 vCPU/1 GiB for 1 hour about $0.08, 8 vCPU/8 GiB for 1 hour about $0.37
Free tier$200 free credits, no card requiredFree tier (5 concurrent sandboxes, 2 vCPU/4 GB, 1-hour sessions) until the balance is above $0; $100 promotional credits for new users who complete a setup survey, no card required; 60 GB persistent storage free
ComplianceSecurity page lists SOC 2 (independent assessment), ISO/IEC 27001 and ISO 9001:2015 (vendor claims); certificates or bridge letters available under NDA on requestFooter shows an AICPA SOC 2 badge and links to a trust centre; Enterprise plans list a 99.95% uptime SLA
RegionsNot listed; the API exposes a region field for filtering and URLs but no region names are documentedus-phx-1 (v2, default; adds Secrets and Snapshots) and us-virginia-1 (v1, legacy); custom region for Enterprise
Company headquartersNot documentedNot documented
Good fit forPay-per-second microVM sandboxes with desktop automation and no session limitsCheap per-second code execution and browser-agent runs with pause/resume on a single US region

Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose HopX

  • You want Firecracker isolation with pay-per-second pricing and no monthly plan
  • You need sandboxes that never expire unless you say so
  • You want desktop automation (VNC, mouse, keyboard, screenshots) inside the sandbox
  • You want an MCP server so an IDE assistant can open sandboxes directly

Reasons to choose Novita Agent Sandbox

  • You want per-second pricing with memory-preserving pause and a generous free storage allowance
  • You run browser or coding agents that need sessions up to 24 hours
  • You are already a Novita customer for inference or GPUs

Trade-offs to check first

  • HopX: Region names are not published, and egress controls are mentioned on the security page but not described in the docs
  • HopX: Resources cannot be set per sandbox, only via templates
  • Novita Agent Sandbox: Isolation technology is not named in the docs
  • Novita Agent Sandbox: Two US regions only on standard tiers

Both are worth piloting with your own image and region. See the full HopX profile and Novita Agent Sandbox profile, or the complete comparison.

Frequently asked questions

Is HopX or Novita Agent Sandbox better for AI agents?
Neither is better for every workload. HopX suits pay-per-second microVM sandboxes with desktop automation and no session limits. Novita Agent Sandbox suits cheap per-second code execution and browser-agent runs with pause/resume on a single US region.
What is the difference between HopX and Novita Agent Sandbox?
Session length: No cap (HopX) versus 1 h free / 24 h paid (Novita Agent Sandbox). Only HopX lists REST API and MCP server.
Which is open source, HopX or Novita Agent Sandbox?
Neither is open source.
How do HopX and Novita Agent Sandbox isolate code?
HopX: Firecracker Linux microVM per sandbox with hardware-level kernel isolation (homepage); the docs overview says only "isolated computing environments". Novita Agent Sandbox: Not documented beyond "system-level separation" and an isolated runtime and filesystem per sandbox; hypervisor or container runtime not named.
How does HopX pricing compare with Novita Agent Sandbox?
HopX: Pay per second with no plans, minimums or idle charges: vCPU $0.000014/s, memory $0.0000045/s per GiB, storage $0.00000003/s per GiB (about $0.050 per vCPU-hour and $0.016 per GiB-hour); examples on the page: 8 hours at 2 vCPU/4 GB about $1.50; enterprise custom SLAs and volume discounts via sales. Novita Agent Sandbox: Per second: vCPU $0.0000098 per vCPU-second (1-8 vCPU), RAM $0.0000032 per GiB-second (512 MiB to 8 GiB in 512 MiB steps); persistent storage for paused sandboxes, templates and snapshots $0.00009/GB-hour beyond 60 GB free; 20 GB ephemeral disk per running sandbox. Examples: 2 vCPU/1 GiB for 1 hour about $0.08, 8 vCPU/8 GiB for 1 hour about $0.37. Rates change, so check the HopX and Novita Agent Sandbox pricing pages before deciding.
How long can sessions run on HopX and Novita Agent Sandbox?
HopX: No expiry unless timeout_seconds is set; the homepage says sandboxes can run for hours, days or weeks; set_timeout resets the timer from now and the sandbox is destroyed, data included, on expiry. Novita Agent Sandbox: Product page: 1 hour maximum per session on the free tier, 24 hours on the paid tier, custom for Enterprise; the docs describe a creation-time lifetime timeout plus an idle timeout, each of which can pause instead of kill.
Do HopX and Novita Agent Sandbox support snapshots or pause and resume?
HopX: snapshots not documented, pause and resume yes. Novita Agent Sandbox: snapshots yes, pause and resume yes.

Sources

  1. hopx.ai
  2. hopx.ai/pricing/
  3. docs.hopx.ai
  4. docs.hopx.ai/llms.txt
  5. novita.ai/sandbox
  6. docs.novita.ai/guides/sandbox-overview.md
  7. docs.novita.ai/guides/sandbox-learn-more.md
  8. docs.novita.ai/guides/sandbox-pricing.md

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

Agent Sandboxes. (2026). HopX vs Novita Agent Sandbox. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/hopx-vs-novita-sandbox/