Architecture

One control layer.
Every model call.

Kyberos sits between application workflows and model providers, creating a consistent layer for telemetry, governance and routing without coupling your product to a single vendor.

System map

Follow a request through Kyberos.

Explore the model traffic, the metadata it produces and the controls around it.

REQUEST PATHGateway foundation
01 / Client

Your application

AI feature · service · agent

OpenAI-compatible clientAuthenticates with a Kyberos key
requestresponse
02 / Gateway

Kyberos

Authenticate · limit · forward

Key checkHeader allowlistStreaming
Content passes through memory
forwardstream
03 / Provider

Your model provider

Model inference

ClaudeGeminiGPT
Separate provider credentialMulti-provider target · provider data policies apply
From gateway · metadata hook
ObservabilityPipeline planned

Telemetry & analytics

Operational metadata, without prompt or response bodies.

  1. Async events
  2. Enrich & store
  3. Metrics & alerts
Designed to stay outside the response path
To gateway · project configuration
Control planePlanned

Identity, secrets & policies

Project boundaries and rules managed separately from model traffic.

PostgreSQLProjects · key hashes · policiesSecret managerProvider credentials
Budgets · model allowlists · audit history
Gateway foundation Planned supporting services

Model names illustrate the target ecosystem. The initial gateway connects to OpenAI; other provider adapters are planned.

One request path. Two supporting layers.

Model traffic passes through the gateway. A separate telemetry branch observes it; the planned control plane supplies project configuration and policies.

Overview

The initial gateway sits on the request path between your application and OpenAI. It authenticates application requests, forwards them with a separate provider credential and streams the response back. A metadata hook provides the starting point for the planned telemetry pipeline; project policies and analytics are supporting services, not extra steps through which a response must travel.

Gateway first

The gateway is designed as the default entry point for new projects. Applications keep the familiar provider API shape while Kyberos applies authentication, tracing, budget controls and routing before forwarding the request.

Normalized event model

Every provider response is converted into a common event format so usage can be compared across vendors and model families.

{
  "project": "support-agent",
  "workflow": "refund-resolution",
  "model": "gpt-5.6",
  "provider": "openai",
  "prompt_tokens": 1280,
  "completion_tokens": 420,
  "latency_ms": 2840,
  "cost_usd": 0.0182,
  "status": "success",
  "cache_hit": false
}

Storage and analytics

PostgreSQL / TimescaleDB is a pragmatic starting point for product metadata, traces and time-series metrics. High-volume analytical workloads can later move into ClickHouse without changing the public gateway contract.

Security and privacy

The gateway foundation separates application and provider credentials and keeps prompt and response content out of persistent telemetry. Requests still reach the configured model provider. Project isolation, secret-manager integration and retention controls are planned next steps.

Explore security & data protection →