Ollama Cloud is the cloud-based model inference service from the Ollama team that lets users call open-source large language models without building their own hardware. Unlike token-metered API services from OpenAI, Anthropic, and others, Ollama Cloud uses a GPU time-based usage model and sets up a distinctive dual constraint: a “5-hour session limit” and a “7-day weekly limit”. This article sorts through the public information on the official pricing page and combines real test experiences from community users to serve as a reference for developers evaluating the service.

1. Overview of Official Pricing Plans

According to the Ollama official pricing page, the Cloud service comes in three tiers:

Benefits of each plan

Free ($0)

• Running models locally is completely free and unlimited
• Access to cloud models
• CLI, API, and desktop app support
• Data privacy protection
• Unlimited public model pulls
• Concurrency limit: 1 cloud model at a time

Pro ($20/month)

• Includes all Free benefits
• Concurrent cloud models: 3
• Cloud usage: 50x that of Free
• Can upload and share private models

Max ($100/month)

• Includes all Pro benefits
• Concurrent cloud models: 10
• Cloud usage: 5x that of Pro (i.e. 250x that of Free)

2. How Usage Is Metered: GPU Time, Not Token Count

Ollama Cloud’s usage metering is fundamentally different from mainstream API providers.

Official explanation

According to the official FAQ:

Key points:

• Billed by GPU time, not a fixed token count or request count
• The larger the model and the longer requests run, the faster usage is consumed
• Short requests and prompts that hit the context cache consume less
• As hardware and model architecture efficiency improve, a given plan may provide more usable time in the future

The dual-limit mechanism

Cloud usage is governed by two independent limits:

Note: Running models locally is not subject to any of these limits.

3. Community Testing: Converting GPU Time to Token Equivalents

Since the official GPU-time quota is not published, community users have estimated it through real-world testing.

Source note

The following data comes from Reddit user u/nusquama’s test post Tracked my Ollama Cloud free tier usage to estimate Pro and Max quotas (posted to r/ollama and r/LocalLLaMA):

Test observations

The user observed the following in a single Free-tier session:

From this it can be inferred:

• Free tier 5-hour Session quota ≈ 2 million token equivalents
• Free tier Weekly quota ≈ 2 million ÷ 0.4 = 5 million token equivalents

Applying the official multipliers (Pro 50x, Max 5x Pro):

Important limitations and disclaimer

Here are the warnings that user explicitly listed:

Key uncertainties:

1. Huge model differences: For the same token count, a 70B model can consume up to 10x more GPU time than a 7B model
2. Single test sample: Based on a single session and a single model
3. Dynamic adjustment: Ollama may adjust quotas in the background without advance notice
4. Concurrency overhead: Running multiple models at once can consume GPU memory even when inactive

4. Concurrency Limits and the Request Queue

In addition to usage limits, Ollama Cloud also sets a hard cap on the number of cloud models running simultaneously:

How the queue works

According to the official documentation:

This means:

• Even when using the same model, concurrent requests occupy separate slots
• When a Pro user sends 4 requests at once, the 4th enters the queue and waits
• The queue has limited depth; it simply errors out under severe overload

5. Available Models and Features

Cloud model list

The mainstream open-source models supported by Ollama Cloud include:

• Qwen series: qwen3.5 (multiple sizes), qwen3-coder-next (code-specialized)
• Google: gemma4 (multimodal)
• Z.ai: glm-5, glm-5.1 (large-parameter MoE architecture)
• MiniMax: minimax-m2.7, ministral-3
• Mistral: devstral-small-2
• NVIDIA: nemotron-3-super

The full list can be viewed in the Ollama Cloud model library.

Feature support

• Tool Calling: models with tool support are tested against real Agent workflows before being listed
• Weight format: uses the native weights published by the model provider; on modern NVIDIA hardware, accelerated formats for Blackwell / Vera Rubin architectures (such as NVFP4) may be enabled
• Privacy protection: Prompt and Response data is never logged or used for training

6. Use-Case Assessment

Scenarios where it fits well

Scenarios where it’s less suitable

1. Ultra-high-concurrency production service: Max only supports 10 concurrent models; anything beyond that must queue. Not suitable for large-scale public API services
2. Unlimited cloud calls: even Max has a periodic cap, and there is currently no way to purchase extra quota on top
3. Strict data-stays-at-home requirements: traffic may be routed to Europe and Singapore, so enterprises with a hard “data must not leave the country” requirement should be cautious
4. Need a clear SLA: Ollama has not published a service-level agreement (SLA) or a dedicated enterprise support channel
5. Dedicated compute for very large models: there is no “exclusive GPU / dedicated instance” tier

7. Community Feedback Summary

Positive feedback

Negative feedback

Concerns about dynamic adjustment

A Reddit post titled Ollama Cloud: Usage limit reduction in past 24 hours notes:

This suggests quotas can be dynamically adjusted, and users are advised to check the usage dashboard regularly.

8. How to View Real-Time Usage

Users can check the ollama.com/settings page for:

• Session usage: a percentage, reset every 5 hours
• Weekly usage: a percentage, reset every 7 days
• Reset countdown

When usage reaches 90%, the system sends an email reminder (which can be turned off in settings).

9. Summary and Decision Reference

Key decision advice:

• If you mostly use small 7B-class models, the cost-effectiveness of Pro may come close to the community estimate
• If you rely on 70B+ large models, the actual usable tokens shrink dramatically, and Max may be the only choice
• For scenarios requiring a strict SLA, data localization, or high-concurrency public services, consider comparing enterprise options like AWS Bedrock and Azure OpenAI

10. Sources and Disclaimer

Official sources

• Ollama official pricing page
• Ollama Cloud model library
• Ollama GitHub Issue #12532: feature request for fetching usage stats via the API
• Ollama GitHub Issue #13728: discussion on showing usage in third-party tools

Community sources

• Reddit r/ollama:
• u/nusquama: Tracked my Ollama Cloud free tier usage to estimate Pro and Max quotas
• Cloud Pro Usage Limits discussion
• Ollama Cloud: Usage limit reduction in past 24 hours
• Ollama Cloud models good for coding?
• Reddit r/LocalLLaMA: crosspost of the same u/nusquama post
• Reddit r/openclaw: user feedback on integrating Kimi k2.5 with Ollama Cloud

Disclaimer

This article is compiled from the following material:

1. Official public documentation: the latest official pricing and FAQ pages as of the retrieval date
2. Community user testing: user experiences shared on Reddit and other platforms, not verified by the official team
3. Inferred data: based on a single test by a single user, with no statistical generalizability

Important note:

• Ollama Cloud usage quotas may be dynamically adjusted, and the official team may change limits without advance notice
• The token-equivalent conversions are for reference only; actual usage varies greatly depending on model size, request patterns, cache hit rate, and other factors
• This article does not constitute a purchase recommendation; choose a plan based on your own use case and budget
• Before buying, it’s advisable to test thoroughly on the Free tier and observe how quickly your usage is consumed

This article was last updated in April 2026. Since the Ollama Cloud service may iterate continuously, readers are advised to check the latest official documentation before deciding.