Unnamed project
A work-in-progress tool providing a thin OIDC authentication layer for self-hosted LLM engines, implemented as a relay: users log in with their organization's identity provider, generate an API key for themselves, and point their harnesses at the relay instance. Written in Erlang and deliberately minimal — no web chat interface and no feature gating.
What it addresses
Self-hosted LLM engines lack a built-in, organization-level auth layer (OIDC/SSO with per-user API keys) for API access.
Shared over time
Each entry reflects what was shared on that date. Details and invitations may have changed since then.
Unnamed project
A work-in-progress tool providing a thin OIDC authentication layer for self-hosted LLM engines, implemented as a relay: users log in with their organization's identity provider, generate an API key for themselves, and point their harnesses at the relay instance. Written in Erlang and deliberately minimal — no web chat interface and no feature gating.
Problem: Self-hosted LLM engines lack a built-in, organization-level auth layer (OIDC/SSO with per-user API keys) for API access.
Audience: People and teams who run self-hosted LLM engines and want organization-level authentication for API access — 'people who want to get shit done'.
Posted by @cmdrk · Builder identity supported: @cmdrk · Original comment ↗