Onboarding¶

Brama gives Wisent services one authenticated gateway for provider-neutral LLM inference without distributing provider credentials to callers. Onboarding is the journey from an empty machine to one alias that answers a real request: pick the path that matches what you are building, carry over any configuration you already have, reach a routed model response, and know the repair for each refusal you can hit on the way.

The journey is finished when the gateway returns a real routed model response. Installing the binary, provisioning trust, and importing a registry document are steps toward that fact, not the fact itself.

What you are configuring¶

Onboarding configures aliases. An alias resolves to exactly one route, and its readiness is one of serving, no_route, capability_absent or routes_file_invalid. When the route refuses, that refusal is what the caller receives, so each alias is worth setting up with its capability in place before the first billable call. Read the current picture at any point with brama aliases, which prints alias, state and route.

The four pages¶

Paths and prerequisites¶

The three paths — safe local detection, authenticated loopback gateway, production host service — what each one requires, and how an installation selects an immutable published release rather than development source.

Bring existing configuration¶

The adoption review: how brama adopt reports each alias with its single source route and its current destination, how a differing route is treated as a conflict, what happens to deployments no alias references, and how brama routes migrate moves an older registry file to the current document shape.

First success¶

Safe local detection end to end, what a zero-state installation does, the provisioned loopback gateway and its first non-billable call, the production host service, and the machine interfaces automation may depend on.

Failures and reset¶

Credential separation, the alias states and the exact repair for each, the startup and HTTP failures onboarding actually hits, and how to uninstall or reset without deleting something an authority still owns.

Suggested order¶

1. Read paths and prerequisites and confirm the prerequisites for your path.
2. Run safe local detection from first success. It costs nothing and touches no provider.
3. If a Brama installation already exists, review it with bring existing configuration before configuring anything by hand.
4. Provision and start the gateway, confirm every intended alias reads serving, then make the first call.
5. Keep failures and reset open: it names the repair for each refusal.

Adjacent references: Quick start for the shortest working path, Configuration for the registry document and environment, HTTP API for the alias and admin endpoints, CLI for every command, and Errors for the full status and code list.