Skip to content

Go to the docs contents

Isolation

Each app runs isolated under gVisor, and each build, tests included, in its own micro-VM, on a separate cluster.

Updated November 21, 2026.

View as Markdown

Each app isolated under gVisor and each build in its own micro-VM: a cracked app stays sealed in its own jar

You, to your AI: Explain how the app is isolated from the others.

When to use it

It is always there, without declaring anything: each app and each build are isolated.

How it works

Each app runs isolated under gVisor, a user-space kernel between it and the machine. Each build, tests included, runs in its own micro-VM, on a separate cluster.

What to know

An app runs in its environment’s space (its namespace), without privileges (Pod Security “restricted”) and with quotas. Apps do not run in micro-VMs: only builds do, on a cluster that reaches neither while nor the apps.

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh