Four components, one coherent system.

The appliance is the only component that ever sees a prompt. It runs the LLM, the retrieval index, and the policy engine on hardware we ship to your office.

Disks are encrypted with TPM-bound keys. The OS is signed, the kernel is signed, and fleet updates roll out through the same signed-manifest pipeline.

Two variants today — a silent desktop Micro for small offices and a 1U rack-mount Starter for production floors — with a dual-GPU Pro configuration for 70B-class models.

Every request into or out of the appliance goes through the gateway. It authenticates virtual keys, evaluates OPA policy, applies rate limits, and emits an audit event before a single token is generated.

Policy is centrally authored but locally enforced. We push new rules to the fleet as signed bundles; the appliance verifies and swaps without downtime.

The gateway is OpenAI-compatible by design, so existing SDKs and tools drop in with a single base-URL change.

The portal is where you and we manage the fleet — list appliances, mint virtual keys, review audit heads, inspect billing, and push policy.

It’s a Next.js app running behind your IdP. It only holds per-request state; logouts clear everything, and session cookies are JWE-encrypted.

We use the same portal ourselves: no side-channel tools, no hidden admin consoles — what you see, we see.

The central plane runs the registry, config service, billing aggregator, audit aggregator, and event bus. It’s what lets us operate thousands of appliances we don’t physically own.

It never sees a prompt or a response — only metadata (heartbeats, audit heads, usage rollups, signed policy bundles).

Everything is written in Go, deployed on Debian, fronted by apache2, and hardened with systemd. No unmanaged dependencies.