OIDC auth relay for self-hosted LLM engines
A thin OIDC authentication relay for self-hosted LLM engines. Users log in with their organization's identity provider, generate a personal API key, and point their harnesses at the relay instance. Implemented as a tight Erlang program with no web chat interface or pricing-gated features.
What it addresses
Self-hosted LLM engines lack a simple OIDC-based auth layer for teams, with existing options adding gates like web chats and call-us-for-pricing feature gating.
Shared over time
Each entry reflects what was shared on that date. Details may have changed since then.
OIDC auth relay for self-hosted LLM engines
A thin OIDC authentication relay for self-hosted LLM engines. Users log in with their organization's identity provider, generate a personal API key, and point their harnesses at the relay instance. Implemented as a tight Erlang program with no web chat interface or pricing-gated features.
Problem: Self-hosted LLM engines lack a simple OIDC-based auth layer for teams, with existing options adding gates like web chats and call-us-for-pricing feature gating.
Audience: Self-hosters running LLM engines and developers who point their tooling/harnesses at the relay
Posted by @cmdrk · Original comment ↗
“Working on a tool to provide a thin OIDC auth layer for self-hosted LLM engines. Users log in with your Org's identity provider, generate an API key for themselves, point their harnesses at your instance of the relay, and then they're off to the races.”