Blog · Agents
Bring your own AI subscription: what it means and why it matters
"Bring your own AI subscription" means a tool uses the AI account you already have, signed in by you, rather than selling you model access bundled into its own price. You pay the AI provider directly, the tool does not sit in the middle of that relationship, and you can change provider without changing tool.
It is a close relative of "bring your own key", which does the same thing with a developer API key. This guide explains both, what they change about cost, privacy and control, and what to check before relying on either.
Two ways a tool can get its AI
Any product with AI features has to get model access from somewhere. There are two basic arrangements.
Bundled access. The vendor holds an account with one or more AI providers and pays for usage. You pay the vendor a subscription, often with some form of usage allowance. Your prompts usually travel from your device to the vendor's servers, then on to the AI provider, and back the same way.
Bring your own. You hold the account with the AI provider. The tool uses your access to make requests on your behalf. The AI provider bills you, and the tool charges separately, if at all, for what the tool itself does.
Within "bring your own" there are two forms:
| Your own API key | Your own subscription | |
|---|---|---|
| What you hold | A developer key from the provider | A personal or team plan with the provider |
| How you pay | Per use, metered | Usually a flat periodic fee with usage limits |
| How the tool connects | You give the tool the key | You sign in to the provider's own program, which the tool runs |
| Typical user | Developers and technical teams | Anyone who already pays for an AI plan |
The distinction matters. An API key is a secret string, and any tool you paste it into can use it, so where it is stored is important. A subscription sign-in is normally handled by the provider's own application, which keeps its own login. A tool that runs that application does not need to see the login at all.
Why it matters
You pay once
Many people already pay for an AI plan. If every tool they use also bundles AI into its price, they pay for model access several times over. Bringing your own means one bill for the model and a separate, smaller question of what each tool is worth.
Costs are visible
With bundled access, the vendor has to cover a usage cost it does not control, so the price and the plan's limits have to allow for that, and the limits can be hard to predict. With your own account, you see your usage in the provider's own dashboard, under the provider's own published terms.
Your data relationship is direct
When you bring your own account, the terms covering your prompts are those between you and the AI provider: their retention rules, their training policy, their enterprise agreement if your organisation has one. With bundled access, a second company's terms and servers are also involved. That is not necessarily bad, but it is one more party to assess. See what actually gets sent to an AI provider.
You can switch
Models improve at different rates, and which one is best changes. If the tool is separate from the model, you can move to a different provider, or use different ones for different jobs, without moving your work. See running more than one AI coding agent.
Organisations keep their existing controls
A company that has already approved an AI provider, negotiated terms and set up central billing generally wants staff to use that arrangement. A tool that accepts the company's existing accounts fits in. A tool that insists on its own bundled model means another review.
The trade-offs
Bringing your own is not better in every case.
- More setup. You need an account with the provider and must sign in or create a key. Bundled tools work straight away.
- You manage the limits. If you reach your plan's usage limit, the tool stops until it resets or you upgrade. Nobody absorbs that for you.
- Support is split. If a request fails, the cause may lie with the tool or with the provider, and you may have to find out which.
- Terms vary. Providers set their own rules about how subscriptions and keys may be used, including through other software. Read the provider's current terms rather than assuming. Running the provider's own official program under your own sign-in is the most conservative approach.
- Credentials need care. An API key stored carelessly can be copied and used by someone else at your expense. See where your AI keys and logins should live.
What to check in a tool that offers it
- Does the tool ever see your login or key? The best answer is no: the provider's own program handles sign-in, or the key goes straight into the operating system's keychain.
- Where do requests go? Directly from your device to the AI provider, or through the tool vendor's servers first? Both can be legitimate, but you should know which.
- What else is sent? A prompt is expected. Whole folders, background telemetry containing your content, or your files synced to the vendor are different matters.
- Can you use more than one provider? If "bring your own" means one named provider only, you have gained less than it seems.
- What happens if you stop paying the tool? Your AI account remains yours either way. Check that your notes, code and history do too.
A note for teams
Decide early whether people use personal accounts or organisation accounts. Personal accounts are quick to start with but leave the company without oversight of terms, billing or what happens when someone leaves. Organisation accounts take longer to arrange but keep the data relationship with the company. Either way, one person's login should never be shared between several people or built into a shared tool. Each person, and each agent acting for them, should use that person's own sign-in. This also makes clear who is responsible for what an agent does, a point covered in when agents owned by different people work in one room.
Where Prism fits
Prism Desktop follows this model. It runs the AI vendors' own agent programs, and each agent signs in with the owner's own AI account or subscription. Prism never holds that login, keys stay in the computer's keychain, and only the prompt goes to the AI provider the person chose. More detail is on the security page.