> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/billing-and-subscription/pricing-plans.md).

# Argos pricing plans

Compare the Hobby, Pro, and Enterprise plans to find the right Argos pricing for individuals, teams, or companies.

Argos offers plans for individuals, teams, and enterprises — from the free Hobby plan to fully custom Enterprise options. For current details, see the [pricing page](https://argos-ci.com/pricing).

### Hobby plan

Best for individuals and small projects.

* **Price**: Free
* **Screenshots included**: 5,000 / month
* **Extra screenshots**: Not available
* **Media sharing**: public share pages, 30-day retention, 50 MB per file

### Pro plan

Designed for teams, with usage-based pricing.

* **Starting price**: $100 / month
* **Screenshots included**: 35,000 / month
* **Extra screenshots**:
  * Standard: $0.004 per screenshot
  * Storybook: $0.0015 per screenshot
* **Optional add-ons** (Stripe subscriptions only):
  * [GitHub SSO](/docs/learn/account-and-access/github-single-sign-on.md): $50 / month
  * [SAML SSO](/docs/learn/account-and-access/saml-single-sign-on.md): $200 / month
* **Media sharing**: team-scoped or public share pages, 1-year retention, 500 MB per file

You can subscribe to the Pro plan with a credit card through [Stripe](/docs/learn/billing-and-subscription/how-to-subscribe.md), or through [GitHub Marketplace](https://github.com/marketplace/argos-ci) to pay via your GitHub invoice. Marketplace plans come in fixed sizes (S, M, L, XL) with increasing screenshot limits instead of usage-based billing — see [Usage & spend management](/docs/learn/billing-and-subscription/spend-management.md) for how each model handles going over the limit.

### What counts as a screenshot

Every snapshot Argos stores for a build counts as one screenshot, whether it is an image or a non-image file such as Markdown, JSON or HTML.

[Media uploads](/docs/learn/media.md) draw on the same allowance rather than a separate quota: one uploaded image counts as 1 screenshot, and one uploaded video as 25 — a video costs more to store and to serve. Uploading the same file twice is free.

### Open-source plan

Argos sponsors selected [open-source projects](/docs/learn/billing-and-subscription/open-source.md) with free usage, evaluated case by case.

### Enterprise plan

For large organizations with custom requirements: custom screenshot volumes, [SAML single sign-on](/docs/learn/account-and-access/saml-single-sign-on.md), and [fine-grained access control](/docs/learn/account-and-access/team-members-and-roles.md).

[Contact us](https://argos-ci.com/contact) to design the right plan for your business.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://argos-ci.com/docs/learn/billing-and-subscription/pricing-plans.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.