01
Nobody gets a copy.
The repository never leaves your cloud. No clone, no VDI, nothing on the contractor's machine.
When the engagement ends, there is nothing to collect and nothing to leak through a vulnerable package on a laptop you don't manage.
02
The build still passes.
Files a person cannot see are still there for the compiler, the test runner and the dev server. Code that is Occluded compiles, tests run, the app boots, in a real IDE at laptop speed.
Every other way to keep a file out of sight breaks the build to do it.
03
Each person sees only what their task needs.
A contractor on the dashboard ticket sees the dashboard, not the billing engine. An agent scoped to src/web cannot read infra/.
And every file they touched, and every door they tried, is on the record.
demo
A 400-file repo. A contractor on one ticket.
Every file is in one of four states.
- Visible
- Read and write.
- Read-only
- Read, not write.
- Occluded
- Exists for the build. Absent to the person. The signature resolves; the body does not.
- Absent
- Not in the runtime at all. Credentials and data seeds live here.
Anything not explicitly Visible or Read-only resolves to Occluded. Nothing is visible by omission.
The five things teams do today.
| Option | What it costs you |
|---|---|
| NDA and full access | Contractual, not technical. You find out what they saw after they've seen it. |
| VDI | The code stays home, but the session shows them everything, and every contractor hates it. |
| Split the repository | Free, recommended by GitHub, GitLab and Microsoft, and it fails on monorepos and shared types. The mock drifts forever. |
| Perforce protections | Excludes the file, and its own manual says the sync breaks. Perforce controls what syncs. Occlude controls what runs. |
| Ship binaries | Works for a stable library behind a fixed interface. Stale the moment the protected code changes. Occlude is binary delivery with a live build. |
Four of these are free. None of them keep the build green and the code out of sight at the same time.
Observation Mode
Watch for a week, decide after.
Observation Mode is a read-only GitHub app plus build telemetry. For a week it watches, then shows you which files your build, your tests and your last twelve tickets actually touched. Nothing is enforced. Nothing changes for your engineers. Removable in one click.
From that report, a contractor profile is one click. Nobody writes a path rule.
Questions, hardest first.
Can't the contractor just dump the compiler's memory?
On a standard container, yes, and we say so. Occlude's hardened tier runs on gVisor, where
/proc/self/memdoes not exist, and the build process and the person's shell run under different users withptracedenied between them. Until that tier ships, the claim is compartmented, not exfiltration-proof, and we put that in writing.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.
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. Browser, or their own VS Code over SSH. 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. Claude Code, Codex, Cursor and CI connect over MCP. Our published benchmark on agent performance under occlusion is in progress.
Talk to the founder.
Twenty minutes. Bring your last contractor engagement and we'll walk through what Occlude would have shown you.