Skip to content
SPECIFICTION
Get listed

CAPE Sandbox vs Sandlock

CAPE Sandbox

github.com

Sandlock

sandlock.io

Side by side

FigureCAPE SandboxSandlock
Price fromFreeFree
Free planYesYes
Free trial——
Open source——
WebYes—
LinuxYesYes
APIYesYes
Self-hostedYesYes
Plans published13
Spec score · Sandbox Software8.2 (#7)7.4 (#16)
PurposeCAPE is a malware sandbox that executes malicious files in an isolated environment while recording behavior and collecting forensic artifacts.Sandlock is a lightweight Linux process sandbox for confining untrusted code with kernel-enforced policies.

Plans

CAPE Sandbox

  • CAPE SandboxFree

CAPE Sandbox pricing →

Sandlock

  • SandlockFree
  • Sandbox HTTP APIPrice not published
  • Sandbox SchedulerPrice not published

Sandlock pricing →

In their own words

CAPE Sandbox

CAPE Sandbox is a free, open-source malware sandbox that executes malicious files in isolation while recording behavior and forensic artifacts. It captures API-hook activity, file changes, network traffic as PCAP, desktop screenshots, and full memory dumps. Malware classification can use YARA scans of unpacked payloads, Suricata scans of network captures, and behavioral signatures from API-hook output. CAPE also performs dynamic unpacking and extracts malware configuration through static and dynamic analysis. Its programmable debugger supports custom unpacking and configuration extractors, anti-sandbox countermeasures, and instruction traces. Configuration parsing works with CAPE’s framework and the listed RATDecoders, DC3-MWCP, MalDuck, and MaCo projects. Documentation covers a REST API, distributed deployment, and endpoints for tasks, reports, files, PCAPs, and machines. Additional integrations include Box-js, Curtain, LibreNMS, and Suricata. The project recommends Ubuntu 24.04 LTS, Windows 10 or Windows 11 23H2 targets, and KVM. Active unpacking is off by default because it may affect detonation quality.

Visit github.com

Sandlock

Sandlock is a Linux process sandbox for confining untrusted code with policies enforced by the kernel. It uses Landlock, seccomp-bpf, and seccomp user notification to control filesystem access, network activity, system calls, and resource use. Policies can deny network egress by default, apply HTTP method, host, and path rules, stage writes through copy-on-write, and set resource limits. A supervisor can attach credentials through a proxy after an HTTP access check, keeping the secret value out of the sandboxed workload. 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, while 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 require explicit waivers for missing protections. It shares the host kernel, excluding kernel vulnerabilities and hardware side channels from its guarantees.

Visit sandlock.io