# Limits

Source size, file and folder limits, Quick scan thresholds, schedule timing, member and invite limits, and the request limits of the MCP server.

*Last updated: 2026-10-21*

The limits that decide whether a scan can start or finish, and the ones that shape how you use the portal and the MCP server. The source and file limits apply to each code source; the sections below say what the others apply to.

## Source size

Kelrova checks each code source against these limits when a scan prepares its code.

| Limit | Value |
| --- | --- |
| Source written after exclusions | 1 GiB |
| Compressed download | 2 GiB |
| Decompressed size, including skipped entries | 4 GiB |

The figure to plan around is **1 GiB of source after exclusions**. Excluded paths and skipped files are not written, so they do not count toward that limit. They are still downloaded, so they do count toward the compressed and decompressed limits.

A source that goes over a limit stops the scan with a reason that names the limit: after exclusions, archive stream or archive download. It never lists file paths. To get under a limit, narrow the code source to a folder, or add excluded paths. See [Add a code source](https://kelrova.com/docs/getting-started/code-sources).

## Files and folders

| Limit | Value |
| --- | --- |
| Largest file a scan reads | 8 MiB |
| Excluded paths per code source | 50 |
| Length of an excluded path | 1 to 200 characters |

Files larger than 8 MiB are skipped automatically. The scan continues with the rest and finishes as partial, with the number of files skipped. A file of exactly 8 MiB is kept.

## Quick scans

| Limit | Value |
| --- | --- |
| Changed files before Standard is recommended | 150, counted after excluded paths |
| Quick previews | 30 per person and 120 per organization, every 10 minutes |
| Sources in a project for the preview | 32 |

A project with more than 32 sources has no Quick preview.

## Schedules

| Limit | Value |
| --- | --- |
| How often a schedule runs | Daily, weekly or every 2 weeks |
| First run | From five minutes to 90 days ahead, in whole hours of your time zone |

## Organization

| Limit | Value |
| --- | --- |
| Members on Basic | 3 |
| Members on Go, Pro and Max | Unlimited |
| Invite lifetime | 7 days |
| Top-ups | $10, $25, $50, $100 or $250 |

Included usage equals the plan's monthly price and does not roll over. There is no metered overage. See [Plans and the trial](https://kelrova.com/docs/organization/plans).

## The MCP server

Requests are counted every 60 seconds, per connection and per organization, in two buckets: read, for discovery, listings and the four read tools, and write, for reports and re-checks. Counters are approximate.

| Bucket | Per connection | Per organization |
| --- | --- | --- |
| Read | 120 | 1,200 |
| Write | 30 | 300 |

These are the default limits. Kelrova can raise them for an organization, and the organization can set a lower cap of its own. Re-checks also have their own budget: 10 per hour per connection and 50 per hour per organization. When a limit is reached, the answer is `rate_limited` with a `Retry-After` value in seconds.

| Token | Lifetime |
| --- | --- |
| Machine client token | 15 minutes, no refresh token |
| Access token without Stay connected | One hour |
| Connection unused | Ends after 30 days |

[Troubleshooting](https://kelrova.com/docs/mcp/troubleshooting) covers what to do when a connection stops working.

## Related

- [Questions people ask](https://kelrova.com/docs/reference/faq)
- [Add a code source](https://kelrova.com/docs/getting-started/code-sources)
- [Troubleshooting](https://kelrova.com/docs/mcp/troubleshooting)
- [When Quick applies](https://kelrova.com/docs/scans/quick-scans)