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.
ApiError: POST /api/checkout failed
with 400 (amount_required)
at createPayment (api.ts:27:11)
at async confirmPayment (checkout.tsx:142:18)
at async onClick (pay-button.tsx:18: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
events 9 users 3
breadcrumbs
10:31:28.412 navigation /checkout
10:31:43.104 ui.click button#pay
10:31:45.310 ui.click button#pay
10:31:45.502 ui.click button#pay
10:31:45.811 ui.click button#pay
10:31:46.003 ui.click button#pay
10:31:46.974 fetch POST /api/checkout 400
10:31:46.981 exception ApiError
10:31:58.020 navigation /cart
sessions
10:31 u_1042 POST /api/checkout 400
09:47 u_0977 POST /api/checkout 400
09:11 anonymous POST /api/checkout 400and 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 release 4f2a91c (yesterday 18:40). Where: src/checkout/checkout.tsx:142, confirmPayment() Why: that release 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: session 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 session, as a timeline of events, itself.
On Builder and Team, connect GitHub, turn pull requests on for the project, 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 by e-mail and in the app when it cannot wait, and one short e-mail 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 within about two minutes when 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 light SDKs for the web, Node and Next.js. For any other backend, an open door: if your services 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: process.env.SYPNIA_PROJECT_KEY }); // requests, outgoing calls, database queries and errors are traced
OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.sypnia.com/v1/otlp OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer%20YOUR_PROJECT_KEY OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf # opentelemetry-instrument python app.py
OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.sypnia.com/v1/otlp OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer%20YOUR_PROJECT_KEY OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf # any OpenTelemetry SDK: traces go to Sypnia
One project key everywhere: our SDKs, or any OpenTelemetry exporter.
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.
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, the analysis, the prompt and the MCP server.
| 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. Clicks and page views are free; in all, up to four times the plan’s events are received. | 5,000 | 50,000 | 500,000 | |
| Replays a month | 50 | 500 | 5,000 | |
| Longest recording | 30 minutes | 2 hours | 2 hours | |
| Data kept for | 7 days | 30 days | 90 days | |
| Replays kept for | 7 days | 30 days | 30 days | |
| People on the account | 1 | 3 | 10 | |
| Uptime checks | 1 | 5 | 25 | |
| AI analyses a month | With your own model key | 50, at most 10 a day | 200 | 1,000 |
| Pull requests Sypnia opens a month | Not in the engine | Not included | 5 | 30 |
| Alert e-mails a month | Not in the engine: a webhook | 100 | 1,000 | 5,000 |
| The prompt and the MCP server | 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
Team grows with you, on the same monthly bill: extra seat $3 extra project $2 +100,000 events $5 +500 replays $5 +100 analyses $3 +10 pull requests $15 +10 uptime checks $1 +2,000 alert e-mails $1 +90 days of data $2. Each a month. Free and Builder grow by moving up a plan.
Prices in US dollars. Self-hosting is always free.
Start freeIs your question missing? Write to us and a person will answer. support@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, on paid plans, 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 Amazon Web Services in the United States (us-east-1), used only 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. What people type is always masked, and you can mask or leave out 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, on Builder and Team, once you turn them on for a project.
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