Security proxy for agent and LLM traffic: isolates keys, filters what leaves, keeps access reliable
The hub is configuration-only in this release. Nothing here opens a listener, builds a client or contacts a hub.
The tables below are parsed and validated only, and only behind the hub cargo feature (not in the default set). A binary built without the feature refuses a config that contains [hubs], [hub] or [accounts]. With the feature on, reiki check accepts them, but nothing serves or uses them. Without these tables nothing changes.
[hubs.main] # a remote hub this instance reaches as an edge
url = "https://hub.example.net:4443" # https, or http on a loopback address
token_file = "/etc/reiki/hub/edge.token" # raw token the hub issued; mode 0400
ca_file = "/etc/reiki/hub/ca.pem" # optional PEM CA certificates for this hub
accounts = ["acct-a"] # account labels routed through this hub
timeout_secs = 300 # default 300, 1 to 3600
[hub] # this instance serves edges
listen = "127.0.0.1:4443" # loopback only: no TLS yet
[hub.edges.peer-a]
token_sha256 = "<64 hex>" # SHA-256 of the token this edge presents
allow_from = ["acct-a"] # account labels this edge may send for
max_concurrent = 8 # 0 means unlimited
max_tokens_per_day = 2000000 # 0 means unlimited
[accounts.acct-a] # one account: its key(s) on one upstream
upstream = "zen"
keys = ["zen-a"] # key names from [keys.*], tried in order
shared = false
[accounts.acct-a.limits] # absent means no shaping
preset = "zen-free" # one of zen-free, openrouter-free
rpm = 20 # 0 means unlimited, for every field below
tpm = 60000
concurrent = 2
daily_requests = 200
daily_tokens = 0
-, at most 63 characters.allow_from and a hub’s accounts name existing accounts.