Bifrost
Point a Custom provider at Bifrost for downstream model routing and identity-aware access control
Bifrost is an OpenAI-compatible LLM gateway that routes to many upstream model providers. Use it as a Custom AI Gateway provider when Pangolin should authenticate clients and Bifrost should pick models, fail over, or apply its own access controls.
Pangolin talks to Bifrost at /v1/chat/completions (default port 8080). Add Anthropic Messages as well if clients will call Bifrost's Anthropic-compatible paths.
See Capabilities for the full capability list.
Install a site on the same network as Bifrost so Pangolin can reach it over the tunnel. See Reach a Self-Hosted API.
Configure
- Sidebar → AI Gateway → Providers → Create.
- Set Provider Type to Custom and give it a name.
- Select OpenAI Chat Completions (and any other formats Bifrost should accept).
- Set Routing Mode to Site Targets if Bifrost runs on a site's network. Use Upstream URL (
http://<host>:8080) only when the Pangolin node can reach Bifrost directly. - Set Auth Type to No Auth on a private LAN. Use Bearer if Bifrost requires a virtual key or other API key.
- Allow the model ids Bifrost should serve, including provider-prefixed keys such as
openai/gpt-4o-miniif that is how Bifrost names them. See Model Routing. - Save. On the Network tab, add a target: the Bifrost host, port
8080, method HTTP. - Attach the provider to an AI Gateway resource.
Then point a client at that resource: Codex, OpenCode, or Open WebUI. Clients still call the Pangolin resource. Bifrost only sees the request after Pangolin has authenticated it.
When the caller is a known user, Pangolin forwards Remote-User, Remote-Email, Remote-Name, and Remote-Role. Use those in Bifrost (or any Custom upstream) for downstream access control. An unattributed manual key authenticates without sending them.
Was this page helpful?

