What Sypnia is
What Sypnia watches, who it is for, how it differs from a dashboard, and what it does not do.
This page is for anyone deciding whether Sypnia fits their app. It applies to the open-source engine and to Sypnia Cloud; where they differ, the page says so.
Sypnia is an open-source observability platform for people who build software with AI. It watches your app in production. When something breaks, it tells you in plain words what happened, to whom and since when, and it hands the fix to the coding agent that wrote the code.
The example these docs use
Every page uses the same story, so the examples agree with each other. You run a small shop with a checkout. Yesterday at 18:40 you deployed a change that renamed the cart’s total from cart.total to cart.totalCents. The checkout still reads the old name, so the payment goes out without an amount and is rejected. Nothing on the screen tells the customer.
A stack trace or a log line would say something like POST /api/checkout 400. Sypnia says:
3 people tried to pay today and could not. The Pay button does nothing since yesterday’s change.
Then it says who it hit, what they were doing, since when, the likely cause with its evidence, and what to do. That sentence, and everything behind it, is called a problem.
What it watches
Sypnia covers the essentials from one install. All of them are available at launch.
| What | In one line | Read more |
|---|---|---|
| Errors, grouped | The same failure is one problem, not four hundred e-mails. | Problems |
| Session replay | The session as the person lived it, with the moment it broke marked. | Sessions and replay |
| Performance | Which pages load slowly for real people, and which API calls are slow or failing. | Performance |
| Rage and dead clicks | Where people click again and again, and the things they click that do nothing. | Rage and dead clicks |
| End-to-end traces | One request followed from the browser to your API and the calls behind it. | Traces |
| Uptime | A check from outside that your app answers. | Uptime |
| Alerts and a daily summary | An alert when it cannot wait, one short message a day for the rest. | Alerts and the daily summary |
Also available at launch, because the system Sypnia is extracted from already has them:
- Click maps: where people click on each page, with rage and dead clicks marked. See Rage and dead clicks.
- People and accounts: who is active, their sessions and when they were last seen. See Sessions and replay.
- Custom events and form failures: events your app names itself, and forms the browser refused to submit. See Events.
- Weekly suggestions: performance and experience improvements the agent proposes, each with its evidence. See How the analysis works.
What makes it different
It speaks human. A problem is told in one sentence, with the people it hit. The analysis behind that sentence is called the agent, and these docs explain what it reads and what it never reads in How the analysis works.
It closes the loop with your coding agent. Every problem comes ready for the agent that writes your code, three ways:
- A prompt you paste into Cursor, Claude Code or any agent that accepts text. See The prompt.
- An MCP server your agent can ask «what is failing in production?». See Connect.
- A pull request with the change and a test, opened by the Sypnia GitHub App. A person reviews and merges it. Cloud See Pull requests.
It is open. The engine that receives, stores and analyses your data is open source, and it accepts OpenTelemetry, so you can run it next to another tool or move later.
Who it is for
Sypnia is built first for people and small teams who ship with Lovable, Bolt, v0, Replit, Cursor or Claude Code, and who want to know whether what they shipped is working without learning to read dashboards.
It is narrower than Sentry, Datadog or PostHog on purpose. If your team already lives in dashboards and needs logs, custom metrics or hundreds of services, those tools do more. Sypnia tells you in a sentence what is wrong, for whom, and how to fix it.
What it works with at launch
- Web apps, with the browser SDK
@sypnia/browser, in any framework. See Browser. - Node and Next.js backends, with
@sypnia/nodeand@sypnia/next. See Node and Next.js. - Any other backend that speaks OpenTelemetry: point its OTLP/HTTP trace exporter at Sypnia. See OpenTelemetry.
- Mobile apps built as web views work with the browser SDK.
Native iOS and Android SDKs, and SDKs for Python, PHP, Go and Rust, are not available at launch. They are on the Planned page. Until then, those backends send traces through OpenTelemetry.
Open source and paid: the short version
| Sypnia engineOpen source, self-hosted | Sypnia CloudPaid service, with a free tier | |
|---|---|---|
| What it is | The open-source engine: one program you run on your own infrastructure. | The same engine, run by us, plus accounts, billing, the full app and the GitHub App. |
| How you read it | The HTTP API, the MCP server, the CLI and the Console (one built-in page: problems list and replay viewer). | The full app: replay player, performance, uptime, daily summary, search and teams. |
| The agent's analysis | Works with your own model key. Off until you set one. | Included. No key needed. |
| Pull requests | Not in the engine. Use the prompt or the MCP server with your own coding agent. | Opened by the Sypnia GitHub App. |
| Alerts | Recorded, and sent to a webhook if you set one. No e-mail sender in the default deployment. | By e-mail and inside the app, plus a daily summary by e-mail. |
| Cost | Free. No limits set by us. You pay for your own infrastructure. | A free tier, and paid plans from USD 10 a month (a proposal, see Plans and limits). |
The full table is in Open source and Sypnia Cloud.
What Sypnia does not do
- It does not collect logs, custom metrics or dashboards. Those are planned, not available.
- It does not merge code. A pull request waits for a person.
- It does not send alerts to WhatsApp or Slack. Sypnia Cloud alerts by e-mail and inside the app; the engine records alerts and calls a webhook.
- It is not a live dashboard. A new problem appears within 2 minutes of its first event, and counts and performance numbers are complete within 10 minutes. How it works has the timing of each part.
- It does not record what people type. Passwords, card numbers and one-time codes are never recorded, and you can mask any other area. See What is collected.
Next
- From a click in your app to a sentence in your inbox.
- The fastest way to see your first session.
- Run the engine yourself.