Network
Worker has no network; only exact approved domains and IPs are reachable through the broker.

Containment evidence · status as of 10 November 2026
Our containment rules only count once they hold on a real Linux host running Docker. This page explains that test run and shows its honest current status.
Historical local run (22 October 2026): 9 Docker probes were skipped. The separate Linux-host results below record the completed builder run.
Linux host run · 10 November 2026
9 passed · 0 failed · 0 skipped
Ubuntu 24.04.5 · Docker 29.1.3 · cgroup v2 · started 2026-11-10T09:53:08Z
Results archive SHA-256: 6d21d0661f605a8cb1a65cf3d6ca4cfdcc45bb5cc1d83579819236f13f2b3294
This Linux run was carried out by us on a disposable server, so it is builder evidence. No independent reviewer has signed off yet; until they do, the containment is a review candidate, not production-qualified. This page does not run tests in your browser.
Approved-domain and IP transport checks
Local functional evidence
Linux worker boundary
9/9 Docker probes passed on a builder-run Linux host (10 Nov 2026)
Independent findings and retest
No external report received
Provider budgets and permitted-channel leakage
Deployment qualification pending
Worker has no network; only exact approved domains and IPs are reachable through the broker.
Child processes, detached processes and escapes from the container are refused or contained.
Memory, CPU and process-count limits hold under load (cgroups).
Spend and step budgets stop the agent before, not after, the limit.
Raw unedited logs, exit codes, host details and pinned image digests are kept for review.
Use an Ubuntu 24.04 virtual machine with no customer data, production credentials or other workloads. Lovable hosts this website but does not provide a Docker daemon for the containment probes. The guided help is free; any third-party server, registry or network charges are separate and are not provisioned by this page.
Create an Ubuntu VM in your own Hetzner account, then return for the Docker and evidence commands.
Start from DigitalOcean's Docker image in your own account, then verify the host before running anything.
These are third-party options, not endorsements or Encased-hosted test servers. You can also use an existing suitable Linux machine. Do not rent or change infrastructure until you have approved the cost and access arrangements. Compare worker connection patterns.
These steps run the reference deployment, not a Smokescreen or gVisor pairing. You need a Linux Docker VM, a registry you control and actual image manifest digests. If reviewed images are not available, stop and ask your reviewer: a self-selected image is not independently approved.
Use a disposable VM with no customer data or credentials. Docker group access is root-equivalent. After this block, log out of SSH and reconnect before continuing. These commands require Bash.
sudo apt-get update
sudo apt-get install -y ca-certificates curl python3 python3-venv docker.io
sudo systemctl enable --now docker
sudo usermod -aG docker "$USER"This block asks for a reviewed base reference and your registry image tag. Obtain the reviewed base manifest digest from Lucas or your technician. A tag is not a digest. Authenticate to your registry outside the logs using its approved login method; never paste passwords into these commands. Building/pushing a worker does not make it independently reviewed.
bash <<'ENCASED_PREP'
set -euo pipefail
umask 077
ROOT="$HOME/encased-run-$(date -u +%Y%m%dT%H%M%SZ)"
mkdir -p "$ROOT/evidence"
printf '%s\n' "$ROOT" > "$HOME/.encased-run-path"
cd "$ROOT"
docker info >/dev/null
curl --fail --location --show-error https://encased.ai/sdk/encased-0.3.2.tgz -o encased-0.3.2.tgz
printf '%s %s\n' 'fc0461a37ef92309be9e18ffb4f26a7332e415db0de0db490d6454a069c8be3f' 'encased-0.3.2.tgz' | sha256sum -c -
sha256sum encased-0.3.2.tgz > evidence/package.sha256
tar -xzf encased-0.3.2.tgz
# Keep the virtual environment outside the Docker build context.
python3 -m venv "$ROOT/venv"
read -r -p 'Reviewed base repository@sha256 digest: ' BASE </dev/tty
if [[ ! "$BASE" =~ ^[^[:space:]]+@sha256:[a-f0-9]{64}$ ]]; then
echo 'STOP: a complete reviewed base manifest reference is required.'; exit 2
fi
read -r -p 'Worker image tag in a registry you control: ' TAG </dev/tty
if [[ -z "$TAG" || "$TAG" =~ [[:space:]] || "$TAG" != */* || "$TAG" == *@* ]]; then
echo 'STOP: enter a repository/tag in your registry, not a digest.'; exit 2
fi
cd "$ROOT/encased-0.3.2"
docker pull "$BASE" 2>&1 | tee "$ROOT/evidence/base-pull.log"
docker build --progress=plain --build-arg "BASE=$BASE" \
-f deployment/isolation-worker.Dockerfile -t "$TAG" . \
2>&1 | tee "$ROOT/evidence/worker-build.log"
docker push "$TAG" 2>&1 | tee "$ROOT/evidence/worker-push.log"
echo 'Enter the worker repository@sha256 manifest reference reported by your registry.'
echo 'Do not enter the local image ID. Ask your reviewer to review this artifact.'
read -r -p 'Worker repository@sha256 digest: ' WORKER </dev/tty
if [[ ! "$WORKER" =~ ^[^[:space:]]+@sha256:[a-f0-9]{64}$ ]]; then
echo 'STOP: a complete worker manifest reference is required.'; exit 2
fi
docker pull "$WORKER" 2>&1 | tee "$ROOT/evidence/worker-pull.log"
printf '%s\n' "$BASE" > "$ROOT/base-reference.txt"
printf '%s\n' "$WORKER" > "$ROOT/worker-reference.txt"
printf 'Prepared: %s\n' "$ROOT"
ENCASED_PREPRun only after step 2 succeeds. Enter who ran it and whether the images have been independently reviewed. The wrapper saves the actual test and log-writing exit codes, including failures. The shipped script rebuilds the worker and stops if its image ID differs from your pinned registry image; do not bypass that check. Its internal pull/build output is suppressed, so the earlier preparation logs are retained separately.
bash <<'ENCASED_RUN'
set -euo pipefail
umask 077
ROOT="$(cat "$HOME/.encased-run-path")"
BASE="$(cat "$ROOT/base-reference.txt")"
WORKER="$(cat "$ROOT/worker-reference.txt")"
. "$ROOT/venv/bin/activate"
read -r -p 'Who is running this test? ' OPERATOR </dev/tty
read -r -p 'Image review status / reviewer reference (or Not reviewed): ' REVIEW </dev/tty
{
date -u --iso-8601=seconds
printf 'Operator: %s\nImage review status: %s\n' "$OPERATOR" "$REVIEW"
cat /etc/os-release
uname -srm
lscpu
free -h
python3 --version
python3 -m pip --version
docker version --format '{{json .}}'
docker info --format 'OS={{.OperatingSystem}} Kernel={{.KernelVersion}} Architecture={{.Architecture}} CPUs={{.NCPU}} Memory={{.MemTotal}} CgroupDriver={{.CgroupDriver}} CgroupVersion={{.CgroupVersion}} SecurityOptions={{json .SecurityOptions}}'
printf 'Base: %s\nWorker: %s\n' "$BASE" "$WORKER"
docker image inspect "$BASE" "$WORKER" \
--format 'ID={{.Id}} RepoDigests={{json .RepoDigests}} OS={{.Os}} Architecture={{.Architecture}}'
} > "$ROOT/evidence/host-details.txt" 2>&1
cd "$ROOT/encased-0.3.2"
set +e
ENCASED_DOCKER_TEST_IMAGE="$WORKER" \
bash deployment/run-linux-isolation-tests.sh "$BASE" \
2>&1 | tee "$ROOT/evidence/qualification.log"
STATUS=("${PIPESTATUS[@]}")
set -e
printf 'test_exit_code=%s\nlog_capture_exit_code=%s\n' \
"${STATUS[0]}" "${STATUS[1]}" > "$ROOT/evidence/exit-status.txt"
printf '%s\n' "$BASE" > "$ROOT/evidence/base-reference.txt"
printf '%s\n' "$WORKER" > "$ROOT/evidence/worker-reference.txt"
cd "$ROOT/evidence"
sha256sum ./*.log ./*.txt ./*.sha256 > SHA256SUMS
cd "$ROOT"
tar -czf encased-run-results.tgz evidence
sha256sum encased-run-results.tgz | tee encased-run-results.tgz.sha256
printf 'Archive: %s/encased-run-results.tgz\n' "$ROOT"
cat evidence/exit-status.txt
if [[ "${STATUS[0]}" != 0 || "${STATUS[1]}" != 0 ]]; then
echo 'FAILED or incomplete capture: retain the evidence; do not claim containment.'
exit 1
fi
echo 'Supplied probes passed on this setup; independent review is still required.'
ENCASED_RUNSend the evidence: copy the printed archive from your VM to your computer, upload encased-run-results.tgz here in the Encased builder conversation and paste its final SHA-256 line. Keep the original logs unchanged and private. Review for unexpected sensitive content before sharing; if redaction is needed, retain the original privately and identify a separate redacted copy. Do not include API keys, registry login files or customer data.
The website does not run tests on your VM or automatically email evidence. Results and host details are published only after the actual run is checked; passing this suite alone is not independent review or certification.
We will walk you through running the containment tests on a disposable Linux host you control and go through the raw results with you. Free, no obligation. Use a throwaway machine with no customer data or credentials.
The $2,500 AI agent security audit includes a private audit workspace, a signed agreement and a written report for up to 10 agents.