Roadmap
Current B3IQ capabilities, production launch gates, and near-term roadmap priorities.
This page summarizes the active roadmap source of truth. It is intentionally conservative: completed pilot evidence is called out, and production blockers stay visible.
North Star
B3IQ is a neocloud for AI inference: customers buy or rent-to-own bare-metal GPU servers that B3IQ hosts or ships and operates as managed, admin-approved nodes, consumed through standard OpenAI-compatible HTTP endpoints plus B3IQ-native receipts, billing, route readiness, and node status. Routing is own-nodes-strict (a customer key routes only to that account's own machines) and pricing/payouts are in USD.
The supported contract is endpoints, metadata, receipts, billing, node status, and documentation. Agent SDKs, bespoke product adapters, and workflow authoring are out of scope.
Current Capabilities
| Area | Status | Notes |
|---|---|---|
| Local node | Live pilot | Linux, macOS, and Windows host agent with setup wizard, local auth, local keys, model installs, playground sessions, support grants, and local OpenAI-compatible chat |
| Hosted gateway | Pilot | Public /v1/api/models, /v1/api/stats, /v1/api/pricing, and authenticated /v1/api/chat/completions with customer-owned gateway keys, paid routing foundations, streaming receipt metadata, and redacted accounting |
| Real routed work | Proven in dev | Deployed real-work smoke has exercised completion, generation, streaming, and private process work through eligible supply with receipts, debits, payouts, and telemetry |
| Settlement | Pilot | The payout settlement proof deployment finalizes payout batches; live settlement counts are published on the explorer |
| Public explorer | Live | b3iq.org shows install paths, model eligibility, node readiness, telemetry, protocol classes, and settlement details |
| GUI installers | Mixed | macOS DMG is signed/notarized as a public pilot. Windows NSIS is Authenticode-signed as a public pilot. Linux GUI packaging remains gated on package trust and VM smoke evidence |
Production Launch Gates
Make network supply durable without active SSH sessions or fragile user-service assumptions.
Complete clean and reused machine GUI smoke tests for the desktop installers.
Add Linux package trust and real Ubuntu Desktop install, launch, reinstall, uninstall, and state-preservation smoke tests.
Enforce signed release metadata in production installers and update flows.
Harden hosted customer auth, roles, audit logs, approval workflows, rate limits, abuse controls, and incident controls before opening public traffic.
Wire the new secured-operator settlement runner into a scheduled environment with monitoring. Worker cron now handles no-key finalization of already-submitted payout batches, but private-key broadcast remains on the secured operator path. The traffic warmer scheduler is now the minimum recurring real-work generator for request, token, receipt, and payout telemetry.
Priority Tracks
Productionize the first approved, benchmarked, paid-route-eligible supply path, keep real-work smokes running, and make route health durable after operator sessions close.
Close Linux package trust, production signed manifest enforcement, rollback smokes, clean/reused machine validation, and production GUI installer evidence.
Turn settlement pilots into recurring USD payout operations, keep signed receipts and payout-batch proofs as accountability evidence, and expand reputation/health snapshots without exposing private payloads. On-chain staking, disputes, and slashing are no longer the product direction.
Keep consumer-edge paid serving separated from managed GPU routing, and keep the host opt-in and capability-advertisement path clearly scoped.
Keep encrypted private transport as the active baseline while implementing verified confidential CPU attestation before claiming privacy from node operators.
Keep OpenAI-compatible endpoint behavior, OpenAPI specs, stable error codes, examples, sandbox mode, and docs as the official developer surface.
Claim Policy
Say what is evidenced
Use precise labels such as local-ready, route-ready, benchmark-observed, paid-route eligible, settlement-pilot, and production-gated.
Call the network production before gates close
A real dev route and payout pilot are meaningful evidence, but production gateway traffic needs installer trust, supply durability, auth, billing, abuse, and settlement automation.