> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3iq.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Local and Managed Use

Local inference, account-scoped managed operation and optional Earn mode on your GPU machine.

A B3IQ machine can serve local inference without managed enrollment. Managed
operation adds account access and remote visibility. Optional Earn mode is a
separate choice about idle capacity, not a public inference-pool enrollment.
The URL of this page retains its historical name for existing bookmarks.

## Mode summary

| Mode | What it enables | Boundary |
| --- | --- | --- |
| Local | Local setup, owner auth, local keys, runtime/model management and inference | No cloud enrollment required |
| Managed Bare metal | Account dashboard, signed enrollment/heartbeats, commands and owned-machine gateway requests | Your account's machines; matching models, healthy runtime/route and key scope still apply |
| Earn | Optional hourly idle-capacity rental under the hosting arrangement | The machine is removed from B3IQ inference routing until returned to Bare metal; earnings are not guaranteed |

## Use your own machine

B3IQ provisions the machines it hosts or ships. Complete local setup and use a
`b3iq_local_` key for local endpoints, or claim the managed machine to your
account and create a gateway key. [Private fleet](/guides/private-fleet)
walks through account-scoped access.

The gateway never selects another account's machine or a third-party provider
as fallback. If no eligible owned machine can serve the request, it fails.
Legacy fields such as `network_eligible` and `paid_route_eligible` do not turn
planning guidance into a deployment-readiness claim and are not a public-pool
subscription. [Model readiness](/operators/model-readiness) explains their
retained diagnostic role.

## Verify readiness separately

An installed matching model, healthy runtime and route, current heartbeat,
account ownership, key restrictions and incident controls matter for owner
requests. Promotion flags and observed benchmarks are not prerequisites for
owner use. Verify model discovery and a small request using the same key your
application will use.

See [route readiness](/operators/route-readiness) for blockers and
[earnings](/operators/earnings) for the separate revenue lifecycle.