loke.dev
Abstract streams of AI model usage flowing through subscription credits and a secured provider key

Kilo Pass or BYOK? Use the Bonus Before It Expires

Compare Kilo Pass, direct credits, and BYOK using measured AI coding usage, expiring bonus value, provider billing, key custody, and Swedish/EU buying checks.

Published By Loke8 min read

Kilo Pass can be cheaper than direct credits when you consume the bonus in the same billing cycle. It can also cost more when usage stays below the paid plan amount. BYOK may reduce the provider bill, but key management and administration belong in the comparison.

Start with the Kilo Pass vs BYOK calculator. Enter one measured month of model usage, then replace the default bonus and administration assumptions with your own.

The short answer

Choose Kilo Pass when your normal usage reliably consumes both the paid credit and most of the monthly bonus. Choose direct Kilo credits when usage is light or unpredictable. Choose BYOK when a supported provider relationship, discount, privacy requirement, or billing arrangement is worth the extra key and account work.

What Kilo Pass includes

On 24 July 2026, the Kilo Pass pricing page listed Starter at $19 per month, Pro at $49, and Expert at $199. The subscription amount becomes the same amount of paid Kilo credits.

For monthly billing, Kilo described a 50% bonus in the first month. A continued subscription then builds a streak bonus that can reach 40%. Annual billing described a 50% bonus every month.

The free bonus expires at the end of each monthly billing cycle. This makes timing important: a headline bonus has no cash value if it expires unused.

Compare cash paid, not nominal credits

For a one-month Pass estimate: cash paid equals the plan price plus model usage above the paid credit and usable bonus. Apply a top-up markup only if the current terms or your observed account charges justify one.

For direct Kilo credits: cash paid equals measured model usage at the provider-equivalent rates shown by Kilo.

For BYOK: operating cost equals the provider bill, any fixed provider fee, and the time required to set up, rotate, restrict, and investigate keys.

Three Pro-plan examples

Low month: $30 of model usage

A $49 Pro subscription requires $49 of cash. Direct credits require $30. The month leaves $19 of paid credit unused and the full $19.60 bonus unused at a 40% rate. Direct credits require $19 less cash for that month.

Working month: $70 of model usage

The $49 paid credit covers the first $49. A 40% bonus contributes $19.60. The remaining $1.40 is a top-up, making total Pass cash $50.40. Direct credits require $70. The full $19.60 bonus becomes useful.

Heavy month: $100 of model usage

The plan and 40% bonus cover $68.60. Another $31.40 is required at a zero-markup top-up assumption, making total Pass cash $80.40. Direct credits require $100. The cash difference is still $19.60 because the bonus is fully consumed.

These examples isolate one month. They do not claim that one model, prompt, or coding task always costs the same. Replace the usage input with an amount measured from your own work.

Direct Kilo credits are the flexibility baseline

Kilo’s credit documentation says $1 becomes $1 of Kilo credit and that model usage is charged at the underlying provider API rate without a general markup. Check the current model list and account ledger because providers and prices can change.

Direct credits fit occasional projects, irregular usage, and early evaluation. You do not need to force work into a billing cycle merely to consume a bonus.

The tradeoff is simple: no Pass bonus means no subscription discount. At stable usage above the plan price, a fully used Pass bonus can reduce cash paid.

BYOK changes who bills and who holds the key

Kilo’s BYOK documentation says supported requests use the provider key you add and are billed by that provider. Kilo records a $0 charge for those requests. An invalid BYOK key does not fall back to Kilo credits.

That can be useful when a team already has provider billing, negotiated rates, spend controls, or a requirement to keep AI usage under a specific vendor account.

  • Use provider-side budgets, rate limits, and invoice history already owned by the team.
  • Apply a real contracted discount instead of assuming public list price.
  • Separate Kilo product access from the provider account that pays for inference.

BYOK is not automatically free. Provider usage still costs money. Some provider plans add a fixed charge, and the team owns more operational work.

  • Create a dedicated key instead of reusing a personal or production credential.
  • Restrict the key where the provider supports project, model, budget, or network controls.
  • Rotate and revoke keys when access changes or suspicious usage appears.
  • Reconcile two systems when a Kilo request and provider invoice disagree.

Put key custody in the decision

Kilo’s gateway authentication documentation says BYOK keys are encrypted at rest with AES-256 and that requests using them are tracked with zero Kilo-side cost. Encryption at rest is useful, but it does not replace your provider-side access policy.

For a team, document the key owner, permitted projects, spending limit, rotation interval, and incident contact before adding the credential. A personal key tied to one employee is a weak default for shared work.

Model mix can move the result more than the plan

Input tokens, output tokens, cached input, context length, tool calls, retries, and provider choice can all change the charge for the same broad coding task. Counting chat messages is not a dependable cost model.

A lower-cost model for routine edits and a stronger model for difficult reasoning can outperform an all-premium default. The important input for the calculator is the resulting provider-equivalent spend, not how busy the month felt.

Run a two-week measurement before subscribing

  • Choose a representative project and keep the model-routing policy stable for two weeks.
  • Record daily model charges, failed or repeated requests, and the tasks that caused large context windows.
  • Separate experimental use from recurring development work.
  • Project the measured total to one month, then test low, expected, and high cases in the calculator.
  • Count BYOK setup and maintenance time at a defensible internal hourly value.

A Pass is a good candidate when expected usage consumes the paid credit and most of the bonus in the low or expected case. If only the high case consumes it, direct credits preserve more flexibility.

Team controls can outweigh a small price difference

For multiple developers, compare account ownership, role management, audit history, budgets, key rotation, and offboarding. Saving $15 per month is not a win if a shared provider credential creates unclear ownership or delayed incident response.

If the AI tool will touch a production application, pair the cost review with the AI app production-readiness checklist.

Notes for a Swedish or EU buyer

Before committing to a subscription or provider account, verify the legal counterparty, invoice fields, currency, payment method, VAT treatment, and whether the invoice works for your Swedish bookkeeping. Do not infer these details from a USD marketing price.

For company source code or customer data, review what can be sent to Kilo and to the selected model provider, where each party processes it, retention settings, sub-processors, and the contract available to your organisation. BYOK changes billing and key ownership; it does not by itself prove an EU processing location or a particular privacy outcome.

For material tax, accounting, employment, or data-protection decisions, use your accountant or legal adviser. This guide is a technical and cost-planning framework.

Choose the operating model

Choose Kilo Pass when usage is recurring, the bonus is likely to be consumed each month, and Kilo-managed credits keep operations simpler.

Choose direct Kilo credits when usage is light, new, seasonal, or hard to forecast.

Choose BYOK when provider-side controls, discounts, billing, or contract terms are worth the key-management work.

Choose a free or local model path when its output quality, hardware cost, privacy design, and maintenance burden fit the work better than a paid hosted model.

Calculate the month before choosing

Open the Kilo Pass vs BYOK calculator, enter measured model usage, and compare cash paid with unused credits and administration shown separately.

Then check the current Kilo Pass and BYOK options. The link is direct and currently earns no commission.

Primary sources checked

Kilo Pass pricing and bonus terms

Kilo credit purchase and rate documentation

Kilo BYOK setup and billing behavior

Kilo Gateway authentication and BYOK key handling

Kilo partner program