Local, Managed, Network
The three B3IQ operating modes and how they map to local inference, managed control-plane enrollment, and paid network routing.
B3IQ separates local usefulness from network participation. A machine can be valuable as a local inference host without being ready for paid routed work.
Mode Summary
| Mode | Default | What it enables | What it does not imply |
|---|---|---|---|
| Local Mode | Yes | Local setup, local auth, local API keys, local OpenAI-compatible inference | Cloud enrollment, paid routing, or protocol eligibility |
| Managed Mode | Operator opt-in | Signed enrollment, heartbeats, command polling, support and fleet workflows | Paid public route eligibility by itself |
| Network Mode | Gated | Protocol-registered, route-ready, benchmarked supply for paid hosted routing | Production decentralization claims before launch gates close |
Local Mode
Local Mode keeps the host useful even when the cloud or protocol surfaces are not involved. The wizard, local API keys, model installs, runtime probes, local playground, and local receipts all belong here.
Start in Local Mode unless you are intentionally testing B3IQ managed or paid network workflows.
Managed Mode
Managed Mode enrolls a node in the control plane. The host signs an enrollment challenge with its Ed25519 identity, posts signed heartbeats, and polls for commands over outbound HTTPS. This model works behind normal NAT and firewall setups.
Managed Mode can support:
- Public-safe node inventory and readiness.
- Remote command queues with signed results.
- Support grants that avoid exposing setup tokens or local secrets.
- Broker-managed public routes when explicitly configured.
- Receipt and billing evidence from managed or routed work.
Network Mode
Network Mode is a policy gate, not a toggle. A node and model profile need live evidence before B3IQ should route paid hosted traffic to them.
Identity
Node enrolled and heartbeat is fresh.
Route
Broker route is healthy and public inference is allowed.
Protocol
Node is registered, active, and stake-satisfied.
Model
Profile is installed, network-eligible, benchmarked, and paid-route eligible.
Customer
Gateway key, billing balance, spend cap, and model policy allow the request.
What Claims Are Safe
Describe exact readiness
Say a node is local-ready, managed-enrolled, route-ready, benchmark-observed, or paid-route eligible when those gates are actually true.
Flatten all modes into earning
A local profile, browser GPU preflight, or installed model does not prove billable network route eligibility.
Decision Guide
Install the host agent, complete setup, create a b3iq_local_ key, and use
the local API. You do not need managed enrollment.
Use Managed Mode. The node can publish heartbeats and receive narrow command workflows without opening inbound ports.
Treat that as Network Mode. You need route health, protocol registration, stake, model install, benchmark evidence, paid-route policy, queue health, and customer billing policy.