Oolyx
The oolyx-dashboard container runs the admin and analytics UI on port :8788. It provides complete visibility into LLM cost, governance controls, workspace management, and savings reporting — all self-hosted on your infrastructure.
Four core areas, all accessible from a single self-hosted UI. Nothing leaves your network to render any of this.
Unified view of all LLM spend across every source in a single dashboard — updated in real time.
Multi-tenant workspace views — each team or project gets its own isolated cost and governance scope, centrally managed.
Two-tier quota hierarchy — global admin sets org-wide budgets, workspace admins override with local limits.
Model benchmarking and monthly savings reports — quantify every dollar saved by Oolyx's optimizations.
Configure data protection behavior per workspace — redact, mask, or delete at three independent scrubbing layers.
See exactly what Oolyx is doing under the hood and how much each strategy is saving you.
The dashboard container is part of the standard docker-compose stack. No separate installation required.
Both ports are internal to your corporate network. Neither requires internet exposure. Clients point to http://oolyx:8787/v1 — the dashboard is accessed directly in the browser at http://oolyx:8788.
| postgres-data | Audit logs, request history, config, savings data |
| redis-data | Semantic cache, rate-limit counters, session state |
| oolyx-config | Workspace settings, tagging schemas, quota rules |
| DATABASE_URL | PostgreSQL connection string |
| REDIS_URL | Redis connection string |
| OOLYX_ADMIN_KEY | Global admin authentication key |
| OOLYX_PROXY_URL | Internal URL the dashboard uses to talk to the proxy |
| PORT | Dashboard UI port (default: 8788) |
Three roles control what users can see and do within the dashboard. Roles are scoped per workspace — a user can be admin in one workspace and observer in another.
The dashboard's audit trail, PII controls, and quota enforcement are designed to satisfy the AI governance requirements of financial services, healthcare, and banking regulators.
The dashboard container reads from PostgreSQL and Redis — it never sits in the hot path of LLM requests. Proxy performance is unaffected by dashboard activity.
All client sources — apps, IDEs, agents, and chat users — flow through the central Oolyx proxy layer before reaching any LLM provider. Nothing bypasses governance.
Orchestrator agents, sub-agents, and MCP servers all route through Oolyx. Every call gets tagged, quota-checked, PII-scrubbed, and cached before reaching the LLM — preventing runaway agent loops from burning budget.
The full Oolyx stack runs as four Docker containers on a single host inside your corporate network. Outbound traffic is HTTPS-only to LLM providers — no telemetry, no external dependencies for the control plane.
Oolyx