Ollama Cloud
credits refresh on a published schedule.
https://ollama.com/apiModels mentioned
kimi-k3minimax-m2.7mistral-large-3:675bglm-5.3-flashgpt-oss:120bnemotron-3-nano:30bminimax-m3qwen3.5:397bnemotron-3-ultrakimi-k2.6glm-5.3glm-5.2kimi-k2.7-codedeepseek-v4-pro:0813deepseek-v4-flash:0731deepseek-v4.1-flashgemma4:31bglm-5.1gpt-oss:20bnemotron-3-superEquivalent paid value
How this was valued: The published allowance or a defensible paid comparison is not precise enough to calculate.
The Free plan now receives a recurring monthly Starter usage-credit amount, but Ollama does not publish its face value and the exact Starter-model subset is account-filtered. The retired 5-hour session and weekly windows no longer apply.
Limits and terms
- Concurrent Cloud Models
- 1
- Recurring Starter Credit Amount
- not public
- Recurrence
- monthly
- Reset
- Monthly from the date the user signed up.
- Rollover
- No
- Accounting
- Token-priced usage consumes included credit; purchased credits unlock all cloud models after the included balance is exhausted.
- Transition
- The former 5-hour session and weekly limits no longer apply.
What happens to your prompts?
Ollama says prompt and response data is never logged or trained on and requires no-logging, no-training, zero-data-retention partners, but partner selection, regional routing, human-access detail, and deletion controls are not fully enumerated for every starter model.
- Plan Scope
- Ollama-hosted cloud models using the recurring monthly Starter credit on the Free plan; available routes and partner deployments can vary.
- Prompt Retention
- Ollama's current pricing disclosure says prompt data is never logged.
- Response Retention
- Ollama's current pricing disclosure says response data is never logged.
- Ordinary Logging
- Account, subscription, billing, security, and aggregate usage metadata may be processed; the public cloud disclosures do not enumerate every metadata field or retention period.
- Model Training
- Ollama says prompts and responses are never used for training and requires model partners to provide no-training terms.
- Product Improvement
- The reviewed Cloud disclosures do not grant a broad right to use prompt or response content for product improvement.
- Human Or Operator Access
- Prompt and response content is not retained for later operator review under the published no-logging rule; transient processing and account/usage administration still occur.
- Subprocessors And Routing
- Ollama says it primarily uses dedicated compute in the United States and European Union, with Singapore currently limited to Qwen models, and requires model partners to provide no logging, no training, and zero data retention.
- Deletion Controls
- There is no retained prompt or response record to delete under the published content rule; account and usage-metadata deletion controls and retention schedules are not fully documented on the reviewed Cloud pages.
- Caveat
- The content guarantees are strong, but partner selection, model-specific regions, transient human-access controls, and account/usage-metadata handling are not enumerated for every Starter route, so the conservative classification remains partially private.
No provider terms or privacy-policy link is captured in this snapshot. Review the provider’s current legal documents before sending sensitive data.
Eligibility
- Account Required
- Yes
- Payment Method Required
- not explicitly documented
Primary sources
Before you build with Ollama Cloud
Read the classification narrowly
This record has current first-party evidence for some zero-cost hosted inference. The label describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every region.
Resolve the live model route
This snapshot records 20 model IDs. Match the exact ID against the provider's live catalog before using it in code; zero-price routes and aliases can rotate while an older documentation page remains online. The recorded base endpoint is https://ollama.com/api, but the provider's current API reference remains authoritative for paths, authentication, and request shape.
Confirm account and billing boundaries
An account is required, so public catalog evidence cannot by itself prove the limits, balance, or billing behavior attached to your workspace. The reviewed evidence explicitly says no payment card is required. Re-check the signup flow because eligibility and billing controls can change after the snapshot. The equivalent paid value shown here prices a documented allowance where possible; it is not cash, guaranteed savings, or protection from overage.
Re-read the prompt policy for your plan
This record classifies the reviewed handling as “Partially private”: Ollama says prompt and response data is never logged or trained on and requires no-logging, no-training, zero-data-retention partners, but partner selection, regional routing, human-access detail, and deletion controls are not fully enumerated for every starter model. Provider policies can distinguish free, paid, enterprise, opted-in, and feature-specific traffic, so verify the governing terms for the exact account and route that will receive your data.
Follow the evidence, then re-check it
The record links 5 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest governing document or live catalog when sources disagree, and submit a correction when a provider changes a material term.
Match the quota to the workload shape
Translate the published allowance into the traffic pattern you actually expect instead of comparing headline totals alone. A daily token pool can look generous while a low requests-per-minute or concurrency ceiling blocks interactive bursts; a high request limit can still fail a long-context job when input, output, or per-request tokens are capped. Separate prompt tokens from generated tokens, include retries and tool calls, and test the largest realistic payload. If the provider documents more than one limit window, the tightest window at your peak load is the practical ceiling. Research, experimental, and community access can also carry eligibility or fair-use constraints that cannot be modeled as a simple number.
Plan fallback without changing the rules
A fallback should preserve more than API syntax. Confirm that the substitute route supports the required modality, context length, streaming behavior, structured output, tools, and safety controls, then compare its prompt-retention and training terms. An OpenAI-compatible request shape does not make providers operationally or contractually equivalent. Decide which errors may trigger a retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. If deterministic output matters, record the model revision and sampling settings; rotating aliases and free-model pools can change behavior even when the endpoint remains available.
Monitor the offer as a dependency
Capture the model ID, response model field, rate-limit headers, usage fields, latency, HTTP status, and any provider request identifier for each test. Watch for authorization failures, quota exhaustion, catalog removal, policy revisions, and dashboard balance changes as separate failure modes. Re-check the provider’s live catalog and governing pages on a schedule proportionate to the workload’s importance, and keep the dated sources that supported your decision. Free capacity is especially suitable for prototypes, evaluations, fallbacks, and bounded workloads when the application can tolerate change; a production dependency still needs observability, an exit path, and an owner responsible for re-verification.
Test one complete request before scaling
Start with the smallest permitted request using the exact credential, model ID, endpoint, and account type you intend to deploy. Record the HTTP status, response headers, usage fields, latency, and any dashboard balance change. Then exercise the failure path: an invalid model, an exhausted quota, or a rate-limit response should fail clearly without silently switching to a paid route. If the provider supports streaming or tool calls, validate those features separately because a free model can expose a narrower capability set than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and avoid sending sensitive data until the observed route matches the reviewed data agreement.