Opportunities › Self-hosted API gateway for LLM CLIs › Proposed app
Tollgate Keys
Self-hosted key vault and spend caps for your team's coding CLIs
- Score
- 75
- confidence 59
- Evidence
- 12
- items on the page
- Rivals
- 6
- named in sources
- First version
- 25 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2023
- Emerging market · AI estimate
ScreensConcept
Desktop app: Developers manage API keys, set budgets, and review detailed spend analytics by developer and repository—back-office work that happens at a desk with dense dashboards and configuration. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Usage
Budget 64% used$1,284
About this appAI proposal
Tollgate Keys is a small gateway you run on your own server. Developers point Claude Code, Codex CLI or Gemini CLI at it and use a personal virtual key. Your real provider keys stay on your machine, and requests pass straight through to the provider.
A web console shows who used which model, how many tokens, and the estimated spend. Set a monthly cap per person or team and the gateway stops requests at the limit. Logs record metadata only by default; prompt capture is a per-team switch, so source code is not stored unless you choose it.
It is built for teams of about 5 to 30 developers who find a full LLM gateway stack too heavy. One container, an embedded database, and copy-paste setup for each CLI.
- Tagline
- Your keys stay home. Your spend stays visible.
- Voice
- PlainPracticalCalmPrecise
- Why this name
- A tollgate is where traffic passes, is counted and is limited. Keys points to the credentials the product guards.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Pass-through endpoints
Accepts OpenAI, Anthropic Messages and Gemini request formats, with streaming, and forwards them to the matching provider unchanged.
No member yet
Virtual keys per developer
Each person gets their own key. Real provider keys are stored only on your server and are never handed to the CLI.
No member yet
Metadata-only request log
Records user, model, tokens, latency and status. Prompt bodies are stored only if you turn capture on for a team.
No member yet
Spend estimates
Costs are computed from a price table you edit, so you can match your own contract rates when providers change prices.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F4C4ADeep Teal · primary#F6F3ECPaper · surface#1B2422Ink · text#E0912BToll Amber · accent#B8402FSignal Red · alert, cap reached#8FB3A5Sage · data
Typography
Aa
Tollgate Keys
PricingAI proposal
The material gives no competitor price except LiteLLM: open source self-hosted at $0, enterprise priced annually by request capacity. These tiers are a starting point to test, flat by team size rather than by volume.
Community
Free
- Up to 5 users
- Virtual keys and request log
- Budget caps and rate limits
- Docker install
Team
$49 a month
- Up to 30 users
- Spend by repository
- CSV export
- Email support
Business
$149 a month
- Up to 100 users
- Multiple tenants
- Longer log retention
- Priority support
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$190,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. The gateway runs on the customer's own server and is used only by their developers. Nothing it produces is sent to outsiders, so growth comes from content, open-source presence and direct outreach.
- Do they become customers?
- Test whether engineering leads who find it through setup guides and repo listings convert from the free tier to Team when they hit the 5-user limit.
- First customers
- Engineering leads at 5 to 30 developer companies where staff already use Claude Code, Codex CLI or Gemini CLI on shared company API keys.
- Where to reach them
- GitHub and open-source lists: Publish the free Community edition with setup guides for each CLI and answer issues on related gateway repositories.
- Developer communities: Post cost-control write-ups in Hacker News, Reddit and CLI-specific Discords, with a real spend dashboard example.
- Direct outreach: Message engineering managers at small startups about shared-key sprawl and offer a free setup call.
- First milestone
- Ten teams running it for 30 days and five of them paying for Team.
Why people already pay for this
- VerifiedGitHub repository gained 1033 stars in 226 days
- Public claimTeams use multiple LLM providers and coding CLIs and need centralized management
- Public claimExisting market for self-hosted API gateways and LLM proxies
- Public claimCost control and usage monitoring are key needs
- Verified
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Gateway serviceStreaming HTTP proxy in a single containerLong-lived streamed responses and low overhead are awkward on serverless hosting, so the gateway runs on the customer's server.
- This app · Embedded databaseSQLite with optional PostgresLets small teams run one container with no external database.
RisksAI inference
- PlatformProviders and CLIs may change endpoints, auth flows or streaming formats, breaking pass-through. Subscription-login CLIs may not work through a key-based gateway.
- CommercialFree open-source gateways such as LiteLLM and CLIProxyAPI already exist. Buyers may not pay for a lighter, CLI-focused option.
- TechnicalToken counts and costs for streamed responses can be inexact, so spend is only an estimate and caps may trip late.
- DataThe gateway holds all provider keys and may log sensitive traffic. A bug or breach would expose the whole team's credentials.
- CommercialSelf-hosted licensing is hard to enforce and support load per customer can be high for a small team.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.