Sandlock
sandlock.io
- Free plan
- Linux
- API
- Self-hosted
What Sandlock is
Sandlock is a Linux process sandbox that confines untrusted code using policies enforced by the kernel. It uses Landlock, seccomp-bpf, and seccomp user notification to govern filesystem access, network activity, system calls, and resource use. Policies can deny network egress by default, allow HTTP requests according to method, host, and path, stage writes with copy-on-write, and set resource limits. A supervisor can attach credentials through a proxy after checking the HTTP rules, so the sandboxed workload does not hold the secret value. Interfaces include a CLI, Python SDK, Rust API, Go SDK, OCI runtime, and MCP server. The OCI runtime works with containerd, CRI-O, and Kubernetes; the remote MCP API can connect to Claude Desktop, Cursor, or another MCP client. Sandlock runs as an ordinary user without root, a container runtime, or a hypervisor. Linux 6.12 or later supports the full protection set by default; older kernels can be used if missing protections are explicitly waived per policy. Sandlock shares the host kernel, so its guarantees do not cover kernel vulnerabilities or hardware side channels. The free plan has no caps, telemetry, or registration and is licensed under Apache-2.0. Commercial HTTP API and Scheduler offerings are self-hosted annual licenses, with prices not listed.
Who it suits
Sandlock suits teams running untrusted code for AI agent tools, CI builds, or per-request execution on Linux. Its commercial API and Scheduler offerings are for customers deploying software on their own infrastructure.
Good to know, and what to watch
- Controls filesystem, network, syscalls, and resources.
- Runs without root, a container runtime, or a hypervisor.
- Offers CLI, SDKs, APIs, OCI runtime, and MCP server.
- Free plan has no caps, telemetry, or registration.
- Supports containerd, CRI-O, and Kubernetes integration.
- Full protection set is supported by default on Linux 6.12 or later.
- Shares the host kernel; guarantees exclude kernel vulnerabilities and hardware side channels.
- Commercial HTTP API and Scheduler are self-hosted.
Plans
Every plan and priceSandbox HTTP API
Sandbox Scheduler
Sandlock
Free plan
The verdict
Sandlock provides policy controls and several interfaces for confining untrusted Linux workloads, including self-hosted commercial options. Its protection boundary includes the shared host kernel, and older kernels may require waiving missing protections.
What the maker publishes
- Commercial deployment
- The commercial HTTP API and Scheduler are licensed software deployed on the customer's infrastructure, with no hosted or shared-tenant offering. source
- Company
- Sandlock is a Multikernel Technologies project; the maker lists its address as San Jose, California. source
- Credential handling
- The supervisor attaches secrets in the proxy only after the HTTP ACL check, so the sandboxed workload does not hold the secret value. source
- Enforcement
- It uses Landlock, seccomp-bpf, and seccomp user notification to control filesystem, network, syscalls, and resources. source
- Headquarters
- San Jose, California, United States source
- Integrations
- The OCI runtime works with containerd, CRI-O, and Kubernetes, and the remote MCP API can be used with Claude Desktop, Cursor, or another MCP client. source
- Interfaces
- The product provides a CLI, Python SDK, Rust API, Go SDK, OCI runtime, and MCP server. source
- Kernel requirement
- Linux 6.12 or later supports the full protection set by default; older kernels can be used if missing protections are explicitly waived per policy. source
- Policy controls
- Policies can restrict filesystem access, default-deny network egress, apply HTTP method/host/path rules, inject credentials, stage writes with copy-on-write, and set resource limits. source
- Privileges
- Sandlock runs as an ordinary user and does not require root, a container runtime, or a hypervisor. source
- Purpose
- Sandlock is a lightweight Linux process sandbox for confining untrusted code with kernel-enforced policies. source
- Support
- Engineering support and a response SLA are included with each commercial license. source
- Threat boundary
- Sandlock shares the host kernel, and its security guarantees do not cover kernel vulnerabilities or hardware side channels. source
- Use cases
- The maker describes use for AI agent tool use, CI and untrusted builds, and per-request code execution. source
Checked against the maker's pages on 4 Oct 2026.