Azure Container Apps dynamic sessions vs Sandock

Azure Container Apps dynamic sessions runs full VMs. Sandock runs containers and limits a session to 24 hours.

Updated Oct 14, 2026

Azure Container Apps dynamic sessions

Isolated sandbox sessions for running code on Azure.

Isolation: Full VM
Free tier: Not listed
Max session: Not listed

Visit site Azure Container Apps dynamic sessions profile

Sandock

Docker sandboxes with persistent volumes for AI agents.

Isolation: Container
Free tier: None
Max session: 24 hours

Visit site Sandock profile

What is different

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

Field

Azure Container Apps dynamic sessions

Sandock

Concurrent sandboxes: Azure Container Apps dynamic sessions: Up to 600; Sandock: Up to 150
Isolation: Azure Container Apps dynamic sessions: Full VM; Sandock: Container
Integrations: Azure Container Apps dynamic sessions: LangChain; Sandock: MCP

Full comparison

18 fields, at each provider's list price

Azure Container Apps dynamic sessionsazure.microsoft.com/en-us/pricing/details/container-appsazure.microsoft.com

Sandocksandock.ai/pricing

Pricing

vCPU, per hour: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed
RAM, per GiB-hour: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed
Storage: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed
Free tier: Azure Container Apps dynamic sessions: Not listed; Sandock: None
Paid plan from: Azure Container Apps dynamic sessions: Not listed; Sandock: $5 / month
Billing: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed

Limits

Max session: Azure Container Apps dynamic sessions: Not listed; Sandock: 24 hours
Idle stop: Azure Container Apps dynamic sessions: Not listed; Sandock: After 30 minutes
Largest sandbox: Azure Container Apps dynamic sessions: Not listed; Sandock: 16 vCPU · 8 GiB
Concurrent sandboxes: Azure Container Apps dynamic sessions: Up to 600; Sandock: Up to 150

Platform

Isolation: Azure Container Apps dynamic sessions: Full VM; Sandock: Container
GPU: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed
Snapshots: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed
Pause and resume: Azure Container Apps dynamic sessions: Not listed; Sandock:

Developer

SDKs: Azure Container Apps dynamic sessions: Not listed; Sandock: JavaScript / TypeScript, Python
Integrations: Azure Container Apps dynamic sessions: LangChain; Sandock: MCP

Trust

License: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed
BYOC: Azure Container Apps dynamic sessions: Not listed; Sandock: Private / VPC deployment on Enterprise

Hourly cost

One sandbox running for one hour

Size

Azure Container Apps dynamic sessions

Sandock

1 vCPU · 2 GiB: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed
2 vCPU · 4 GiB: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed
4 vCPU · 8 GiB: Azure Container Apps dynamic sessions: Not listed; Sandock: Not listed

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.

Sandock fits when

You use MCP.
You need pause and resume.
You need the sandboxes in your own cloud account.

More comparisons

See all comparisons

Azure Container Apps dynamic sessions

Sandock

What is different

Full comparison

Pricing

Limits

Platform

Developer

Trust

Hourly cost

Which one fits

Azure Container Apps dynamic sessions fits when

Sandock fits when

More comparisons

Related

Compare

Pricing

Browse