System Overview
The B3IQ component map across host agent, setup wizard, control plane, protocol explorer, and contracts.
B3IQ is a neocloud: customers buy or rent-to-own bare-metal GPU servers that B3IQ hosts or ships and operates as managed, manually onboarded inference nodes, fronted by a hosted control plane and gateway. The same host software also runs local-first — the local node must work without cloud enrollment, and managed and network features build on top of that local baseline. Routing is own-nodes-strict and payouts are in USD.
Components
| Component | Runtime | Responsibility |
|---|---|---|
| Host Agent | Go service | Local identity, inventory, setup APIs, runtime probes, model jobs, local auth, API keys, receipts, heartbeats |
| Setup Wizard | React/Vite static app | Browser UI served by the host agent at /setup |
| Control Plane | Cloudflare Worker + D1 | Enrollment, node inventory, heartbeats, commands, receipts, billing, public network APIs |
| Protocol Explorer | Cloudflare Worker static assets | Public b3iq.org site, install scripts, network status, model and node views |
| Registry & settlement | Network services | Node registry primitives and payout settlement pilot |
Local Flow
Initialize host state
The host agent creates local config, identity, setup token state, runtime records, and local service state.
Serve setup
The setup wizard opens from the host agent at /setup/ and calls local APIs.
Claim ownership
The operator creates the local owner account, reviews hardware, configures runtime/model posture, and creates scoped local API keys.
Use local inference
Local clients call /v1/models and /v1/chat/completions through
b3iq_local_ credentials.
Managed Flow
Managed enrollment avoids inbound firewall setup. The node signs outbound heartbeats and polls for commands over HTTPS.
Public Protocol Flow
b3iq.org reads public-safe network data from the control plane. It can show
route readiness, model classes, public node status, receipt summaries, settlement
metadata, and payout batch state. It must not expose prompts, outputs, API keys,
customer IDs, exact private routes, raw tunnel details, local URLs, or raw TEE
material.
Use b3iq.org for B3IQ product and route-readiness state. Use
explorer.b3.fun for broader B3 ecosystem context.
State Boundaries
| State | Location | Notes |
|---|---|---|
| Node config | B3IQ home config.json | Node ID, identity, setup token state, runtime config, local setup state |
| Local app state | state.db next to config | Jobs, audit events, receipts, users, sessions, API keys, support grants |
| Control-plane state | Cloudflare D1 | Enrolled nodes, commands, heartbeats, receipts, private job metadata, billing rows |
| Public settlement state | Settlement network | Registry state, approval, public commitments, payout proof logs |
| Generated downloads | b3iq.org static assets | Install scripts, release metadata, public GUI pilot artifacts |
Design Principles
- Local-first must work without cloud enrollment.
- Managed and network features should not require inbound firewall or router setup.
- Host-agent actions are narrow and explicit, not arbitrary shell access.
- Browser code should not hold infrastructure credentials.
- Public settlement surfaces carry commitments and summaries, not private payloads.