Stockyard runs on your machines. Prompts, completions, traces, and audit logs stay on your network. No SaaS dependency, no third-party data sharing, no vendor lock-in.
One static binary. One SQLite file for state. Download, run, done.
Every prompt and completion. Stockyard proxies requests to LLM providers, but the proxy itself runs locally. Your request content is never stored or processed by a Stockyard server.
All traces and cost data. Lookout writes traces to your local SQLite database. Query them through the API or dashboard without sending data anywhere.
Audit ledger entries. Brand's tamper-proof hash chain lives in your database. You control access and retention.
Provider API keys. Keys are encrypted with AES-256-GCM in SQLite. They never appear in logs or API responses.
Most LLM proxy tools need Redis for caching, Postgres for state, Docker for isolation, and sometimes a dedicated queue. Stockyard needs none of these. Everything is compiled into one binary using pure-Go SQLite.
This matters for self-hosting because fewer dependencies means fewer things to secure, patch, monitor, and keep running. Your attack surface is one process and one file.
~25MB binary + one .db file = complete system
Stockyard runs on bare metal, VMs, containers, or PaaS. If it runs Linux, it runs Stockyard. Common deployment targets include Railway, Fly.io, a VPS, or a Raspberry Pi in a closet. The binary is statically compiled with no CGO dependencies — it runs on any Linux system without installing libraries.
If you don't want to self-host, Stockyard Cloud runs the same binary on managed infrastructure. But the self-hosted version is the same code, same features, same binary. There's no "enterprise edition" that locks features behind hosting requirements.
Download the binary. Run it. Your LLM proxy is live, your data stays local, and you control everything.
Install Stockyard