3 people tried to pay today and could not. The Pay button does nothing since yesterday’s change.
Yesterday’s change renamed the cart’s total. The checkout still asks for the old name, so the payment goes out without an amount and is rejected.
Sypnia watches your app in production. When something breaks, it tells you in plain words what happened and to whom, and hands the fix to your coding agent.
For people who build with Lovable, Bolt, v0, Replit, Cursor or Claude Code.
3 people tried to pay today and could not. The Pay button does nothing since yesterday’s change.
Yesterday’s change renamed the cart’s total. The checkout still asks for the old name, so the payment goes out without an amount and is rejected.
A stack trace tells you where the code stopped. Sypnia tells you who it hurt, what they were trying to do, and what to do about it.
PaymentError: amount is required
at createPayment (payments.ts:58:11)
at async confirmPayment (checkout.tsx:142:18)
at async onPay (PayButton.tsx:37:5)
at HTMLButtonElement.dispatch
(react-dom.production.js:3941:16)
request POST /api/checkout 400
amount undefined
release 4f2a91c, deployed yesterday 18:40
url /checkout?step=3
events 7 users 3
breadcrumbs
18:52:07.114 ui.click button#pay
18:52:07.131 fetch POST /api/checkout 400
18:52:07.133 exception PaymentError
18:52:09.203 ui.click button#pay
18:52:09.221 fetch POST /api/checkout 400
18:52:09.224 exception PaymentError
18:52:10.014 ui.click button#pay
18:52:10.377 ui.click button#pay
18:52:10.391 exception PaymentError
18:52:18.940 navigation /cart
18:54:41.262 ui.click button#pay
18:54:41.701 exception PaymentErrorand 212 more lines3 people tried to pay today and could not. The Pay button does nothing since yesterday’s change.
You did not write that checkout by hand, and you should not have to debug it by hand. Every problem comes ready for your coding agent, three ways.
What happened, where, why, and how to check the fix, written for Cursor, Claude Code or whichever agent you use.
Fix a production bug reported by Sypnia. What happens: clicking Pay does nothing. 3 people hit it today, since deploy 4f2a91c (yesterday 18:40). Where: src/checkout/checkout.tsx:142, confirmPayment() Why: that deploy renamed cart.total to cart.totalCents, but checkout.tsx still reads cart.total. The payment goes out with amount undefined and the API answers 400. Do: read cart.totalCents in confirmPayment(), and show the customer a message when a payment is rejected. Check: replay 8f3a shows the clicks. Add a test that fails when the amount is missing.
Connect Sypnia once. From then on your agent can ask what is failing in production and read the trace and the replay itself.
Connect GitHub and Sypnia opens the pull request for you. You read it, you merge it. Nothing ships without you.
Seven things tell you whether your software and the people using it are well. Sypnia covers them all from one install.
See the session as the person lived it: every click, scroll and error, with the moment it broke already marked.
An alert when it cannot wait, and one short message a day for everything else.
Good morning. Here is yesterday.
The same failure is one problem, not four hundred emails. Each comes with who it hit, where, and the deploy that caused it.
Which pages load slowly for real people, and which API calls are slow or failing.
Sypnia checks from outside that your app answers, and tells you the minute it stops.
Where people click again and again, and the things they click that do nothing.
One request followed across your frontend, your API and the services behind it.
Our own SDKs for the web, mobile and the backend. And an open door: if your services already speak OpenTelemetry, point them at Sypnia.
import { init } from '@sypnia/browser'; init({ project: 'YOUR_PROJECT_KEY' }); // errors, replay, performance and clicks are on by default
import { init } from '@sypnia/node'; init({ project: 'YOUR_PROJECT_KEY' }); // errors, replay, performance and clicks are on by default
import sypnia sypnia.init(project="YOUR_PROJECT_KEY") # errors, replay, performance and clicks are on by default
OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.sypnia.com OTEL_EXPORTER_OTLP_HEADERS="x-sypnia-project=YOUR_PROJECT_KEY" # OTLP
One project key, and the same call on every platform.
The engine that receives, stores and analyzes your data is open. Its core is written in Rust, so it is cheap to run and has room to grow.
Deploy the whole engine on your own infrastructure with one template. Your data never leaves your account.
The engine's repository opens at launch.
If you would rather not run servers, we run it for you. Start on the free tier; paid plans begin at $10 a month.
Self-hosting is free. On Sypnia Cloud you pay for how much you send, not for features: every plan has replay, traces and the agent loop.
| Self-hosted Free On your own infrastructure | Free Free To try it on a real project | Builder $10 a month For an app with real users | Team $49 a month For several apps and people | |
|---|---|---|---|---|
| Projects | No limits set by usProjects, events, replays, people and how long data is kept: as much as your own servers hold. | 1 | 3 | 10 |
| Events a monthAn event is an error, a trace or a performance sample. | 5,000 | 50,000 | 500,000 | |
| Replays a month | 50 | 500 | 5,000 | |
| Data kept for | 7 days | 30 days | 90 days | |
| People on the account | 1 | 3 | 10 | |
| Uptime checks | 1 | 5 | 25 | |
| Pull requests Sypnia opens a month | 5 | 50 | 300 | |
| Prompt, MCP server and GitHub | Included | Included | Included | Included |
| Support | Community | Community | Priority email |
On your own infrastructure
To try it on a real project
For an app with real users
For several apps and people
Prices in US dollars. Self-hosting is always free.
Start freeIs your question missing? Write to us and a person will answer. hello@sypnia.com
Create a project, paste one snippet into your app (or point your OpenTelemetry exporter at Sypnia) and open your app. Its first session shows up, and problems start arriving as sentences.
The essentials on this page: errors grouped with context, session replay, performance, uptime, rage and dead clicks, end-to-end traces, alerts and a daily summary, plus the loop with your coding agent (the prompt, the MCP server and GitHub pull requests). If it is not on this page, we are not promising it.
They are excellent and broad, built for engineering teams who are at home in dashboards. Sypnia is narrower on purpose: it is for people who ship with AI and want to be told in a sentence what is wrong, for whom, and how to fix it. It is open source and accepts OpenTelemetry, so you can run it next to another tool or move later.
If you self-host, on your own infrastructure and nowhere else. On Sypnia Cloud, on our servers, used to show you your own app and kept for as long as your plan says.
It rebuilds what the page looked like from its changes; it is not a camera on the person. You can mask what people type and any area you mark as sensitive.
The prompt works with any coding agent that accepts text. The MCP server works with agents that support MCP, such as Cursor and Claude Code. Pull requests go through GitHub.
Self-hosting is free. Sypnia Cloud has a free tier and paid plans from $10 a month.
The engine is: ingest, storage and analysis, with its Rust core. You can read it, run it yourself, and keep your data on your own servers.
Three steps, and Sypnia is watching your app.
Open a free account and name your app.
One snippet in your app, or point your OpenTelemetry exporter at Sypnia.
Open your app. Its first session appears in Sypnia, and the first problem arrives in plain words.
Sypnia is open source. If it helps you, help keep the light on.
Donate with PayPal