Radar / Ideas / FencedBox: the on-prem appliance that…

FencedBox: the on-prem appliance that lets outsourced teams run coding agents without client code ever leaving the building

daily ideaambitiousJEV confidence 0.47JEV monetization 0.482026-10-16
OutcomeOutsourced dev teams ship AI-accelerated code while proving to every client that not a byte of source ever left the building.

The problem

Client contracts increasingly forbid feeding proprietary code to cloud AI tools, and the failures are public: Samsung banned generative AI company-wide in 2023 after engineers leaked source code, and in October 2026 researchers showed GitHub Copilot CLI exfiltrating .env secrets via encrypted prompt injection. Outsourced and staff-augmentation firms are stuck: ban AI and lose velocity, or use it and breach client NDAs.

The idea

A 1U on-prem appliance (or signed VM image) that combines a Rust hypervisor sandbox for coding agents, KV-cache-compressed local models that run bigger-than-RAM from SSD, and a Jev decision gate on every egress action: any tool call touching the network or reading outside the repo gets a calibrated allow/deny verdict with a signed audit log. The dev team gets agent velocity; the client gets a tamper-evident log proving code never left the box.

Why now

Three radar launches in 48 hours make this newly buildable: Capsem, Google's Rust hypervisor sandbox for AI coding agents (Oct 15); Telperion's 4x KV-cache compression for Qwen3.8-27B (Oct 15); Janas, which runs LLMs bigger than RAM from SSD (Oct 14). And the Oct 6 Adversa disclosure of Copilot CLI secret exfiltration just made cloud agents on client code radioactive for vendor-risk teams.

What it combines

capsem-google-s-rust-hypervisor-sandbox-for-ai-coding-agents (hypervisor isolation) + telperion-qwen3-8-27b-mla-gla-4x-kv-cache-compression-for-qwen3-8-27b (local frontier-class inference) + janas-run-llms-bigger-than-your-ram-from-ssd (SSD offload so a 27B model runs on appliance hardware) + autotrust-jev-35b (calibrated egress allow/deny). The mix matters because sandboxing alone cannot stop an agent from phoning home; only the judgment gate on egress turns isolation into provable compliance.

MVP

Weekend MVP: a signed VM image with a Firecracker sandbox running one coding agent, a local Qwen3.8-27B with Telperion KV compression, and a Jev-gated egress proxy that logs every outbound connection with allow/deny verdicts. Deliberately skip: physical hardware, multi-tenant management, and the tamper-evident ledger (start with append-only signed logs).

How it makes money

Budget owner: CISO / vendor-risk plus the CTO of outsourcing firms, from the existing VDI and security-tooling budget (replacement budget). Pricing anchor: E2B Pro at $150/month base plus per-second usage (~$0.166/hr per 2vCPU/4GiB sandbox), with Enterprise at a $3,000/month minimum (https://upstash.com/blog/ai-agent-sandbox-providers-compared-2026 and https://tech-insider.org/e2b-vs-modal-vs-daytona-2026/). A fixed-price appliance amortizes far below metered cloud sandboxing at fleet scale. Willingness-to-pay: enterprises already budget five figures annually for agent sandboxing (E2B Enterprise $3,000/mo minimum), and Samsung's 2023 company-wide AI ban after the source-code leak (https://www.moneyweb.co.za/news/ai/samsung-bans-staffs-ai-use-after-spotting-chatgpt-data-leak/) shows the pain this budget protects against.

The moat

Microsoft/GitHub monetize cloud tokens and Copilot seats; an appliance that removes client code from their cloud cannibalizes that revenue, and they would have to become a hardware/appliance vendor and rebuild their agent stack for offline hypervisor execution, which fights their Azure growth story. E2B, Daytona and Modal are cloud-native multi-tenant businesses; on-prem appliances destroy their unit economics.

Distribution

Sell to the client side, not the dev shop: enterprises whose vendor contracts mandate data residency (banks, healthcare) buy FencedBox for their approved vendor panel, and vendors adopt it as the price of the contract. Second channel: MSP and VDI resellers who already sell compliance appliances.

Why it wins

E2B, Daytona and Modal sell cloud sandboxes, so code still sits on third-party infrastructure and fails client data-residency clauses. VDI keeps data on-prem but gives developers a 1990s terminal, not an agent. FencedBox is the first agent-native, on-prem appliance with provable egress control.

Risks

Biggest risk is hardware economics: appliance margins and support burden can kill an indie. De-risk by shipping the signed VM image first on the customer's own servers (zero hardware), proving the wedge before ever building hardware.

Build it with

Repo to start from

fencedbox: open-core repo with the sandbox runtime, the egress gate, and the audit-log format; appliance firmware and the management console stay closed.

Evidence

Get the week's best AI launches, plus 3 ideas worth building

One email every Saturday. Ranked by traction, not hype. Free.