Escrows opened by the allowlisted wallet
We operate the privileged escrow wallet and assign escrows to one broker only.
Broker infrastructure for Gonka inference
Dedicated devshard capacity. One broker API.
OpenBroker handles the escrow operator wallet, devshardctl runtime, version routing, observability, and GNK-native accounting for brokers that need inference access after public node gateways go away.
OPENBROKER CONTROL PLANEreserved capacity
Activation
100 GNK
Broker keys
obk-
Fallback
none
Runtime
v1/v2
Each broker gets isolated accounting and capacity. Traffic stops when the broker balance or dedicated devshard capacity is unavailable.
What brokers should not operate themselves
Running as a broker should be about users, billing, and products. The low-level devshard work belongs in a control plane with explicit accounting and visible capacity.
Dedicated gateway state per broker
Broker traffic can be isolated through its own devshardctl instance and state.
No node4 fallback
OpenBroker is designed for the post-node4 flow: if capacity is unavailable, the request stops.
Built for broker observability
Dashboard and Prometheus metrics are broker-labeled: balance, runtime split, devshard ID, model, request status, token volume, latency surfaces, and escrow state.