AI Infra Portal

Your AI gateway, one control plane.

  • Create Kong consumers and API keys in one click
  • Map LiteLLM virtual keys into gateway requests
  • Read Langfuse traces from the same portal

AI Infra Portal

Sign in to AI Infra Portal

Portal admin account. Clients never sign in here.

AI Infra Portal

Gateway Control Plane

Overview
Registry
Observability
Configuration
Services
A
Signed in

AI Infra Portal

Checking

Infra Dashboard

Your AI gateway control plane — Kong, LiteLLM and Langfuse at a glance

Applications

—

registered apps

Registered Models

—

LiteLLM deployments

LiteLLM Keys

—

Kong consumers

Traces (today)

—

Langfuse

Kong Gateway

—

…

LiteLLM Proxy

—

…

Langfuse

—

…

Gateway requests

Traced requests per day · last 14 days

Langfuse

Recent activity

Register a new appKong key + LiteLLM mapping
Add a modelRegister a LiteLLM backend
Connection statusKong, LiteLLM, and Langfuse

App Registry

Register an app to get a Kong consumer, API key, request-transformer plugin, and a LiteLLM virtual key mapped onto the request.

No apps yet

Create an app, or import Kong consumers that already map to a LiteLLM key.

Live gateway inventory

Kong consumers and LiteLLM teams this portal can see

Kong

ConsumerKeyBearerPII

LiteLLM

TeamKeysPII

Inference Registry

Models served by LiteLLM — self-hosted, OpenAI, Anthropic, SiliconFlow, or custom. Config-backed models stay read-only.

ModelProviderlitellm modelUsed by

litellm config.yaml

Preview from the live model list

model_list: []

Langfuse Traces

Requests observed by Langfuse for this gateway. Open a row to see the timeline.

…
TraceAppModelLatencyTokensCostStatusTime

Connection Settings

This portal calls Kong, LiteLLM, and Langfuse directly. Endpoints come from the portal environment — one process, no extra service to deploy.

How the pieces fit together

App Registry creates a Kong consumer and key-auth credential, then attaches a request-transformer so the gateway swaps the client apikey for a LiteLLM virtual key.

Inference Registry registers model backends into LiteLLM. Clients only ever receive the Kong apikey.

Traces reads Langfuse so you can follow a call: which model, latency, tokens, and whether it failed.

Register a new app

Creates the Kong consumer, API key, request-transformer, and LiteLLM team/key.

Link existing Kong or LiteLLM instead of creating new


        
      

App

Kong Gateway


      

LiteLLM

Clients receive only the Kong apikey. The LiteLLM virtual key stays on the platform and is injected by Kong.

Audit

    Edit app

    Register a model

    These entries are written into LiteLLM with /model/new.

    Trace

    Timeline

    Confirm