Security.RunDevelopers
v1 PreviewOpenAPI ↗
API & MCP reference/Limits and environments
REFERENCE

Limits and environments

Check whether a workload fits before you submit it.

Request and output limits

  • Deadline: 1–120 seconds, default 30.
  • Inputs: up to 64 files, 8 MiB per artifact, and 32 MiB total including stdin.
  • Arguments: up to 256 items; environment: up to 32 variables.
  • Stdout and stderr: 1 MiB each. Requested output files: up to 64 files and 8 MiB total.

Choose a supported environment

The current AWS catalog runs Linux ARM64 tools. It does not provide Windows-only execution, GPUs or access to host devices. Inspect each tool’s prerequisites before choosing a module, plugin or database.

Memory and CPU

The AWS baseline is 1 GiB and 0.5 vCPU, with provider-controlled bursts up to 4 GiB and 2 vCPU. It is not a hard 1 GiB memory cap. The local Docker adapter has different enforcement; inspect your deployment’s advertised resources.

What persists

Each invocation gets a fresh MicroVM. Processes and unrequested files disappear after cleanup. Requested outputs and run records remain in your operator’s storage until explicitly deleted. There are no warm pools or shared running sessions.

Networking and collection

Without a target profile, the customer VPC policy applies. A selected profile shares a private loopback network with the tool. Generic runs report lifecycle and stdout/stderr; use explicit collector tools when you need kernel events.

Search documentation, capabilities and native tools.

Copy this page

Your browser couldn’t copy automatically. Copy the selected Markdown below.