Methodology: assumptions you can inspect
Read the scope, formulas, verification policy and exclusions behind ModelBudgetCalc’s Ollama monthly cash estimates.
This is a deterministic planning calculator for current Ollama monthly credit plans. It is not an account connection, universal token counter or invoice audit. All sample workloads are synthetic. The public pricing snapshot is dated; it is not a live feed.
Primary sources
- Ollama pricing: monthly fees, included usage, model rates, published peak rates and concurrency.
- Transparent-pricing announcement: introduction of credit plans, resets and legacy context.
- Usage documentation: total input, cached subset and output fields.
- Cached-input implementation: supporting field semantics.
- Cloud documentation: hosted versus local execution.
Formula
Total requests equal requests per active day multiplied by active days within one monthly billing period. The day count is a whole number from one to thirty-one, not a forecast across monthly resets. A shorter active workload still incurs the selected plan's full monthly fee; fees and allowances are not prorated. Fresh input is total input multiplied by one minus the assumed cache share. Cached input is total input multiplied by that share. Each token category is priced per million at its effective rate. Effective rate equals base rate plus the token-weighted peak share multiplied by the difference between peak and base rates. The same category mix is assumed during peak and off-peak work.
Consumption is the sum of the three category costs. Each plan's estimated cash equals its monthly fee plus any consumption beyond included usage. Unrounded results determine minima; tied plans remain tied. Remaining-credit forecasts use user-entered consumed usage, daily pace and days until reset. They do not infer account balances or exact exhaustion dates.
Limits and freshness
Excluded: unknown starter allowances, legacy quota conversions, annual purchase cash flow, taxes, exchange rates, prepaid top-up timing, proration, promotions, model-quality comparisons, multimodal tokenization, and separate client or hosting costs. Team availability must be checked independently. A lower modeled price is not an eligibility or performance recommendation.
The interface marks the snapshot stale after fourteen days. A changed source should trigger a reviewed data update and calculation checks before a release, not an unreviewed automatic overwrite. Until an update is published, follow the provider's current terms where they differ. See contact status for the correction channel, and return to the calculator.