Canonical Technical Definition

A software architecture model where users supply their own private API credentials (e.g., OpenAI, Anthropic) directly to an application, eliminating middleman proxies and markups.

Bring Your Own Key (BYOK)—often termed user-provided API keys—is an architectural design pattern in software where an application allows users to supply their own personal API credentials for third-party machine learning providers (such as OpenAI, Anthropic, or Mistral AI) rather than forcing them to pay a marked-up subscription to a middleman vendor.

When commercial AI tools emerged, most SaaS startups adopted a reseller business model: they wrapped public AI APIs in a basic web interface, marked up the underlying token costs by 500% to 1,000%, and charged users $20 to $30 per month. Crucially, all customer prompts and transcripts were routed through the startup’s intermediate cloud servers.

The architectural differences: Vendor Proxy vs BYOK

Vendor Reseller Model (Traditional SaaS):
[User Mac] ──> [Vendor Middleman Cloud] (Logs & Marks Up Tokens) ──> [AI Provider API]

Bring Your Own Key Architecture (Oyma):
[User Mac] ────────────────(Direct Encrypted TLS Connection)──────────────> [AI Provider API]
(Zero Vendor Middleman / Zero Token Markup / Direct Enterprise Terms)

The four core advantages of BYOK

1. Massive cost savings (Wholesale pricing)

Transcribing a 60-minute meeting via direct API typically costs under $0.10, and summarizing it with a fast model costs less than $0.02. A user holding their own API key might spend $2.00 across an entire month of meetings, compared to paying $240.00 annually for a rigid cloud subscription.

2. Elimination of middleman privacy risks

In proxy architectures, the startup’s servers see your unencrypted meeting transcripts and private notes. With BYOK, the application connects directly from your Mac to the provider’s API endpoint over TLS. The software creator has zero technical visibility into your requests.

3. Enterprise zero-retention contractual terms

Major API providers (including OpenAI and Anthropic) explicitly contract under their commercial API terms that data sent via paid APIs is never used to train future foundation models, and is subject to strict 30-day zero-retention policies. Consumer web chat interfaces do not offer these protections.

4. Freedom to choose models

With BYOK, you are not locked into whatever model the vendor hardcodes. You can swap between GPT-4o, Claude 3.5 Sonnet, or local Ollama instances at will based on cost, speed, or reasoning requirements.

BYOK in Oyma

Oyma supports full Bring Your Own Key flexibility on macOS:

  • You can run 100% offline using on-device Whisper and local Ollama models.
  • If you desire cloud intelligence for complex document synthesis, you can input your private API key.
  • Your key is stored securely in macOS Keychain. Requests route directly from your Mac to the provider with zero middleman logging.

Frequently asked questions about Bring Your Own Key (BYOK)

What is the primary benefit of Bring Your Own Key (BYOK)?

BYOK eliminates third-party subscription markups and middleman servers. You pay the AI provider directly for raw wholesale token usage (pennies per month) and maintain your own contractual privacy terms.

How does BYOK protect privacy compared to bundled SaaS AI plans?

In bundled SaaS plans, your data passes through the vendor's proxy servers where it can be logged. With BYOK, requests travel directly from your local application to the AI provider under enterprise API zero-retention terms.

Where are API keys stored in Oyma on macOS?

In Oyma, your API keys are stored securely in your Mac's encrypted Apple Keychain or local configuration file; keys are never transmitted to Oyma servers.