What the Linux kernel offers for isolation, and what we do and do not claim.
Checked 18 October 2026 against the kernel.org documentation linked on each row.
The four mechanisms below are real kernel features. We list them so the difference between a kernel feature and our own setup is clear. Each row says what the kernel documentation says, then what our workers do today, then a label.
Namespaces
What the kernel documents. The kernel docs list six namespace kinds that tasks can live in or share: UTS, IPC, VFS, PID, User and Net. An ID such as a process group or semaphore is only valid inside the namespace it came from. Source
Our workers today. We do not create or configure namespaces. Each product runs as its own deployed worker, and that separation is a deployment fact, not a kernel namespace.
Target, not claimed
Control groups v2
What the kernel documents. The kernel docs describe cgroup as a way to organize processes in a hierarchy and distribute system resources along that hierarchy, with a single hierarchy in v2. Source
Our workers today. We do not set cgroup limits. We have no published CPU or memory limit per worker.
Target, not claimed
Landlock
What the kernel documents. The kernel docs say Landlock restricts ambient rights, such as global filesystem or network access, for a set of processes. It is a stackable security module that sits on top of the normal access controls. Source
Our workers today. We do not apply Landlock rules.
Target, not claimed
Seccomp filters
What the kernel documents. The kernel docs say seccomp lets a process filter the system calls it can make, using a BPF program. They also say system call filtering is not a sandbox by itself. It reduces exposed kernel surface and is a tool for sandbox builders. Source
Our workers today. We do not install seccomp filters.
Target, not claimed
What our workers do today
Verified in our own setup
Each product is a separate worker deployment that gets only the bindings written in its own config. The platform front reaches its backend through one named Durable Object binding and its status panel through one service binding. Secrets are stored as worker secrets, not in page code. The free try pages say what they store: the Security Desk sample saves nothing.
Not yet shown
We have not published a test that a worker cannot use a tool outside its scope. That is the next proof to build. Until it exists, read the tool scope on How it works as how the platform is designed, not as a tested guarantee.
Target
Labels: Target means a goal we have not met or have not tested. Nothing on this page is a security certification.