• Docs
  • Changelog
Sign in
Get started
    • Home
    • Your first deploy
    • Free instances
    • Platform features by plan
    • Use with coding agents
    • FAQ
    • Templates
      • Migrate from…
        • Heroku
        • Railway
    • Compute plans
    • SandboxesBeta
      • Service types
        • Which to use?
        • Static sites
        • Web services
        • Private services
        • Background workers
        • Cron jobs
        • Workflows
        • Multi-service architectures
      • Data storage
        • Render Postgres
        • Render Key Value (Redis®-compatible)
        • Persistent disks
    • How deploys work
    • Supported languages
    • Git providers (GitHub, etc.)
    • Build pipeline
    • Deploy hooks
    • Monorepo support
    • Troubleshooting deploys
      • Previewing changes
        • Single-service previews
        • Preview environments (multi-service)
      • Docker deploys
        • Overview
        • Deploy a registered image
        • Using secrets
      • Runtime
        • Native runtimes
        • Environment variables & secrets
        • Default environment variables
    • Intro to sandboxes
    • Limits & pricing
      • How to…
        • Create & configure sandboxes
        • Execute commands
        • Upload and download files
        • Manage snapshots
      • Use with…
        • Claude Managed Agents
        • Cursor Cloud Agents
        • OpenAI Agents API
      • SDK/CLI reference
        • TypeScript SDK
        • Python SDK
        • CLI commands
    • Intro to workflows
    • Tutorial
    • Limits & pricing
      • How to…
        • Define tasks
        • Define flowsNew
        • Trigger runs
        • Develop locally
      • SDK reference
        • TypeScript SDK
        • Python SDK
      • Example workflows
        • TypeScript examples
        • Python examples
    • Overview
    • Create & connect
    • Database credentials
    • Extensions
    • Version upgrades
    • Logical replication
    • Legacy instance types
      • Database recovery
        • Recovery & backups
        • High availability
      • Database performance
        • Read replicas
        • Connection pooling
        • Admin apps
        • Repacking tables
        • Troubleshooting performance
    • Regions
    • Inbound IP rules
    • Edge caching
    • WebSockets
    • TLS certificates
      • Custom domains
        • Overview
        • Cloudflare
        • Namecheap
        • Other DNS providers
      • Internal traffic
        • Private network
        • Private links
      • Outbound traffic
        • Default IP ranges
        • Dedicated IP addresses
        • Outbound bandwidth
        • Handling network changes
      • Static site config
        • Custom response headers
        • Redirects & rewrites
    • The Render Dashboard
    • SSH / Shell access
    • Projects & environments
      • Service actions
        • Scaling
        • Rollbacks
        • Maintenance mode
        • One-off jobs
      • Infrastructure as code
        • Blueprints overview
        • render.yaml reference
        • Terraform provider
    • In-dashboard metrics
    • Health checks
    • Uptime best practices
      • Logging
        • In-dashboard logs
        • Log streams (syslog/HTTPS)
      • OpenTelemetry (OTel) metrics
        • Provider setup
        • Metrics reference
      • Notifications
        • Webhooks
        • Email / Slack
    • MCP Server
      • Render CLI
        • Overview
        • Command reference
      • REST API
        • Overview
        • API reference
      • Third-party connections
        • OIDC support
        • Datadog
    • Workspaces, members, & roles
    • Login settings
    • Audit logs
      • Organizations
        • Overview
        • SAML SSO
    • DDoS protection
    • Platform maintenance
      • Compliance
        • Overview
        • HIPAA (US health data)
        • HIPAA best practices
        • Shared responsibility model
        • Pentest policy
    • Heroku vs Render
    • Vercel vs Render

Limits and Pricing for Render Sandboxes

Render Sandboxes is in public beta.

APIs, defaults, and limits might change during the beta period.

The following limits and pricing apply to Render Sandboxes. Limit and pricing details are subject to change during the beta period.

Compute plans and billing

Each sandbox uses one of the following compute plans, which determines its specs and pricing. You specify which plan to use when you create a sandbox.

PlanSpecs
Price

1c-2g (default)

1 CPU
2 GB RAM
$0.12 / CPU-hour +
$0.038 / hour

2c-4g

2 CPU
4 GB RAM
$0.12 / CPU-hour +
$0.076 / hour

4c-8g

4 CPU
8 GB RAM
$0.12 / CPU-hour +
$0.152 / hour

8c-16g

8 CPU
16 GB RAM
$0.12 / CPU-hour +
$0.304 / hour

How billing works

Sandboxes are billed differently for CPU and memory usage:

ResourceBilling

CPU

Billed at $0.12 per CPU-hour, based on the total amount of CPU your sandbox actually uses:

  • If a sandbox on the 1c-2g plan constantly uses its full 1 CPU for one hour, Render bills $0.12 for CPU usage.
  • If the same sandbox uses only 0.5 CPU for one hour, Render bills $0.06 for CPU usage.

Memory

Billed at $0.019 per GB-hour according to your sandbox's total provisioned memory (regardless of actual usage).

A sandbox is not billed for CPU or memory usage while suspended.

General limits

PropertyLimit

Writable filesystem storage per sandbox

40 GB

Maximum runtime timeout

  • If you set a runtime timeout, the maximum allowed value is 30 days.
  • You can also disable this timeout entirely to prevent automatic termination.

Learn more about sandbox timeouts.

Maximum idle timeout

  • If you set an idle timeout, the maximum allowed value is 24 hours.
  • You can also disable this timeout entirely to prevent automatic suspension.

Learn more about sandbox timeouts.

Suspended sandbox resumability period

30 days

Sandbox groups per workspace

10

Concurrent sandboxes per sandbox group

Default: 1,000 for Pro workspaces and above, 100 for Hobby workspaces

You can request an increase to 5,000 for a Pro workspace or 10,000 for a Scale workspace.

See details below.

Environment variables per sandbox

100 variables, with a combined size of 256 KB across names and values

Supported regions

1 (Oregon)

Need to increase any of these sandbox limits?

Reach out with details about your use case:

Talk to our team

Concurrency per group

By default, each sandbox group in a Pro workspace or above can have up to 1,000 concurrent sandboxes, and each sandbox group in a Hobby workspace can have up to 100 concurrent sandboxes.

  • In some cases, Render might enforce a temporarily reduced concurrency limit for newly created workspaces with minimal billing history.

  • You can request a limit increase to 5,000 for a Pro workspace or 10,000 for a Scale workspace. To request an increase, please contact Render.

  • Suspended sandboxes do not count toward concurrency limits.

    • To resume a suspended sandbox, its group must be under its concurrency limit.
  • You can reduce the concurrency limit for an individual group.

  • While a group is at its concurrency limit, requests to create or resume a sandbox fail with HTTP code 429.

    • To reclaim capacity, terminate sandboxes you no longer need.

API rate limits

Sandbox API operations have separate default rate limits. These limits apply per user, shared across that user's API keys. Requests that exceed a rate limit fail with HTTP code 429.

OperationRequests per minute

Create a sandbox

100

Terminate a sandbox

1,000

Execute a command

1,000

Upload or download a file or directory

1,000

Read sandbox and sandbox group resources

400

Write sandbox group resources

100

Capture a snapshot

10

Limits and Pricing for Render Sandboxes
  • Compute plans and billing
    • How billing works
  • General limits
    • Concurrency per group
  • API rate limits
All Systems Operational
© Render Inc. All rights reserved.