Drylab
Compute & Resources

Select a Sandbox

Choose the machine your analysis runs on: a Drylab cloud instance or your own local runtime.

The sandbox is the machine your analysis code runs on. By default, Drylab runs on a cloud Instance Small. You can switch to a bigger instance for heavy jobs, or to your own machine with a local runtime.

Open the sandbox selector

Click the sandbox button at the top of the page (it shows the current sandbox, for example Instance Small). The Select Sandbox list shows the cloud instances your plan includes and your local runtimes.

Select Sandbox

  • CPU: Drylab cloud instances.
  • GPU: cloud GPU instances. These aren't offered right now; the group appears here once they are.
  • Local Runtime: machines you connected yourself. Click Add local runtime… to set one up.

Cloud instances

InstanceCPURAMGPUBest for
Instance Small (default)32 vCPU128 GBNoneMost analyses, including standard scRNA-seq
Instance Medium64 vCPU192 GBNoneLarge datasets, multi-sample integration, genome-scale jobs

Cloud GPU sandboxes aren't offered right now.

Instance Small, Instance Medium or a local runtime: which to pick

Heavy GPU work such as protein structure prediction or docking usually doesn't need a GPU sandbox. Drylab's accelerated tools run those jobs on dedicated GPU hardware and report back to your chat. Heavy single-cell, spatial and ATAC steps also go to GPU workers automatically. See HPC Tasks.

When to switch

SituationSuggested sandbox
Exploring data, plots, statisticsInstance Small
scRNA-seq with many samples or >200k cellsInstance Medium
Drylab shows More Memory Recommended on the planInstance Medium (click Approve with ...)
Data that must stay on your own hardwareA local runtime

Switching during a chat

Pick another sandbox in Select Sandbox at any time. Your files in the Vault are kept. Variables held in memory by the previous sandbox aren't carried over, so rerun the notebook if you need them.

Chats stay tied to where they started: a cloud chat needs a cloud sandbox, and a local-runtime chat needs that same machine. Otherwise the chat opens in View Only Mode until you switch back.

On this page