Valkey

v1.0.7

Shared state on the Valkey you already run.

What it is Points Busbar’s cluster-shared governance state at the Valkey you run.

When to use it You already operate Valkey and would rather not stand up another database.

CategoryStore StatusAvailable

Overview

Some fleets already run Valkey (the Linux Foundation–hosted, BSD-licensed fork of Redis that the ecosystem has largely standardized on) and would rather point Busbar at it than stand up another database. The Valkey store does exactly that: virtual keys, usage, and the audit trail live in the Valkey you already operate, shared across every Busbar node behind it.

It keeps the same discipline as the other stores: each node enforces against fast in-memory counters and reconciles spend into Valkey behind the request. Keys, usage, and audit are cluster-shared; the hard budget cap is enforced per node and reconciled durably, so nothing waits on a network round-trip inside the hot path.

It implements the same Store contract the Memory, SQLite, and Postgres stores do, and speaks the standard RESP wire protocol, so it works unmodified against any server that speaks it, including a Redis one if that is what your fleet still runs.

Install it

Download the signed tarball for your platform (button above), drop it in plugins/, and set:

store:
  module: valkey
  settings: { url: "redis://:password@host:6379/0" }

The plugin, its crate, and its config alias are all valkey. The connection string keeps the redis:// URI scheme: that is the standard RESP protocol scheme Valkey itself speaks, not a product name. Independently versioned from busbar itself: pin both explicitly in production. Requires busbar 1.5.0+.

Prefer to install by hand? No plugins.fetch config needed: download the signed tarball (links above), drop it in your plugins.dir, and busbar loads it at boot; signature and trust checks still apply. You can also push it live over the admin API. See the plugin install docs.

Settings

Setting	Required	Default	Description
`url`	Yes	—	Connection string using the standard `redis://` RESP URI scheme (`rediss://` for TLS). Any password in it is scrubbed from error messages.
`connect_timeout_ms`	No	`10000`	Initial TCP connect timeout in milliseconds, so a blackholed host fails fast at boot rather than hanging.

← Back to the Plugin Store