CoreWeave Sandboxes vs RemoteHost
CoreWeave Sandboxes costs $0.128 per vCPU-hour. CoreWeave Sandboxes runs microVMs, offers GPUs and limits a session to 720 hours. RemoteHost runs Firecracker microVMs and limits a session to 72 hours.
Updated
CoreWeave Sandboxes
- Isolation
- MicroVM
- Free tier
- Not listed
- Max session
- 720 hours
RemoteHost
- Isolation
- Firecracker microVM
- Free tier
- 7-day free trial
- Max session
- 72 hours
What is different
7 fields differ. The rest are the same or not listed.
CoreWeave Sandboxes
RemoteHost
- RAM, per GiB-hour
- CoreWeave Sandboxes: $0.0212
- RemoteHost: Included
- Storage
- CoreWeave Sandboxes: Snapshots and volumes billed separately
- RemoteHost: Free
- Billing
- CoreWeave Sandboxes: Per second
- RemoteHost: Bundled machine time
- Max session
- CoreWeave Sandboxes: 720 hours
- RemoteHost: 72 hours
- Concurrent sandboxes
- CoreWeave Sandboxes: Up to 5,000
- RemoteHost: Up to 2,000
- Isolation
- CoreWeave Sandboxes: MicroVM
- RemoteHost: Firecracker microVM
- SDKs
- CoreWeave Sandboxes: Python, TypeScript
- RemoteHost: TypeScript
Full comparison
18 fields, at each provider's list price
CoreWeave Sandboxescoreweave
RemoteHostremotehost
Pricing
- vCPU, per hour
- CoreWeave Sandboxes: $0.128
- RemoteHost: Not listed
- RAM, per GiB-hour
- CoreWeave Sandboxes: $0.0212
- RemoteHost: Included
- Storage
- CoreWeave Sandboxes: Snapshots and volumes billed separately
- RemoteHost: Free
- Free tier
- CoreWeave Sandboxes: Not listed
- RemoteHost: 7-day free trial
- Paid plan from
- CoreWeave Sandboxes: Not listed
- RemoteHost: $20 / month
- Billing
- CoreWeave Sandboxes: Per second
- RemoteHost: Bundled machine time
Limits
- Max session
- CoreWeave Sandboxes: 720 hours
- RemoteHost: 72 hours
- Idle stop
- CoreWeave Sandboxes: Not listed
- RemoteHost: Not listed
- Largest sandbox
- CoreWeave Sandboxes: Not listed
- RemoteHost: 8 vCPU · 16 GiB
- Concurrent sandboxes
- CoreWeave Sandboxes: Up to 5,000
- RemoteHost: Up to 2,000
Platform
- Isolation
- CoreWeave Sandboxes: MicroVM
- RemoteHost: Firecracker microVM
- GPU
- CoreWeave Sandboxes:
- RemoteHost: Not listed
- Snapshots
- CoreWeave Sandboxes:
- RemoteHost:
- Pause and resume
- CoreWeave Sandboxes: Not listed
- RemoteHost:
Developer
- SDKs
- CoreWeave Sandboxes: Python, TypeScript
- RemoteHost: TypeScript
- Integrations
- CoreWeave Sandboxes: Not listed
- RemoteHost: MCP
Trust
- License
- CoreWeave Sandboxes: Not listed
- RemoteHost: Not listed
- BYOC
- CoreWeave Sandboxes: Your CKS clusters. CoreWeave runs the gateway.
- RemoteHost: Enterprise, on hardware you own
Hourly cost
One sandbox running for one hour
CoreWeave Sandboxes
RemoteHost
- 1 vCPU · 2 GiB
- CoreWeave Sandboxes: $0.170
- RemoteHost: Not listed
- 2 vCPU · 4 GiB
- CoreWeave Sandboxes: $0.341
- RemoteHost: Not listed
- 4 vCPU · 8 GiB
- CoreWeave Sandboxes: $0.682
- RemoteHost: Not listed
Compute only, at list rates.
Open the calculatorWhich one fits
Based on the fields above
CoreWeave Sandboxes fits when
- You need GPUs.
- A session must run longer than 72 hours.
- You need a desktop in the sandbox.
RemoteHost fits when
- You use MCP.
- You need pause and resume.
More comparisons
Agent Sandbox vs CoreWeave Sandboxes- Agent Sandbox vs RemoteHost
Agent37 Cloud vs CoreWeave Sandboxes- Agent37 Cloud vs RemoteHost
AgentBay vs CoreWeave Sandboxes- AgentBay vs RemoteHost
- Alibaba Cloud Agent Sandbox vs CoreWeave Sandboxes
- Alibaba Cloud Agent Sandbox vs RemoteHost