Self-Hosted Codex Gateway

Codex Pooler is a self-hosted Codex gateway for operators who need shared Codex account capacity behind stable Pool API keys. It runs under your own Docker Compose or Kubernetes deployment, routes supported Codex backend traffic through Pool policy, and keeps request evidence metadata-only.

When To Use Codex Pooler As A Self-Hosted Gateway

Use Codex Pooler when you already operate trusted Codex accounts and want one controlled gateway between clients and account capacity. It is not a hosted provider and it is not a general OpenAI API clone.

Need	Codex Pooler fit	Canonical docs
Run the gateway yourself	Docker Compose for local or small installs, Helm for Kubernetes deployments	Quick Start and Helm deployment
Give clients one stable credential	Pool API keys represent a Pool, not one upstream account	Pools and API keys
Support Codex backend clients	Use the Codex backend compatibility route rooted at /backend-api/codex	Codex CLI and Runtime Routes
Keep operations evidence safe	Request logs, audit logs, and MCP tools expose metadata, not raw prompts, bodies, or credentials	Request logs and Admin UI

Public Route Shape

For local setup, use http://localhost:4000. For deployed examples, use https://codex-pooler.example.com.

Codex backend clients: http://localhost:4000/backend-api/codex
Selected SDK clients:  http://localhost:4000/v1
Operator MCP hosts:    http://localhost:4000/mcp

Runtime work on /backend-api and /v1 uses Pool API keys. Operator MCP uses operator-owned MCP bearer tokens and stays separate from runtime credentials.

Related Discovery Pages

• AI coding agent gateway
• Codex account pooling
• OpenAI-compatible Codex gateway
• Codex Pooler vs direct credentials

Backed By Existing Docs

• Quick Start shows the local Docker Compose first-run flow
• Runtime Routes lists the public route families and support boundaries
• Routing Strategies explains Pool API key admission, eligibility, and upstream account selection