Docs

Billing

How paying for Sypnia Cloud works, including what changing or cancelling a plan does, what a failed payment does, and what you are never charged for.

Applies to Cloud At launch

View as Markdown
On this page
  1. The short version
  2. Who pays, and for what
  3. Paying
  4. Changing plan
  5. When a payment fails
  6. Refunds
  7. If prices change
  8. What is never charged
  9. Example: the shop moves to Builder

Cloud This page is for the owner of an organization on Sypnia Cloud. A self-hosted engine has nothing to bill: it is free, and you pay your own infrastructure.

The short version

  • The Free plan needs no card and has no time limit.
  • Paid plans are Builder, USD 10 a month, and Team, USD 49 a month.
  • You are billed once a month, in advance, in US dollars.
  • There is no overage charge. Sypnia never bills more than the plan’s price. When a limit is reached, Sypnia slows down and tells you; it does not charge more. See Plans and limits.
  • You can change plan or cancel at any time, from the app.

Who pays, and for what

A plan belongs to an organization, not to a person or a project. One plan covers all the organization’s projects and people. Only an owner can choose the plan, enter the payment method and see invoices. See Organizations and teams.

If you belong to two organizations, each has its own plan and its own bill.

Paying

HowBy card.
Who handles the cardA payment provider, Stripe. Your card details go to the provider; Sypnia never sees or stores the card number.
WhenThe day you start a paid plan, and the same day of each month after that.
CurrencyUS dollars.
TaxesPrices do not include taxes. If a tax applies in your country, it is shown before you pay and on the invoice.
InvoicesOne for each payment, in the app and by e-mail to the owners. You can add your company name, address and tax number, and they appear on later invoices.

Changing plan

To a larger plan. The change is immediate. You pay the difference for the days left in the current period, and the full new price from the next one. The new limits apply at once: if Sypnia had slowed down because a limit was reached, it resumes within minutes.

To a smaller plan, or to Free. The change takes effect at the end of the period you already paid for. Until then you keep the current plan. Before you confirm, the app shows what the smaller plan will change: shorter retention, fewer projects, people and uptime checks. Those rules are in Plans and limits.

Cancelling a paid plan is moving to Free: it takes effect at the end of the paid period, and nothing is charged after it. Your organization, projects and data stay, within the Free plan’s limits.

To stop using Sypnia altogether and have your data deleted, delete the organization. See Deleting data.

When a payment fails

  1. The owners are told by e-mail the same day, and the app shows a notice.
  2. The payment is tried again several times over the next 14 days. The plan stays active meanwhile, with its full limits.
  3. Three days before the 14 days end, the owners are told again.
  4. If no payment has succeeded after 14 days, the organization moves to the Free plan, with the same rules as choosing a smaller plan.

Paying at any point during those 14 days ends the matter. Nothing is deleted before the organization moves to Free.

Refunds

Payments are for the month ahead and are not refunded for a month already started. If you were charged by mistake, or something on our side went wrong, write to us and a person will look at it. See Support.

If prices change

A price change does not apply to a period you already paid for. Owners are told by e-mail at least 30 days before a new price applies to their organization.

What is never charged

  • Self-hosting the engine.
  • The Free plan.
  • Going over a limit.
  • Members who only read: a seat is included in the plan up to its number of people, and there is no charge for each person.
  • Alerts, the daily summary, the prompt and the MCP server.
  • Each pull request. On the Builder and Team plans a number of them is included in the price, and asking for more is refused, not billed.

Example: the shop moves to Builder

The shop starts on Free. On 29 March it reaches the month’s events, and the owner moves to Builder that day. She enters a card and is charged USD 10. Collection resumes within minutes, with Builder’s events for what is left of March, and again for April from the 1st: usage is counted by calendar month, while the bill comes on the 29th of each month.

In July the shop closes for the summer. The owner cancels on 10 July. The plan stays Builder until 29 July, then becomes Free: data older than the Free plan keeps is deleted that day, Sypnia opens no more pull requests, and the app said so before she confirmed.

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