# Plans and limits

> What each Sypnia Cloud plan includes, exactly how each limit is counted, and what happens when a limit is reached.

Applies to: Sypnia Cloud (paid service). Status: at launch.  
Source: https://docs.sypnia.com/cloud/plans-and-limits/

**\[Cloud]** This page is for anyone choosing a plan or wondering what a number on the pricing page means. Limits exist only on Sypnia Cloud. A self-hosted engine has no limits set by us.

> **Note: A proposal**
>
> Plan names, prices and limits come from `src/config/pricing.ts` in the website's repository and are a proposal until the owner confirms them. Fixed already: a free tier, the price of the Builder plan, and that self-hosting is free. The limits of the Free plan follow one rule: no free project may cost Sypnia more than USD 3 a month, everything included.

You pay for how much you send, and for pull requests. Every plan has replay, traces, the analysis in plain words, the prompt and the MCP server. Pull requests opened by Sypnia are part of the Builder and Team plans.

## The plans

Every number of every plan is in this table, and nowhere else on this page.

|                                    | Self-hosted                                     | Free                        | Builder                     | Team                        |
| ---------------------------------- | ----------------------------------------------- | --------------------------- | --------------------------- | --------------------------- |
| Price                              | Free                                            | Free                        | USD 10 a month              | USD 49 a month              |
| For                                | Your own infrastructure                         | Trying it on a real project | An app with real users      | Several apps and people     |
| Projects                           | No limit set by us                              | 1                           | 3                           | 10                          |
| Events a month                     | No limit set by us                              | 5,000                       | 50,000                      | 500,000                     |
| Replays a month                    | No limit set by us                              | 50                          | 500                         | 5,000                       |
| Data kept for                      | As long as you set                              | 7 days                      | 30 days                     | 90 days                     |
| Replay recordings kept for         | As long as you set                              | The plan's days             | The plan's days             | 30 days                     |
| People on the account              | No accounts: tokens                             | 1                           | 3                           | 10                          |
| Uptime checks                      | 50 for each project by default, yours to change | 1                           | 5                           | 25                          |
| Analyses a day, for each project   | 100 by default, yours to change                 | 20                          | 100                         | 500                         |
| Pull requests Sypnia opens a month | Not in the engine                               | Not included                | 50                          | 300                         |
| The analysis in plain words        | With your own model key                         | Included                    | Included                    | Included                    |
| The prompt and the MCP server      | Included                                        | Included                    | Included                    | Included                    |
| Alerts                             | Recorded, webhook                               | E-mail, in the app, webhook | E-mail, in the app, webhook | E-mail, in the app, webhook |
| Daily summary by e-mail            | No                                              | Yes                         | Yes                         | Yes                         |
| Support                            | Community                                       | Community                   | E-mail                      | Priority e-mail             |

«Self-hosted» is the open-source engine on your own servers. It is in the table so you can compare; nothing else on this page applies to it. You can set your own quotas on an engine in its [configuration](https://docs.sypnia.com/self-hosting/configuration).

## How each limit is counted

A plan belongs to an organization. Limits are for the organization as a whole, across all its projects and all their environments, except the analyses a day, which are for each project.

| Limit                 | What counts as one                                                                                                                                                                                                              | Period            |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
| Projects              | A project that is not deleted.                                                                                                                                                                                                  | At any moment     |
| Events a month        | An error, a trace, or a performance sample. Page views, clicks, rage and dead clicks, form failures and custom events are free. The exact rules are in [Events](https://docs.sypnia.com/concepts/events).                       | Calendar month    |
| Replays a month       | A session that has a recording, however long.                                                                                                                                                                                   | Calendar month    |
| Data kept for         | Days since the data was recorded. Replay recordings have their own row in the table. What each number applies to, kind by kind, is in [Data location and retention](https://docs.sypnia.com/cloud/data-location-and-retention). | Rolling           |
| People on the account | A member, or an invitation not yet accepted.                                                                                                                                                                                    | At any moment     |
| Uptime checks         | A check, paused or not.                                                                                                                                                                                                         | At any moment     |
| Analyses a day        | One run of the agent on one problem: the first analysis, a new one because the problem grew or came back, and one you asked for. See [Limits](https://docs.sypnia.com/agent/limits).                                            | Calendar day, UTC |
| Pull requests a month | A pull request that Sypnia opened. Asking for one that cannot be written, because the evidence is not enough, does not count.                                                                                                   | Calendar month    |

A calendar month runs from the first day at 00:00 UTC to the first day of the next month. Counters start at zero each month, and what you did not use does not carry over.

## Pull requests

Pull requests are part of the Builder and Team plans. They are not included in the Free plan, where the fix goes to your coding agent through the prompt or the MCP server, as on a self-hosted engine.

On Builder and Team, pull requests are a setting of each project, and it is **off** until an owner or an admin turns it on. Sypnia opens no pull request in a project where the setting is off. See [The GitHub App](https://docs.sypnia.com/cloud/github-app) and [Pull requests](https://docs.sypnia.com/agent/pull-requests).

## Seeing your usage

Every project has usage counters, visible in the app and through the [API](https://docs.sypnia.com/api/projects-keys-and-tokens): events, replays and analyses, for the current month and the ones before. The organization's page adds them up and shows them against the plan.

## What happens when a limit is reached

**Nothing is dropped silently.** Each time, three things are true: the SDK is told, the organization's owners are told, and Sypnia counts what it did not store.

### Before the limit

At **80 %** of the events or the replays of the month, the organization's owners get an alert by e-mail and in the app. The daily summary carries a usage line from then on.

### Events

At **100 %** of the month's events:

1. The owners get an alert by e-mail and in the app.
2. Ingest tells the SDKs to slow down until the month ends. From then on they send **failures only**: errors, failed calls and, from your server, the requests that failed with their spans. They also keep sending what ties a failure to a visit and a person: session starts, page views and who the person is.
3. The SDKs stop sending the rest: performance samples, requests that worked, clicks, form failures and custom events. Recording of replays stops too.
4. Every answer from ingest says how many events were stored and how many were not, and why. The app shows the total not stored since the limit was reached.

So past the limit you still learn about a new problem, and you are still alerted. What you lose until the month ends, or until you change plan, is the picture around it: performance numbers, what people clicked, and replays.

Uptime checks are not events. They keep running and alerting.

### Replays

At **100 %** of the month's replays, the SDKs are told to stop recording. Sessions are still listed with their full timeline. A session that would have been recorded says «not recorded: the month's replays were used». Everything else carries on.

### Analyses

When a project has used its analyses for the day, a new problem keeps its technical title, still alerts, and its prompt still carries the evidence. The next day the problems that were skipped and are still open are analysed first. See [Limits](https://docs.sypnia.com/agent/limits).

### Projects, people and uptime checks

Creating one more than the plan includes is refused, with a message that names the limit and the plan. Nothing that exists is touched.

### Pull requests

Asking for one more than the month includes is refused, with a message that says when the count starts again. The prompt and the MCP server have no limit, so the fix can still go to your coding agent.

### Getting past a limit

Change to a larger plan. New limits apply at once: the SDKs are told to resume within minutes, and recording restarts with the next session. There is no overage charge on any plan: Sypnia never bills more than the plan's price. See [Billing](https://docs.sypnia.com/cloud/billing).

## When a plan gets smaller

Moving to a smaller plan, or back to Free, takes effect at the end of the period you paid for. Before you confirm, the app shows what will change:

- **Retention.** Data older than the new plan keeps is deleted the day the change takes effect.
- **Projects.** If you have more projects than the new plan includes, you choose which stay active. The others are paused: they stop receiving data, and what they hold stays readable until it expires or you delete it.
- **People.** If you have more members than the new plan includes, you choose who stays. The others leave the organization; their accounts are not deleted.
- **Uptime checks.** Checks beyond the new number are paused, newest first.
- **Pull requests.** On Free, Sypnia opens no new pull requests. The ones already open stay in your repository; they are yours.

## Example: the shop on the Free plan

The shop is small, and in a normal month it stays inside the Free plan's events.

In a busy month it reaches 80 % of them on the 24th. The owner gets the alert. On the 29th it reaches 100 %. From then until the 1st, Sypnia keeps receiving failures, so the broken Pay button would still become a problem and send an alert, but page speed for those two days is missing, and the app says how many events were not stored. On the 1st, at 00:00 UTC, everything resumes.

Moving to Builder on the 29th would have resumed everything within minutes.
