FAQ

Can't the contractor just dump the compiler's memory?

Not directly, though until the hardened runtime ships the claim is compartmented, not exfiltration-proof, and we put that in writing. The compiler runs as a different user on the build's side: the contractor's processes cannot attach a debugger to it or open its memory. Two routes remain. A kernel bug could cross that line on a standard container, which is why the hardened runtime is designed for gVisor, a user-space kernel with far less to attack. And a test the contractor writes runs on the build's side, so its output is sanitised and the attempt is on the record. Credentials and data seeds are never in that memory at all: they are Absent.

Perforce has done this for thirty years.

It has, and its own manual says what happens: exclude the read and the sync breaks. Perforce controls what syncs. Occlude controls what runs.

Isn't this an agent gateway?

No. Gateways decide whether an agent may call a tool. Occlude decides what exists on disk when it does. And when the outsider is a human with an editor and no agent, a gateway has nothing to intercept.

We already use Codespaces or Coder. Isn't that this?

They keep the code off the laptop, and so does Occlude. Inside the workspace they stop: a Codespace token is scoped to the whole repository, so everyone who can open one can read every file. Occlude puts the four states inside the workspace. In one session the contractor sees the dashboard and the compiler sees the billing engine, and the ledger records which was which.

Where does it run, and what do I operate?

In your cloud. You install one Helm chart and connect your source host and your SSO. Occlude starts an isolated workspace per session and closes it when the grant ends. You operate nothing per contractor. For a trial, and for Observation Mode, we host the same thing single-tenant.

Who is Occlude not for?

Teams whose repositories already match who may see what, or whose codebase is small enough that splitting it is cheap: repository permissions do the job. And anyone who needs exfiltration-proof isolation today, before the hardened runtime ships. Regulated and self-hosted teams are who it is built for, because it installs in your cloud.

Do my developers have to change anything?

No. Your repo stays on GitHub, CI stays, your engineers keep their editors. Occlude is a door for outsiders and agents.

What does the contractor's experience feel like?

A normal IDE. The browser workspace now; their own VS Code over SSH is the next door. Autocomplete works across modules they cannot read. If it felt like a remote desktop we would have failed.

What do I get at audit time?

One export: the profile that person ran under, every file they touched, every refusal and which rule refused it.

Does it work with AI agents?

Agents run under the same boundary. The door for Claude Code, Codex, Cursor and CI is MCP, and it is next after the human door. Our published benchmark on agent performance under occlusion is in progress.