You shipped
it with AI.
Is it actually
working?

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.

A customer clicks Pay Checkout page POST /api/checkout createPayment() 400 A customer clicks Pay POST /api/checkout createPayment() 400
New problem2 min agoExample

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.

3 people affectedWatch what they sawTrace across 3 services
Open pull requestCopy prompt for your agent
  • Open sourceEngine in Rust, built in the open.
  • Free to self-hostOne template. Your data stays yours.
  • Cloud from $10 a monthWith a free tier to start.
  • Web, iOS, Android, backendOur SDKs, plus OpenTelemetry.

It speaks human.

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.

What your app says
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  PaymentError
and 212 more lines
What Sypnia says Example

3 people tried to pay today and could not. The Pay button does nothing since yesterday’s change.

Who it hit
3 people. Two of them tried again and gave up.
What they were doing
Paying for an order, at the last step of checkout.
Since when
Yesterday’s change, deployed at 18:40. It worked before.
What to do
The checkout still reads the cart’s old field name. Point it at the new one. The fix is ready as a pull request.

It hands the fix to the agent that wrote the code.

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.

  • A prompt, ready to paste

    What happened, where, why, and how to check the fix, written for Cursor, Claude Code or whichever agent you use.

    Prompt for your coding agentExample
    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.
  • An MCP server your agent can ask

    Connect Sypnia once. From then on your agent can ask what is failing in production and read the trace and the replay itself.

    Your coding agent, connected to SypniaExample
    You
    what is failing in production?
    Agent
    sypnia.problems({ status: "open" })
    1 open problem since yesterday’s deploy: 3 people tried to pay and could not. The checkout sends the payment without an amount. I have the trace and the replay. Want me to fix it?
    You
    yes, and add a test
    Agent
    sypnia.problem("pay-button-does-nothing").context()
    Editing src/checkout/checkout.tsx
  • A pull request with the fix

    Connect GitHub and Sypnia opens the pull request for you. You read it, you merge it. Nothing ships without you.

    Read the cart total from its new field
    sypnia/pay-button-does-nothingintomainopened by Sypnia, 2 minutes agoExample
    async function confirmPayment(cart) {
    - const payment = await createPayment({ amount: cart.total });
    + const payment = await createPayment({ amount: cart.totalCents });
    + if (!payment.ok) return showPayError(payment);
    return payment;
    }
    Tests passFixes the problem 3 people hit todayReview pull request

Everything it watches, so you can stop watching.

Seven things tell you whether your software and the people using it are well. Sypnia covers them all from one install.

Session replay

See the session as the person lived it: every click, scroll and error, with the moment it broke already marked.

One of the 3 sessionsExample
  1. 0:12Opened checkout
  2. 0:27Clicked Pay
  3. 0:29Clicked Pay 4 more timesRage click
  4. 0:31Payment rejected: no amount
  5. 0:42Left the page
0:31 / 0:421x

Alerts and a daily summary

An alert when it cannot wait, and one short message a day for everything else.

Daily summaryExample

Good morning. Here is yesterday.

  • 1 new problem: 3 people tried to pay and could not, since yesterday’s change. A pull request is waiting for you.
  • The search page got slower: 3.1 seconds to load, it was 1.9.
  • Your app answered all day. 412 people used it.
  • Errors, grouped

    The same failure is one problem, not four hundred emails. Each comes with who it hit, where, and the deploy that caused it.

  • Performance

    Which pages load slowly for real people, and which API calls are slow or failing.

  • Uptime

    Sypnia checks from outside that your app answers, and tells you the minute it stops.

  • Rage and dead clicks

    Where people click again and again, and the things they click that do nothing.

  • End-to-end traces

    One request followed across your frontend, your API and the services behind it.

It works with what you already built.

Our own SDKs for the web, mobile and the backend. And an open door: if your services already speak OpenTelemetry, point them at Sypnia.

  • WebJavaScript, TypeScript
  • iOSSwift
  • AndroidKotlin
  • Node.js
  • Python
  • PHP
  • Go
  • Rust
  • OpenTelemetryOTLP in

One snippet to install

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.

Open source. Run it yourself, or let us.

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.

Self-host, for free

Deploy the whole engine on your own infrastructure with one template. Your data never leaves your account.

  • The full engine: ingest, storage and analysis
  • One template to deploy
  • Free, with no limits set by us

The engine's repository opens at launch.

Sypnia Cloud

If you would rather not run servers, we run it for you. Start on the free tier; paid plans begin at $10 a month.

  • Nothing to deploy or maintain
  • A free tier to start
  • The same engine you can read

Start free

Free to start. From $10 a month when you grow.

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.

Plans compared
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.1310
Events a monthAn event is an error, a trace or a performance sample. 5,00050,000500,000
Replays a month 505005,000
Data kept for 7 days30 days90 days
People on the account 1310
Uptime checks 1525
Pull requests Sypnia opens a month 550300
Prompt, MCP server and GitHubIncludedIncludedIncludedIncluded
SupportCommunityCommunityEmailPriority email

Self-hostedFree

On your own infrastructure

Projects
No limits set by us
Events a month
No limits set by us
Replays a month
No limits set by us
Data kept for
No limits set by us
People on the account
No limits set by us
Uptime checks
No limits set by us
Pull requests Sypnia opens a month
No limits set by us
Prompt, MCP server and GitHub
Included
Support
Community

FreeFree

To try it on a real project

Projects
1
Events a month
5,000
Replays a month
50
Data kept for
7 days
People on the account
1
Uptime checks
1
Pull requests Sypnia opens a month
5
Prompt, MCP server and GitHub
Included
Support
Community

Builder$10 a month

For an app with real users

Projects
3
Events a month
50,000
Replays a month
500
Data kept for
30 days
People on the account
3
Uptime checks
5
Pull requests Sypnia opens a month
50
Prompt, MCP server and GitHub
Included
Support
Email

Team$49 a month

For several apps and people

Projects
10
Events a month
500,000
Replays a month
5,000
Data kept for
90 days
People on the account
10
Uptime checks
25
Pull requests Sypnia opens a month
300
Prompt, MCP server and GitHub
Included
Support
Priority email

Prices in US dollars. Self-hosting is always free.

Start free

Honest answers.

Is your question missing? Write to us and a person will answer. hello@sypnia.com

How do I start?

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.

What does it watch?

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.

How is it different from Sentry, Datadog or PostHog?

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.

Where does my data live?

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.

What does session replay record?

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.

Which AI tools does it work with?

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.

What does it cost?

Self-hosting is free. Sypnia Cloud has a free tier and paid plans from $10 a month.

Is it really open source?

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.

Sleep. We keep one eye open.

Three steps, and Sypnia is watching your app.

  1. Create a project

    Open a free account and name your app.

  2. Paste the snippet

    One snippet in your app, or point your OpenTelemetry exporter at Sypnia.

  3. See your first session

    Open your app. Its first session appears in Sypnia, and the first problem arrives in plain words.