System Overview
How customer-owned GPU machines, the host agent, account dashboard and gateway work together.
B3IQ hosts customer-owned bare-metal GPU machines or ships them to their owners. The host agent supports local inference and managed operation. An account's hosted gateway key selects only that account's machines. There is no public inference pool or external provider fallback.
Components
| Component | Runtime | Responsibility |
|---|---|---|
| Host agent | Go service on the machine | Local identity, inventory, setup APIs, runtime and model management, local auth, receipts, heartbeats and command polling |
| Setup wizard | React/Vite at /setup | Setup and local owner access on a provisioned machine |
| Control plane and gateway | Cloudflare Worker and D1 | Account-scoped machine inventory, signed enrollment, commands, owned-machine routing, usage and operating records |
| Customer dashboard | Authenticated frontend | Your machines, models, keys, SSH, earnings and payout records |
| Public site | Cloudflare Worker static assets | Machine configurations, model and hardware planning, ownership terms and product documentation |
Local and managed use
Provision and claim
B3IQ provisions the machines it hosts or ships. Fleet enrollment uses a B3IQ-issued code, and claiming binds a provisioned machine to its account.
Run locally
The host serves its setup wizard, local keys, installed models and local OpenAI-compatible endpoints. Local inference does not require enrollment.
Manage remotely
The machine signs outbound heartbeats and polls for commands over HTTPS. The account dashboard exposes authorized operational controls.
Route your application
A gateway key discovers and calls matching models on machines your account owns. Health, installed-model matching, key scope and incident controls apply. A missing eligible owned machine produces an error.
State and privacy boundaries
The machine retains local configuration and application state. The control plane retains enrollment, commands, heartbeats, account and operating records. Receipts and usage records do not turn a request into owner earnings.
Ordinary gateway requests pass through the gateway in memory. Private jobs use ciphertext envelopes addressed to an owned machine. Read the privacy boundary before choosing a path. Neither path currently claims to hide execution content from the machine's operator.
Optional earnings
Earn mode offers idle capacity under the owner's hosting arrangement. It withdraws that machine from B3IQ inference routing. Estimates, revenue accrual and paid funds are separate states; consult the machine's deal and signed-in earnings page.
Historical records
The former public explorer and blockchain-oriented serving narrative are retired. Shared receipt and money types and existing historical settlement records remain. They are separate from current USDC purchase rails and from current hourly rental revenue. See operating evidence.