Docs

Sypnia Cloud

How the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.

Applies to Cloud At launch

View as Markdown

Cloud Everything in this section is about Sypnia Cloud, the paid service with a free tier. None of it exists in the open-source engine, which has no users, no organizations and no billing.

Sypnia Cloud is not a different product. It is our deployment of the same engine, plus a private part that the engine does not have: accounts, organizations, plans and billing, the full app, e-mail alerts and the Sypnia GitHub App. What the two share and where they differ is in Open source and Sypnia Cloud.

  • Organizations and teams

    Accounts, organizations, the three roles and what each can do.
  • Plans and limits

    What each plan includes, how each limit is counted, and what happens when one is reached.
  • Billing

    How you pay, what changing or cancelling a plan does, and what a failed payment does.
  • Data location and retention

    Where your data is stored, who else touches it, and how long each kind is kept.
  • The GitHub App

    What the app may do in your repository, what it never does, and how to remove it.
  • Support

    How to reach us on each plan, and what to send.

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