Frontier intelligence.
Zero code leaves your machine.
Outfall places an autonomous boundary between your AI coding agents and external clouds. Your agent solves tasks on local silicon, delegating only sterile problem briefs when frontier reasoning is required. Your files, hostnames, and secrets never leave.
What stays private. What leaves.
Watch Outfall isolate your machine from external models in real time. Routine tasks never touch the wire; frontier tasks receive pure mathematical briefs.
[WIRE DARK — ZERO EGRESS] Task resolved in-perimeter on host machine. No network connection opened. Zero tokens transmitted to external clouds.
Three steps to sovereign AI.
No source code leaves your machine. No cloud proxies to blindly trust. Your model writes the brief; only the brief crosses.
Solve on local silicon first
Routine engineering queries stay inside your perimeter.
When your agent inspects files, lints syntax, or generates unit tests, Outfall executes the loop locally on your machine. Over 70% of developer tasks are resolved in-perimeter with zero cloud API spend and sub-millisecond response time.
Delegate the problem, not the code
Frontier models receive the question, never your files.
When an obstacle genuinely requires frontier reasoning, Outfall never uploads your workspace or active files. Instead, your local agent authors a sterile, self-contained mathematical brief. The cloud sees an isolated reasoning problem, solves it, and returns the logic.
Deterministic floor at the wire
Infallible mathematical protection before packet release.
Unlike prompt filters that can be jailbroken, Outfall enforces a deterministic mathematical floor. Machine paths, private IPs, API tokens, and credentials are mechanically blocked before a single packet can exit your hardware.
Real briefs through the privacy floor.
Every example below is verified against the real Outfall privacy gate. Observe how worker briefs are inspected and sanitized before packet release.
DELEGATE refactor an authentication module in /home/dana/work/acme-portal that logs full card numbers to a payments API, email [email protected], ticket ACME-4471
refactor an authentication module in [file] that logs full card numbers to a payments API, email [email], ticket [ref]
Architectural certainty, not promises.
Traditional AI gateways ask you to trust legal checkboxes and cloud provider policies. Outfall replaces trust with architectural guarantees.
Cloud Developer AI
Your entire repository uploaded to remote servers.
Uploads full file trees, git history, and local files to external clouds.
Protected only by corporate privacy policies and terms of service.
Billed on external tokens for every keystroke and routine file scan.
Completely inoperable when offline or behind airgapped firewalls.
Centralized Proxies
Forwards raw prompts through a remote relay.
Still transmits raw code across the internet to the cloud model.
Relies on prompt-based LLM classifiers vulnerable to jailbreaks.
Continuous token spend; does not resolve tasks on local silicon.
Hard failure if the proxy service or internet is unreachable.
Outfall Runtime
Your model writes the brief. Only the brief crosses.
0 source files cross. Worker authors sterile, token-bounded briefs.
Deterministic fail-closed boundary halts credentials before egress.
Over 70% of routine edits handled on local silicon at $0 cost.
Fully autonomous offline; delegates only when frontier scale is required.
Connect at launch. One command.
When the private beta opens, Outfall will expose a local MCP server and drop-in HTTP proxy at http://127.0.0.1:8787. These are the integrations being tested with the first invite wave.
claude mcp add --transport http outfall http://127.0.0.1:8787“The worker authors every byte that leaves the machine.”
When an AI agent uploads your entire repository to cloud models, your intellectual property and machine perimeter are already breached. Corporate policy agreements and vendor checkboxes do not protect against data breaches, training pipeline ingestion, or cloud leaks.
Outfall is built on an architectural invariant: frontier models receive the problem, never the machine.
Your agent inspects files locally, solves routine tasks on your device silicon, and authors a sterile problem brief when frontier reasoning is required. The cloud solves the logic, and your local agent applies the fix in-place.
Clear answers to common questions.
No marketing ambiguity. Everything you need to know about the privacy boundary.
Not yet. Outfall is in pre-release and the package has not been published to PyPI or the uv registry. Join the waitlist and we will email you the install instructions as soon as your beta invite is ready.