The most expensive thing
you ship is your free tier.
Your users bring their own Claude or ChatGPT plan, and your app runs on their subscription instead of your API key.. Your app runs on it, not your key.
How it works
Your users already pay for AI.
Let them use it in your app.
Connect your AI
Use access you already have.
Nothing here is charged to you.
Your own API key
Stays on this machine. Your app never receives it.
Approve it on this machine
This page finishes on its own.
Needs Claude Code installed and signed in
Open it againYour browser asks permission the first time.
Your app wants to use the AI on this Mac
Your accounts stay on this Mac. Your app never sees them.
Inference you didn’t pay for
$7,21871% on their plans29% on your key
| Started | User | Model | Ran on | Cost |
|---|---|---|---|---|
| 11:04 | ana@northwind.io | claude-opus-4 | Their Claude Max | $0.00 |
| 11:04 | tom@arclight.dev | gpt-5 | Their ChatGPT Plus | $0.00 |
| 11:03 | priya@kestrel.app | claude-sonnet-4 | Your key | $0.012 |
| 11:03 | leo@fieldnote.co | llama-3.3 | Their Ollama | $0.00 |
| 11:02 | mia@northwind.io | claude-opus-4 | Their Claude Max | $0.00 |
| 11:02 | sam@arclight.dev | gpt-5 | Your key | $0.011 |
| 11:01 | zoe@kestrel.app | gpt-5 | Their ChatGPT Pro | $0.00 |
| 3,041 runs this month | $0.023 |
Users connect Claude or ChatGPT One click. Their machine pairs from the browser.
Runs use their plan, not your key Their AI if they have one, your key if not.
See how much you saved Plans, limits and every run, in one dashboard.
Where a run lands
It runs on a machine they already own
Their Mac, Windows or Linux machine, paired through the Soba app. Your app sends the run there and the answer streams back.
Your app
Summarise everything I saved this week
Ask ▶
Desktop only. macOS, Windows or Linux, and only while that machine is awake and paired.
Back in your UI
Tokens arrive the same way on every surface you ship.
Plans
You decide what your users run on,
and what they pay you.
Each plan sets both. Your users subscribe to you, and the money arrives in your own Stripe account.
What a run on this plan may reach
- 01
Their Claude or ChatGPTTheirs, already paid
- 02
A model on their machineFree. They own the hardware
- 03
Their own API keyBilled to them, not to you
- 04
Your API creditsYou pay, at wholesale rates
What your users pay you
Plan
Your plan
$your pricea month
- Runs included, or unmetered
- Then a price a run, or a wall
- A free trial, if you want one
- Runs on their own AI, free or counted
One of as many plans as you like
A run tries those four in that order and stops at the first one that answers, so a user who brought their own Claude never reaches the one you pay for. Both halves are one stored object, which is why changing a price, an allowance or what a plan may reach is not a deploy, and Soba takes no percentage of what your users pay you.
How plans workEverything between the
model call and the invoice.
Pairing, routing, metering and billing, so your team only builds the feature.
Read the docsYou pick the order. Each run goes to the first AI the user has, and your key only if nothing else is there.
$0.04 a run after that
Free on a plan they connect
Per run, per message, per token or per seat. Allowances, trials and codes.
Set your plans. Payments go straight to your Stripe.
Who ran it, where it ran, and what it cost you.
Turn free users
into paying ones.
You set the plan your users are on: what the free tier runs on, how long it lasts, and what the paid one costs. Soba holds them to it and bills at your price.
Your free users run on
for or
Then they see an upgrade prompt
And pay you for
Their account.
Their machine. Their say.
Each run stays on a machine dedicated to one user, signed in with that user’s own account.
Users say yes on their own machine, with no key to paste. They can take it back any time.
Your prompts, tools and data stay in your app. Soba handles the model call, the limits and the bill.
Add it in an afternoon.
Drop-in screens for connecting, plans and checkout, styled with your own CSS. Or run npx skills add soba.so/skill and let the coding agent you already have open wire it up.
Start with the quickstartIs this allowed?
Yes. Each user runs on their own account, under their provider’s terms, and the invariant that keeps it true is enforced in code. Read the provider terms.
What do users install?
The Soba app for Mac, Windows or Linux. It pairs from the browser in one click.
What if their laptop is off?
The run falls back to your supply, billed at your price. Nothing breaks.
Can you see my data?
No. Your tools and data stay on your side. What Soba sees and the security model are written out.
Why not a gateway?
A gateway buys tokens at the margin and resells them, so the price it gets is the price you would get. There is no subsidy in the middle. A consumer plan is the one place the same compute sells for less.
Stop paying for
your free tier.
Let your users run your AI features on the Claude or ChatGPT plan they already pay for.