Cap CPU and memory where the work runs

Set optional CPU and memory limits per Project group, repository or session. The most specific limit applies, running containers are updated live, and Settings → Resource limits shows each effective value, its source and current use.

Live limit updates have not been proven on a production server yet. Hard enforcement depends on the host’s cgroup configuration.

How it works

  1. Set limits at the right level

    A session limit overrides its repository limit, which overrides its Project group. Everything is unlimited by default, and the control plane is never limited.

  2. Change running containers

    New limits reach running containers without a restart. A memory limit below current use or above the host’s capacity is refused; a shared container uses its repository limit.

  3. Keep the console responsive

    Core, Host agent and web gateway run with a higher CPU weight than project containers, so the console stays usable while workloads use every core.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

Release videos

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.