Plugin Store · Store
Memory
RAM store — zero setup, ephemeral. Available
Busbar’s governance layer — virtual keys, per-key budgets, RPM/TPM rate limits, and usage metering — needs somewhere to keep its counters. The Memory store keeps them in process RAM, so there is nothing to install, provision, or connect: deploy the binary and it works.
Enforcement is always in-memory anyway (a hard cap checked on the hot path), so the Memory store is simply that same state with no durable mirror behind it. It costs effectively nothing and adds zero latency.
The trade is durability: a restart starts the counters fresh. That’s the right default for a single node, a dev environment, or a stateless tier fronted by something else. When you need budgets and keys to survive a restart — or to be shared across a fleet — swap in a durable store (SQLite for one node, Postgres for a cluster). The switch is one config line; nothing else changes.
Built into the core — the default when no store is configured.