Roadmap
Current B3IQ service boundaries, planned capabilities and the evidence needed to accept a release.
The repository's active roadmap is the implementation source of truth. This public overview describes the service boundary and how to assess planned work; it does not mark a production launch gate complete.
Current direction
Customer-owned GPU machines are the product. Local inference and managed owner-scoped gateway use are separate from optional hourly capacity earnings. There is no shared public serving pool, third-party provider fallback or blockchain-based enrollment requirement for customers.
Source-supported capabilities
| Area | Boundary |
|---|---|
| Local machine | Host agent, setup wizard, local auth and keys, runtime/model management and OpenAI-compatible inference |
| Account gateway | Model discovery and requests scoped to the account's machines and key restrictions; failures remain within that boundary |
| Managed operations | Signed enrollment and heartbeats, narrow commands, machine health and authorized dashboard evidence |
| Private jobs | Encrypted asynchronous transport to an owned enrolled machine; verified confidential execution is not active |
| Optional earnings | Hourly idle capacity under the machine's hosting arrangement, separate from free owner inference |
Planned work
Serverless-style experiences, training workflows and verified confidential CPU/GPU execution remain planned until their own supported contracts and operational acceptance are published. Do not infer availability from a model guide, animation or future interface.
Release acceptance
Before relying on a new capability, ask for dated evidence on the intended machine, model and deployment. Useful checks include authenticated discovery with the intended key, a successful request, persistent service health, provisioning/update trust, recovery behavior and the support scope.
A local test, merged change and deployed release are different states. Historical pilot proof does not establish today's availability or performance. For earnings, estimated utilization and rates, accrued revenue and paid funds also need distinct evidence.
Retired work
The old public node explorer, speed leaderboard, public rate pages, provider fallback and decentralized serving narrative are retired in the October 3, 2026 source change. Historical records are preserved where needed; they are not future commitments to reopen those services.