This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Codex Pooler
One gateway for many Codex accounts
Codex Pooler is a self-hosted gateway for sharing Codex account capacity across agents, tools, and teams. Add accounts to pools, issue stable API keys, and route Codex backend or OpenAI-compatible requests by model support, limits, health, and session continuity. Operators get accounting, audit logs, MCP access, and privacy-minded metadata-only observability.
Codex Pooler is a self-hosted gateway for expert teams that need to share and operate Codex account capacity as infrastructure.
Instead of binding every agent, CLI, or internal tool to one account, you add Codex accounts to Pools, issue stable Pool API keys, and let the gateway route work by model support, limits, health, policy, and session continuity.
What pooling gives you:
- one stable key representing many Codex accounts
- central capacity changes without reconfiguring every client
- fewer blocked workflows when one account is exhausted or unhealthy
- long-running sessions and reconnects staying on the right upstream
- clearer visibility into which account handled a request, and why
Works with multiple harnesses:
- Codex CLI
- OpenCode
- editor agents
- internal automations
- custom agent workflows
Operator layer:
- alerts and incidents
- stats, request history, routing views, and audits
- Prometheus metrics and a Grafana dashboards
- advanced tuning for limits, diagnostics, circuits, ingress, model metadata, and timeouts
Deployment:
- self-hosted
- Docker Compose for trying it
- Helm for Kubernetes with separate app, worker, scheduler, and migration roles
The goal is simple: pool Codex capacity, keep sessions reliable, and give teams enough control to run Codex-powered work seriously.
I'd love feedback from teams already juggling multiple Codex accounts. Where would pooling help first, and what controls would you need before trusting it?
About Codex Pooler on Product Hunt
“One gateway for many Codex accounts”
Codex Pooler was submitted on Product Hunt and earned 4 upvotes and 1 comments, placing #63 on the daily leaderboard. Codex Pooler is a self-hosted gateway for sharing Codex account capacity across agents, tools, and teams. Add accounts to pools, issue stable API keys, and route Codex backend or OpenAI-compatible requests by model support, limits, health, and session continuity. Operators get accounting, audit logs, MCP access, and privacy-minded metadata-only observability.
On the analytics side, Codex Pooler competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Codex Pooler performed against the three products that launched closest to it on the same day.
Who hunted Codex Pooler?
Codex Pooler was hunted by Claudio Poli ✪. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Codex Pooler including community comment highlights and product details, visit the product overview.
Claudio Poli ✪
Hey Product Hunt,
Codex Pooler is a self-hosted gateway for expert teams that need to share and operate Codex account capacity as infrastructure.
Instead of binding every agent, CLI, or internal tool to one account, you add Codex accounts to Pools, issue stable Pool API keys, and let the gateway route work by model support, limits, health, policy, and session continuity.
What pooling gives you:
- one stable key representing many Codex accounts
- central capacity changes without reconfiguring every client
- fewer blocked workflows when one account is exhausted or unhealthy
- long-running sessions and reconnects staying on the right upstream
- clearer visibility into which account handled a request, and why
Works with multiple harnesses:
- Codex CLI
- OpenCode
- editor agents
- internal automations
- custom agent workflows
Operator layer:
- alerts and incidents
- stats, request history, routing views, and audits
- Prometheus metrics and a Grafana dashboards
- advanced tuning for limits, diagnostics, circuits, ingress, model metadata, and timeouts
Deployment:
- self-hosted
- Docker Compose for trying it
- Helm for Kubernetes with separate app, worker, scheduler, and migration roles
The goal is simple: pool Codex capacity, keep sessions reliable, and give teams enough control to run Codex-powered work seriously.
Docs: https://docs.codex-pooler.com
Code: https://github.com/icoretech/codex-pooler
I'd love feedback from teams already juggling multiple Codex accounts. Where would pooling help first, and what controls would you need before trusting it?