
Deploy Codex Pooler
Self-hosted Codex gateway with pooled accounts and OpenAI-compatible APIs.
Just deployed
/var/lib/postgresql/data
codex-pooler
Just deployed
Deploy and Host Codex Pooler with Railway
Codex Pooler is a self-hosted gateway for pooling Codex accounts and exposing OpenAI-compatible APIs. This Railway template provisions the application together with a persistent PostgreSQL database, generated encryption secrets, public HTTPS networking, health checks, database migrations, and the bundled OpenAI pricing snapshot.
About Hosting Codex Pooler
Hosting Codex Pooler gives teams and automated agents a central service for managing upstream Codex identities, organizing them into pools, and routing compatible API traffic. The template uses the project's official container image and a private Railway connection to PostgreSQL. On every deployment, the application applies its idempotent database migrations and imports the bundled pricing data before starting the web server. Railway supplies the public domain, persistent database volume, generated application secrets, service health monitoring, and automatic restart behavior. After deployment, visit the generated application URL and complete the owner bootstrap flow.
Common Use Cases
- Share managed Codex capacity across a team or collection of agents.
- Provide an OpenAI-compatible gateway for existing tools and SDKs.
- Centralize upstream identity, pool, quota, and routing administration.
- Run a private Codex gateway without maintaining servers manually.
- Evaluate Codex Pooler in an isolated, reproducible environment.
Dependencies for Codex Pooler Hosting
- Codex Pooler's official container image from GitHub Container Registry
- PostgreSQL 18 with persistent Railway storage
- Railway private networking between the application and database
- Railway public HTTPS networking for the web interface and APIs
- Generated Phoenix and credential-encryption secrets
Deployment Dependencies
Implementation Details
The application listens on port 4000 and uses /metrics as its Railway health-check path. The startup command runs the release migrations and pricing import with the Phoenix server disabled, then starts the normal release process. PostgreSQL data is stored on a persistent volume and is reached through Railway's private network.
Why Deploy Codex Pooler on Railway?
Railway hosts the application, PostgreSQL database, private service network, public HTTPS endpoint, persistent storage, generated secrets, health checks, and deployment lifecycle in one project. This reduces the operational work required to run Codex Pooler while preserving access to logs, metrics, scaling controls, and the underlying service configuration.
Template Content
