> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iriscode.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Scan allowances: how many cloud scans you get, and how they are counted

> Cloud scans use the selected personal or team allowance. Every accepted scan counts once, whoever started it, and paid, trial and Free allowances stay separate.

Each cloud scan uses one scan from an allowance: a set number of scans per month or per period. The rule is deliberately simple: **every audit counts one, whoever or whatever started it.**

Your personal account and each team have their own allowance. This page explains how much you get, what counts, and what happens when it runs out.

## Free and paid allocations

Your **Projects** screen shows your current allowance, as recorded on Iris Code's servers. Signed-in Free personal accounts and Free Teams get a cloud allowance every month, separate from their local project actions. [Free allowances](https://docs.iriscode.co/free.md) explains how Free capacity works and what you can still read after it runs out.

The [pricing page](https://iriscode.co/pricing) reads paid plan quantities from the same settings that count your scans. For paid Teams it shows the total included and the amount per seat. Your **Projects** screen also names which allowance you are using, how much is used and the exact reset date.

Repositories start in manual mode. Free and paid users can choose to turn on automatic scans for merges or pull requests. Automatic and manual scans come out of the same allowance.

## Paid and trial allocations

| | Window | Scans |
| - | - | - |
| **Pro** | per billing month | Current allocation shown in your account |
| **Teams** | per billing month | Current shared allocation shown in team billing |
| **Pro trial** | Trial period | As shown in your account |
| **Teams trial** | Trial period | As shown in the team |

## What counts as one scan

All of these count, equally:

* An audit you start yourself from the project screen
* An audit triggered by a change landing on your default branch
* An audit triggered by a pull request being opened or updated
* The first audit queued when you import a repository

These do not count, because they produced no report:

* An audit you cancelled
* One replaced by a newer push to the same branch or pull request
* One no scanner picked up, or that timed out
* One stopped because the repository was paused or GitHub access ended

## Reset dates by plan

Free allowances reset monthly, on the first at 00:00 UTC. Paid allowances follow your billing period instead, so if your period starts on the 14th, that is when it resets.

A trial has its own set allowance and end date. **Projects** shows the exact reset date for the allowance you are using. Starting a paid plan or a trial does not refill the Free allowance underneath.

## Personal and team allowances are separate

Your personal account and each team have separate scan allowances. Unused scans cannot be moved between them.

* Your account uses your personal allowance
* Each team uses that team's allowance
* Being in two teams means two separate allowances, both usable, neither shared

> [!WARNING]
>
> A paid team seat does **not** add scans to your personal account. Team repositories use the team's allowance; personal repositories use your own Free, trial or paid allowance. You do not need a personal Pro subscription to use your personal Free scans. See [Team entitlement](https://docs.iriscode.co/teams/entitlement.md).

## Running out

You are warned when 80% of the allowance has been used. The card on your **Projects** screen turns amber and says so, while there is still enough left to act on.

If it does run out, automatic audits stop for every repository in that account or team, and each one shows "allowance used". Your GitHub connection is untouched and existing reports are unaffected. Audits start again on their own when the allowance resets, and the screen shows the date.

## Getting more

There are three ways, depending on your situation:

* **Adding seats** changes the team's paid allowance according to its current billing settings
* **Subscribing** replaces a trial allowance straight away
* **Scanning merges only**, rather than every pull request update, is the single setting that saves the most scans. See [Audit triggers](https://docs.iriscode.co/cloud/triggers.md)

> [!NOTE]
>
> You cannot buy extra scans yet. If an account or team runs out, the options are the three above or waiting for the reset.

## Working out what you need

Estimate how many changes land on your default branch and how often pull requests are updated, then compare that with the allowance shown in your account. Each merge uses one scan. Stay in manual mode if automatic scans would use up the allowance faster than you want.

Turning on pull request scans multiplies the number by how many times a branch is pushed before it merges, which is usually three to five. Estimate that before switching it on across every repository.

> [!TIP]
>
> Separately, each repository has a daily scan limit. It is a safety stop for runaway loops, not a budget. It sits far above a busy day and exists so a misconfigured CI job cannot use a month's allowance in an afternoon. Hitting it means something is looping, not that you are working too hard.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.