How labiium/routiium works
Routiium is a self-hosted OpenAI-compatible LLM gateway, with a browser-based admin panel. The main runtime path accepts a client request, applies access controls and limits, prepares and judges it, selects a model route, and proxies to an upstream; the gateway also supports chat history, analytics, MCP tools, Bedrock, and subscription proxying. The admin panel exposes management views through the gateway API. Some links are based on README descriptions or the source index; unsampled implementation details are not inferred as direct calls.
Main entry points: server.rs HTTP gateway · router_client.rs Model router · pages Admin views · adminApi.ts Admin API client
Components 24
Gateway runtime
- HTTP gateway
src/server.rs - API key auth
src/auth.rs - Rate limits
src/rate_limit.rs - API models
src/models/chat.rs - API conversion
src/conversion.rs
Routing and safety
- Safety judge
src/safety_judge.rs - Typed decisions
src/decision.rs - Model router
src/router_client.rs - Jev adapter
src/jev.rs
Gateway capabilities
- Bedrock support
src/bedrock.rs - MCP tools
src/mcp_client.rs - MCP configuration
src/mcp_config.rs - Chat history
src/chat_history.rs - History manager
src/chat_history_manager.rs - Analytics
src/analytics.rs - Analytics middleware
src/analytics_middleware.rs - Subscription proxy
src/subscription_proxy.rs
Administration
- Admin panel
apps/admin/src/App.tsx - Admin views
apps/admin/src/pages - Panel state hook
apps/admin/src/hooks/useAdminPanelState.ts - Admin API client
apps/admin/src/lib/adminApi.ts
Other components
- OpenAI client
- Model providers
- Admin
Connections 26
- OpenAI client → HTTP gateway: sends request
- HTTP gateway → API key auth: checks credentials
src/server.rs - HTTP gateway → Rate limits: applies limits
src/server.rs - HTTP gateway → API models: parses request
src/server.rs - HTTP gateway → API conversion: converts API
src/server.rs - HTTP gateway → Safety judge: judges request
src/server.rs - HTTP gateway → Model router: selects route
src/server.rs - Model router → Typed decisions: requests decision
src/router_client.rs - Jev adapter → Typed decisions: implements provider
src/jev.rs - Model router → Model providers: resolves model
- HTTP gateway → Model providers: proxies request
- HTTP gateway → Bedrock support: supports Bedrock
src/server.rs - HTTP gateway → MCP tools: uses tools
src/server.rs - MCP tools → MCP configuration: loads settings
src/mcp_client.rs - HTTP gateway → Chat history: records conversations
src/server.rs - History manager → Chat history: uses store types
src/chat_history_manager.rs - HTTP gateway → History manager: manages history
src/server.rs - HTTP gateway → Analytics middleware: records requests
src/server.rs - Analytics middleware → Analytics: updates analytics
src/analytics_middleware.rs - OpenAI client → Subscription proxy: uses proxy
- Admin → Admin panel: uses panel
apps/admin/src/App.tsx - Admin panel → Admin views: routes views
apps/admin/src/App.tsx - Admin views → Panel state hook: loads panel state
apps/admin/src/pages/Routing.tsx - Panel state hook → Admin API client: fetches state
apps/admin/src/hooks/useAdminPanelState.ts - Admin views → Admin API client: sends updates
apps/admin/src/pages/Routing.tsx - Admin API client → HTTP gateway: calls admin API