No Docker. No Postgres. No Redis. No Python. One ~25MB Go binary that runs your entire LLM proxy, tracing, and security stack.
Every dependency is a failure mode. Postgres needs backups, upgrades, and monitoring. Redis needs memory tuning and persistence configuration. Docker adds a layer of abstraction that complicates debugging. Python needs virtual environments and package management.
Stockyard compiles to a single static binary. It embeds SQLite for all storage, serves its own dashboard, and runs its own API server. You download it, set an environment variable, and start it. That is the entire deployment.
The ~25MB binary contains: an OpenAI-compatible proxy with 76 middleware modules, embedded SQLite for traces/costs/config, a Preact dashboard, 16 provider integrations, a CLI, and 29 product modules from cost tracking to adversarial testing.
There is no separate database to install. No message queue. No cache layer. No sidecar. The binary is the entire platform.
Stockyard uses modernc.org/sqlite, a pure-Go SQLite implementation. No CGO, no shared libraries. The database file lives next to the binary. Backups are a file copy. There is no connection pooling to configure, no schema migrations to manage across versions, no replication topology to design.
The tradeoff is real: SQLite is single-writer, single-node. Stockyard will never be a distributed system. For the target use case (one proxy per team, handling hundreds of requests per second), this is not a limitation. It is a simplification. Full writeup on why SQLite.
Upgrades: download the new binary, restart the process. Backups: copy the SQLite file. Monitoring: one process, one port. Debugging: one log stream. Security surface: one binary, no network-accessible databases, no shared dependencies.
This is infrastructure that a single developer can operate. No DevOps team required. No Kubernetes cluster. No Terraform modules. One binary on one server.