DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to pool team AI subscriptions behind one employee endpoint with Subpool

Self-host a control plane that gives each employee a key across shared provider accounts.

Account pooling. Sharing subscription capacity across employees can breach a provider's terms, so connect only accounts you are authorized to manage.

Who it is forAn IT or platform administrator whose team holds several AI subscription or API accounts and needs to hand out access without sharing one login.

The problemSeparate subscriptions are hard to track, and employees each need access to capacity they can use without owning the upstream account.

The outcomeA running Subpool instance where accounts are grouped into a pool and each employee has a dedicated API key for that pool.

What you need first

  • Docker Engine and Docker Compose installed
  • openssl available to generate secrets
  • AI subscription or API accounts that you are authorized to manage
  • Administrator credentials for a running Subpool console (set in .env)

Steps

  1. Run cp .env.example .env, then replace every replace-with-* value using openssl rand -base64 32 and openssl rand -hex 32.
  2. Run docker compose up -d to start Subpool from the published image.
  3. Open http://localhost:8081 and sign in with the administrator credentials from .env.
  4. In Accounts, connect a Codex, GitHub Copilot, Google Antigravity, or OpenAI-compatible account.
  5. Create a pool, add the connected account to it, then create an employee API key for the pool.

Prompt for your agent

Using the gesta-run/subpool repository, set up a local Subpool instance by following its quick start, then report the console URL and the API URL. Expected output: both URLs responding, with the console reachable at http://localhost:8081. Verify that `docker compose ps` shows the Subpool service running before reporting success.

Caveat. Subpool stores no prompts, responses, or source code, but you must back up PostgreSQL together with SUBPOOL_CREDENTIAL_KEY and SUBPOOL_API_KEY_HMAC_KEY or encrypted credentials cannot be recovered.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for gesta-run/subpool and "Pool team AI subscriptions behind one employee endpoint"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer