Docs

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 Cloud At launch

View as Markdown
On this page
  1. The plans
  2. How each limit is counted
  3. Pull requests
  4. Seeing your usage
  5. What happens when a limit is reached
  6. Before the limit
  7. Events
  8. Replays
  9. Analyses
  10. Projects, people and uptime checks
  11. Pull requests
  12. Getting past a limit
  13. When a plan gets smaller
  14. Example: the shop on the Free plan

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.

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-hostedFreeBuilderTeam
PriceFreeFreeUSD 10 a monthUSD 49 a month
ForYour own infrastructureTrying it on a real projectAn app with real usersSeveral apps and people
ProjectsNo limit set by us1310
Events a monthNo limit set by us5,00050,000500,000
Replays a monthNo limit set by us505005,000
Data kept forAs long as you set7 days30 days90 days
Replay recordings kept forAs long as you setThe plan’s daysThe plan’s days30 days
People on the accountNo accounts: tokens1310
Uptime checks50 for each project by default, yours to change1525
Analyses a day, for each project100 by default, yours to change20100500
Pull requests Sypnia opens a monthNot in the engineNot included50300
The analysis in plain wordsWith your own model keyIncludedIncludedIncluded
The prompt and the MCP serverIncludedIncludedIncludedIncluded
AlertsRecorded, webhookE-mail, in the app, webhookE-mail, in the app, webhookE-mail, in the app, webhook
Daily summary by e-mailNoYesYesYes
SupportCommunityCommunityE-mailPriority 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.

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.

LimitWhat counts as onePeriod
ProjectsA project that is not deleted.At any moment
Events a monthAn 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.Calendar month
Replays a monthA session that has a recording, however long.Calendar month
Data kept forDays 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.Rolling
People on the accountA member, or an invitation not yet accepted.At any moment
Uptime checksA check, paused or not.At any moment
Analyses a dayOne 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.Calendar day, UTC
Pull requests a monthA 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 and Pull requests.

Seeing your usage

Every project has usage counters, visible in the app and through the API: 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.

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.

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.

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close