Docs

Concepts

The ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.

Applies to EngineCloud At launch

View as Markdown

This section defines how Sypnia behaves. Read it when you want to know exactly what a word means or what a number counts: what starts a session, what makes two failures the same problem, what a rage click is, when an alert is sent.

Every page applies to the open-source engine and to Sypnia Cloud, and says where they differ. The examples all come from one small shop with a checkout.

  • Projects, environments, keys and tokens

    Where data belongs and what each key can do.
  • Events

    What your app reports, and which events count towards a plan.
  • Sessions and replay

    What starts and ends a session, and what a replay records.
  • Problems

    What makes failures one problem, and when it is new, growing, resolved or back.
  • Traces

    One request followed from the browser to your API and the calls behind it.
  • Performance

    Page speed and API speed, how percentiles are shown, and the element behind each number.
  • Rage and dead clicks

    The exact rules for both, and what does not count.
  • Uptime

    What a check does, when your app counts as down, and when you are told.
  • Releases and source maps

    How Sypnia knows which change broke it, and shows your real code.
  • Alerts and the daily summary

    What triggers an alert, what it contains, and what waits for the morning.

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