Opportunities › Local gateway for AI coding clients › Proposed app
Tallyport
One local gateway for your AI coding clients: costs, keys and risky calls
- Score
- 59
- confidence 35
- Evidence
- 7
- items on the page
- Rivals
- 2
- named in sources
- First version
- 40 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2025
- New market · AI estimate
ScreensConcept
Desktop app: Developers monitor spend and traces across clients, switch providers, and review risky tool calls in a dedicated dev environment at their machine. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Today
Within budget$18.40
About this appAI proposal
Tallyport runs on your machine and sits between your AI coding clients and the API providers they call. Point Claude Code, Codex or another client at it once. From then on you switch providers, see what each session costs, and decide what may leave your laptop.
API keys stay local. Tallyport holds the real keys, gives clients a stand-in, and redacts secrets found in outgoing requests. Tool calls that look dangerous can be held for approval or blocked before they run. Every request is traced so you can audit it later.
A web dashboard, installable as a PWA, shows spend and usage across clients and, for teams, shared rules and audit logs. The gateway does the work on each developer's machine, so the clients need no changes.
- Tagline
- Your AI clients, one gate you control.
- Voice
- PlainCalmPrecise
- Why this name
- A tally counts what was spent and a port is where traffic passes. Together they say: every call goes through one counted point on your machine.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Switch providers in one place
Change which provider serves Claude Code, Codex or another client from one setting. No edits inside each tool.
No member yet
Spend across every client
Tokens and cost per client, project, model and day in one view, so a runaway session shows up the same day.
No member yet
Keys stay on the machine
Real keys sit in a local vault. Clients get stand-ins, and secrets found in outgoing prompts are redacted.
No member yet
Hold or block risky tool calls
Write rules for shell commands, file paths and network targets. Matches are blocked or wait for your approval.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F5C4DHarbor Green · primary#F6F3EAPaper · surface#1E2A28Ink · text#E27A2FSignal Orange · accent#2F6DB5Tide Blue · data#B3362BStop Red · blocked state
Typography
Aa
Tallyport
PricingAI proposal
The material gives no competitor prices. The tiers follow the freemium idea in the opportunity and are a starting point to test, not a market-based figure.
Free
Free
- Local gateway for any client
- Provider switching
- Cost and usage tracking
- 7 days of request history
Pro
$12 a month
- Tool-call rules and approvals
- Budget caps and fallback
- Unlimited trace history and export
- Secret redaction rules
Team
$24 a month
- Per developer, 3 seat minimum
- Shared policies
- Team audit log
- Spend by person and project
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
$194,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
- Users invite others. A team lead sets shared policies and budgets, then invites teammates, who install the gateway to apply them. Each added developer brings spend and rules into the shared dashboard.
- Do they become customers?
- Invited teammates can become paying seats, but many will use only the free tier. Test how many invited developers install it and whether leads pay for shared policies and audit logs.
- First customers
- Engineering leads at small software teams (5 to 30 developers) where several people already use more than one AI coding client and want to cap and review spend.
- Where to reach them
- GitHub project communities: Join discussions on related open-source gateway projects and answer cost and key-safety questions with a free tool.
- Developer forums and newsletters: Post a write-up of cost and tool-call findings from real sessions, with a link to install.
- Direct outreach to team leads: Offer a free two-week team pilot with shared budgets and an audit log.
- First milestone
- Five small teams each pay for Team seats after a pilot, with at least 70% of invited developers keeping the gateway installed after two weeks.
Why people already pay for this
- VerifiedGitHub repository gained 1000 stars in 29 days
- Public claimThe project describes itself as a local gateway that allows switching between AI coding clients and providers without modifying clients themselves
- Public claimThe gateway protects API keys by intercepting and redacting them before they reach external services
- Public claimThe tool enables developers to block malicious or unsafe API calls before they execute
- Public claim
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 · Local gateway agentSmall cross-platform background app (macOS, Windows, Linux)Requests must be intercepted on the developer's machine; a PWA cannot run a local proxy.
- This app · Local secret storageOS keychain integrationReal API keys must stay on the machine, not in Supabase.
RisksAI inference
- TechnicalClients differ in how they accept a custom endpoint and how they stream responses and tool calls. Each client needs testing, and updates can break routing.
- CommercialAn open-source project with 1,000 stars in 29 days already does similar things for free. Paid value must come from team features, not the local proxy.
- PlatformProviders or clients may change terms or add built-in cost and key controls, which would shrink the need for a gateway.
- AIRules to detect dangerous tool calls will miss some and flag harmless ones. Overclaiming protection could mislead users.
- DataThe gateway sees prompts and code. Trust depends on keeping content local and syncing only metadata, which must be proven.
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.