Skip to main content
Modal is a hosted sandbox provider for running task sandboxes away from the Roomote server. It is a good fit when you want provider-managed sandbox infrastructure, better isolation from the app host, and snapshot-capable resume flows.

​
When to use Modal

Use Modal when:
  • several people may run tasks at the same time
  • task work should not consume CPU or memory on the Roomote host
  • you want hosted sandboxes with snapshot support
  • you can provide Modal credentials

​
Configuration

Add Modal from Settings > Sandboxes, or provide the values as deployment env vars:
Optional values:
MODAL_REGIONS is an optional comma-separated list of Modal container placement regions (for example us, us-west, or us,eu). When unset, Modal chooses placement. Prefer broader tokens such as us for capacity and cold-start behavior. Pinning a region can add a Modal pricing multiplier and only applies to newly created or resumed sandboxes, not sandboxes that are already running. Environments with Docker projects automatically use Modal’s beta VM sandbox runtime so Docker and Docker Compose can run inside the task. Roomote starts Docker as the VM sandbox’s primary service and requests 2 CPU cores and 8 GiB of memory for these tasks. Other Modal tasks use the standard sandbox runtime with 2 CPU cores and 4 GiB of memory. Container builds and services share the task sandbox’s CPU and memory.

​
Verify setup

  1. save Modal credentials
  2. select Modal as the default sandbox provider
  3. start a small task from an environment
  4. confirm the task starts, streams logs, and can run project commands
  5. try resuming or following up on a task that can use a saved snapshot

​
Common issues

  • Tasks fail immediately after launch. Check MODAL_TOKEN_ID, MODAL_TOKEN_SECRET, and any Modal environment or endpoint overrides.