Azure Container Apps dynamic sessions vs SF Compute Autoresearch Sandboxes

SF Compute Autoresearch Sandboxes bills memory only, at $0.04572 per GiB-hour. Azure Container Apps dynamic sessions runs full VMs. SF Compute Autoresearch Sandboxes runs microVMs.

Updated

Azure Container Apps dynamic sessions

Isolation
Full VM
Free tier
Not listed
Max session
Not listed

SF Compute Autoresearch Sandboxes

Isolation
MicroVM
Free tier
None
Max session
Not listed

What is different

3 fields differ. The rest are the same or not listed.

Azure Container Apps dynamic sessions
SF Compute Autoresearch Sandboxes
Concurrent sandboxes
Azure Container Apps dynamic sessions: Up to 600
SF Compute Autoresearch Sandboxes: Up to 4,096
Isolation
Azure Container Apps dynamic sessions: Full VM
SF Compute Autoresearch Sandboxes: MicroVM
Integrations
Azure Container Apps dynamic sessions: LangChain
SF Compute Autoresearch Sandboxes: MCP, Claude Code

Full comparison

18 fields, at each provider's list price

SF Compute Autoresearch Sandboxesautoresearch.sfcompute.com

Pricing

vCPU, per hour
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Included
RAM, per GiB-hour
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: $0.04572
Storage
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Sandbox snapshots $0.10 per GiB-month of deduplicated bytes, $0.05 per GiB-month in cold storage
Free tier
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: None
Paid plan from
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Pay as you go
Billing
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Memory only

Limits

Max session
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Not listed
Idle stop
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Not listed
Largest sandbox
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: 4 vCPU · 8 GiB
Concurrent sandboxes
Azure Container Apps dynamic sessions: Up to 600
SF Compute Autoresearch Sandboxes: Up to 4,096

Platform

Isolation
Azure Container Apps dynamic sessions: Full VM
SF Compute Autoresearch Sandboxes: MicroVM
GPU
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Not listed
Snapshots
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes:
Pause and resume
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes:

Developer

SDKs
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Not listed
Integrations
Azure Container Apps dynamic sessions: LangChain
SF Compute Autoresearch Sandboxes: MCP, Claude Code

Trust

License
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Not listed
BYOC
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: Not listed

Hourly cost

One sandbox running for one hour

Azure Container Apps dynamic sessions
SF Compute Autoresearch Sandboxes
1 vCPU · 2 GiB
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: $0.091
2 vCPU · 4 GiB
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: $0.183
4 vCPU · 8 GiB
Azure Container Apps dynamic sessions: Not listed
SF Compute Autoresearch Sandboxes: $0.366

Compute only, at list rates.

Open the calculator

Which one fits

Based on the fields above

Azure Container Apps dynamic sessions fits when

  • You want each sandbox to be a full VM.
  • You use LangChain.

SF Compute Autoresearch Sandboxes fits when

  • You want each sandbox in its own microVM.
  • You use MCP or Claude Code.
  • You need snapshots.
  • You need pause and resume.

More comparisons

See all comparisons

Related