Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

Sandlock review

Freemium#7 of 25 in Sandbox Software

A deep, open-source Linux sandbox for teams that need granular policy controls.

8.5/10Editor score
Sandlock8.5 Visit Sandlock

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Sandlock is a Linux process sandbox for running untrusted code, aimed at teams that need policy-level control over filesystems, network access, system calls, and resource usage. Its core product is Apache-2.0 licensed and available through a free plan. Sandlock does not require root, a container runtime, or a hypervisor, and includes a CLI, Python, Rust, and Go SDKs, an OCI runtime, and an MCP server. The product is focused on Linux environments, with API access also represented in its platform coverage.

The published plans separate the core Sandlock product from fleet-oriented components. The Sandlock plan includes the Apache-2.0-licensed core, CLI, SDKs, OCI runtime, and MCP server. The Sandbox HTTP API adds an API server, client SDKs, and unlimited sandboxes and keys per deployment. Sandbox Scheduler adds placement, a checkpoint store, and routers. The HTTP API and Scheduler are commercial components, with pricing based on fleet size or node count, making the plan structure most relevant to teams planning self-hosted fleet deployments rather than a single local sandbox.

Policy depth is Sandlock’s defining strength. Filesystem rules cover read, write, deny, chroot, and per-sandbox mounts, while copy-on-write workspaces support commit, abort, keep, and dry-run modes. Network policies can allow or deny hosts, IPs, CIDRs, protocols, and ports; HTTP controls cover methods, hosts, and paths, with HTTPS interception. Resource limits include memory, processes, open files, CPU, disk, and GPU. Custom syscall handlers can audit, deny, or fabricate results. Choose Sandlock when Linux compatibility and granular enforcement matter most; teams needing broader platform coverage should consider a different sandboxing approach.

Sandlock pros and cons

  • Where it wins
    • Filesystem, network, syscall, and resource controls
    • Open source with CLI, Python, Rust, and Go SDKs
    • OCI runtime supports containerd, CRI-O, and Kubernetes
  • Where it doesn't
    • Core platform coverage is Linux-only
    • HTTP API and Scheduler pricing depends on fleet size or node count
    • Fleet deployment features are split across commercial components

Sandlock fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update