// wing 02 · 100% local-only · air-gapped · cmmc level 2 · itar · scif
Private & Air-Gapped Coding Agents on Your Own GPUs.
Castor Wing 2 runs coding agents entirely on-prem: zero cloud API calls, zero code egress. Outbound tools are excluded at compile time, engine ports bind to loopback only, and every tool call lands in a per-task JSONL audit log — so source in a CMMC Level 2, ITAR, or SCIF enclave never leaves the machine. The boundary is a 5-layer stack verified across 137 attack vectors, with host-OS default-deny networking as the final guarantee.
Path layers
5
Test vectors
137
Blocked / Allowed
123 / 14
AST grammars
27
Single-stream decode
70.4 tok/s
n=1 · 78-day mean
Concurrent decode
260 tok/s
aggregate · n=4 concurrent · warm KV prefix
Verified corpus
2.77B
78-day local ledger · 97% tool success
Cloud calls
0
air-gapped · egress compiled out
Five Layers, Verified Across 137 Vectors
Every file path and shell command passes a deterministic
pipeline before it touches the filesystem: 137 verified test
vectors, 123 blocked / 14
allowed — reproducible from the open-source test suite
(src/tools/sandbox/tests.rs:527-548).
- L1
resolve_workspace_root
Canonical root anchor
- L2
verify_symlink_containment
Realpath symlink-escape refusal
- L3
refuse_out_of_tree
Strict boundary containment
- L4
normalize_traversal
Null-byte / tilde / device-name / .. collapse
- L5
check_binary
Magic-number sniff → BinaryFileError
Kernel, Shell & AST — Three Hard Gates Below the Path Pipeline
Linux Landlock Kernel Confinement (5.13+)
src/tools/shell/process.rs
On Linux, every shell child is confined to the workspace root by a Landlock ruleset at exec; unsupported filesystems fall back to the lexical gates, which run on every platform.
Lexical Shell Scanner + Dead-Man Fuse
src/tools/shell/scanner.rs
Static lexical scan of the command line: destructive targets, protected roots, and a synthetic canary trip FatalDeadManFuseError before any execution.
27-Grammar Tree-Sitter AST Syntax Gate
src/tools/ast.rs
Every file commit is parsed in memory against 27 bundled tree-sitter grammars. Malformed code is rejected and the write rolls back atomically.
137
total vectors
123
blocked
14
allowed
Zero Egress Is a Compile-Time Decision
# --no-default-features · --features mcp,ast
--no-default-features strips the default
toolset. --features mcp,ast compiles in only
the stdio MCP surface and the AST gate — the paper
research feature is excluded at compile time, and external web tool
config stays disabled. Pair this binary with a host-OS
default-deny outbound firewall or air-gapped enclave networking
for strict zero-egress enforcement.
Compile-Time Offline Binary Profile
- Stdio-only MCP. The server speaks to the host process over stdio and opens no network listener.
- Loopback-only ports. Engine, status, and SSE-proxy ports (18020–18022) bind to 127.0.0.1 — nothing listens on a public interface.
- No outbound tool code. The
paperresearch feature is excluded at compile time by this profile, and external web tool config is disabled — the binary carries no outbound network tooling. - Strict enforcement. Pair the build with a host-OS default-deny outbound firewall or air-gapped enclave networking: `ss -ltnp` / `nmap` on the host then show only loopback listeners.
Two Ways to Stand It Up
Turnkey Local Sprint
$1,500
One-Time · 48-Hour Setup
Dedicated local inference hardware stood up in a day — no weeks of vLLM / CUDA / quantization tuning.
- vLLM 0.33 / llama.cpp + MTP/DFlash2 tuning for your GPUs (RTX 3090/4090/5090 or L40S/H100)
- Air-gapped profile built (`--no-default-features --features mcp,ast`), external web tool config disabled
- Workspace sandbox & shell-policy hardening
- Throughput benchmark handoff + loopback egress audit
Fixed-Scope Air-Gap Pilot
Fixed-Quote
10–50 Seats · 1–3 Months
A fixed-scope compliance pilot for DIB, defense, finance, and healthcare enclaves where source code cannot touch external APIs.
- Commercial dual-license (AGPL-3.0 opt-out)
- Air-gapped binary (`--no-default-features --features mcp,ast`): `paper` research feature excluded at compile time
- NIST 800-171 / CMMC Level 2 / ITAR per-slice JSONL audit ledger
- Dedicated deployment SLA & custom model qualification
Direct line: m.abdullah.ali.2523@gmail.com · Open source (AGPL-3.0): github.com/usecastor/castor
Five Questions, Answered for the Auditor
Can source code or build artifacts leave the enclave at all?
No. The air-gapped profile (cargo build --release --no-default-features --features mcp,ast) excludes the paper research feature at compile time and retains the stdio MCP surface; the engine, status, and SSE-proxy ports (18020–18022) bind to 127.0.0.1 only, and external web tool config is disabled. With a host-OS default-deny outbound firewall or air-gapped enclave networking in front of that build, nothing the binary does can reach an external host.
What kernel-level confinement does the sandbox use?
On Linux (kernel 5.13+), every shell child process is dropped into a Landlock ruleset at exec that restricts its filesystem access to the workspace root. On every platform — Linux, Windows, and macOS — the 5-layer path pipeline (root anchor → symlink containment → out-of-tree refusal → traversal normalization → binary sniff) and the lexical shell scanner run beneath it.
How do I prove the egress boundary to a CISO or auditor?
Build with the --no-default-features --features mcp,ast profile, capture nmap / ss -ltnp output showing only loopback listeners on 127.0.0.1:18020–18022, and present the per-slice JSONL audit ledger that records every tool call and its verdict. The 137-vector test table at src/tools/sandbox/tests.rs:527 (123 blocked / 14 allowed) is reproducible from the open-source test suite.
Is the AST syntax gate a hard requirement or a toggle?
It is a compile-time Cargo feature: ast is included in both the default build and the air-gapped mcp,ast profile, so every production binary carries the gate, and once compiled in it cannot be disabled at runtime. Every file commit is parsed in memory against the 27 bundled tree-sitter grammars before it touches disk; malformed code is rejected and the write rolls back atomically.
How is deployment priced?
Two engagements. The Fixed-Scope Air-Gap Pilot is a quote-based engagement for 10–50 seats over 1–3 months: commercial dual-license (AGPL-3.0 opt-out), the air-gapped binary, the per-slice JSONL audit ledger, and a dedicated deployment SLA. The 48-Hour GPU & vLLM Setup Sprint is a flat $1,500 one-time fee that stands up your dedicated local inference hardware. Both are scoped through a direct email.