RemoteHost vs xShellz Agent Shell
RemoteHost runs Firecracker microVMs and limits a session to 72 hours. xShellz Agent Shell runs gVisor and has no session limit.
Updated
RemoteHost
- Isolation
- Firecracker microVM
- Free tier
- 7-day free trial
- Max session
- 72 hours
xShellz Agent Shell
- Isolation
- gVisor
- Free tier
- Free plan, 1 box with 0.5 vCPU and 512 MB
- Max session
- No limit
What is different
7 fields differ. The rest are the same or not listed.
RemoteHost
xShellz Agent Shell
- Free tier
- RemoteHost: 7-day free trial
- xShellz Agent Shell: Free plan, 1 box with 0.5 vCPU and 512 MB
- Paid plan from
- RemoteHost: $20 / month
- xShellz Agent Shell: $10 / month
- Max session
- RemoteHost: 72 hours
- xShellz Agent Shell: No limit
- Largest sandbox
- RemoteHost: 8 vCPU · 16 GiB
- xShellz Agent Shell: 4 vCPU · 4 GiB
- Concurrent sandboxes
- RemoteHost: Up to 2,000
- xShellz Agent Shell: Up to 5
- Isolation
- RemoteHost: Firecracker microVM
- xShellz Agent Shell: gVisor
- SDKs
- RemoteHost: TypeScript
- xShellz Agent Shell: Python, JavaScript / TypeScript, Go, Java, Ruby, Rust
Full comparison
18 fields, at each provider's list price
RemoteHostremotehost
xShellz Agent Shellxshellz
Pricing
- vCPU, per hour
- RemoteHost: Not listed
- xShellz Agent Shell: Not listed
- RAM, per GiB-hour
- RemoteHost: Included
- xShellz Agent Shell: Included
- Storage
- RemoteHost: Free
- xShellz Agent Shell: Free
- Free tier
- RemoteHost: 7-day free trial
- xShellz Agent Shell: Free plan, 1 box with 0.5 vCPU and 512 MB
- Paid plan from
- RemoteHost: $20 / month
- xShellz Agent Shell: $10 / month
- Billing
- RemoteHost: Bundled machine time
- xShellz Agent Shell: Bundled machine time
Limits
- Max session
- RemoteHost: 72 hours
- xShellz Agent Shell: No limit
- Idle stop
- RemoteHost: Not listed
- xShellz Agent Shell: Not listed
- Largest sandbox
- RemoteHost: 8 vCPU · 16 GiB
- xShellz Agent Shell: 4 vCPU · 4 GiB
- Concurrent sandboxes
- RemoteHost: Up to 2,000
- xShellz Agent Shell: Up to 5
Platform
- Isolation
- RemoteHost: Firecracker microVM
- xShellz Agent Shell: gVisor
- GPU
- RemoteHost: Not listed
- xShellz Agent Shell: Not listed
- Snapshots
- RemoteHost:
- xShellz Agent Shell: Not listed
- Pause and resume
- RemoteHost:
- xShellz Agent Shell:
Developer
- SDKs
- RemoteHost: TypeScript
- xShellz Agent Shell: Python, JavaScript / TypeScript, Go, Java, Ruby, Rust
- Integrations
- RemoteHost: MCP, Claude Code
- xShellz Agent Shell: MCP, Claude Code
Trust
- License
- RemoteHost: Not listed
- xShellz Agent Shell: Not listed
- BYOC
- RemoteHost: Enterprise, on hardware you own
- xShellz Agent Shell: Not listed
Hourly cost
One sandbox running for one hour
RemoteHost
xShellz Agent Shell
- 1 vCPU · 2 GiB
- RemoteHost: Not listed
- xShellz Agent Shell: Not listed
- 2 vCPU · 4 GiB
- RemoteHost: Not listed
- xShellz Agent Shell: Not listed
- 4 vCPU · 8 GiB
- RemoteHost: Not listed
- xShellz Agent Shell: Not listed
Compute only, at list rates.
Open the calculatorWhich one fits
Based on the fields above
RemoteHost fits when
- You want each sandbox in its own microVM.
- You need snapshots.
- You need the sandboxes in your own cloud account.
- You need a sandbox larger than 4 vCPU · 4 GiB.
xShellz Agent Shell fits when
- A session must run longer than 72 hours.
- You need GDPR.
More comparisons
Agent Sandbox vs RemoteHost- Agent Sandbox vs xShellz Agent Shell
Agent37 Cloud vs RemoteHost- Agent37 Cloud vs xShellz Agent Shell
AgentBay vs RemoteHost- AgentBay vs xShellz Agent Shell
- Alibaba Cloud Agent Sandbox vs RemoteHost
- Alibaba Cloud Agent Sandbox vs xShellz Agent Shell