Prynt Replay Available

See why your users get stuck

Watch the session behind every bug report and every lost sale. Py, Prynt's AI, watches them for you and tells you what broke.

Free plan, then from $279 / month · 14-day free trial

How it works

From “it doesn’t work” to fixed

  1. 1

    Record

    Every session, with form fields masked twice.

  2. 2

    Py finds the problem

    Every morning, before you ask. And in Claude or Cursor.

  3. 3

    Fix it

    Jump to the exact second, or send it to Jira or Linear.

Sound familiar?

The problems Replay ends

  • The problem

    “It doesn’t work.” And nobody can reproduce it.

    With Replay

    Open the session at the second it broke.

    • JS error
    • Failed request
    • Console
    • Who it was
  • The problem

    People leave checkout and you don’t know why.

    With Replay

    See the button nobody can click.

    • Rage clicks
    • Dead clicks
    • Heatmaps
    • Frustration score
  • The problem

    A deploy breaks something. You find out a week later.

    With Replay

    Get an alert the moment a new issue appears.

    • Issue alerts
    • Lost sales
    • Jira / Linear
  • The problem

    No time to watch hundreds of recordings.

    With Replay

    Ask Py and watch only the 3 that matter.

    • Summaries
    • Key moments
    • Ask Py
Py · Prynt AI

Meet Py, the AI that watches sessions for you

Prynt's AI reads every session so you don't have to.

  • Sums up each session in a few lines.
  • Takes you straight to the key moments.
  • Answers questions about all your sessions.

Py never sees form values, page text, IPs or emails.

Py · session #4182

Tried to pay 3 times. The payment failed every time.

  • Clicked “Pay” 3 times in 2 seconds after a 502.
  • Left 40 seconds later without buying.
Key moments
  1. 0:42Arrives at /checkout
  2. 1:15POST /api/pay → 502
  3. 1:17Rage click on “Pay”
Next step

Check the payment gateway. 23 more sessions hit this.

Ask Py

Which sessions had checkout errors this week?

24 sessions, 21 on mobile Safari. Start with #4182, #4177 and #4160.

Example with fictional data.
Prynt Replay

Capabilities

  • Session recording

    Loaded on demand. Multi-page visits and single-page apps.

  • Py, Prynt’s AI

    Session summaries and Ask Py over 100 recent sessions. 1,000 requests a month.

  • Py’s daily brief

    Every morning Py tells you what broke and where people struggled. Email and Slack.

  • Py in Claude and Cursor

    MCP server: ask about sessions and issues from your AI assistant.

  • iOS and Android apps

    Native, React Native and Flutter. Fields masked on the device.

  • Issue impact and alerts

    Issues ranked by sessions, users and lost conversions. Alerts when one is new or comes back.

  • Masking and privacy

    Forms always masked, twice. Mask or block elements, URL rules, sampling and consent per site.

  • Player

    Errors and clicks marked on the timeline, 1–8× speed, skip inactivity.

  • Who each session is

    User id, company (Reveal), IP, location and VPN or bot flags (Identify).

  • Filters

    By page, country, device, errors, rage clicks, frustration, user or visitorId.

  • Heatmaps

    Where people click and how far they scroll, per page and device.

  • Errors and failed requests

    Grouped; each opens the replay 2 seconds before it happened.

  • Frustration

    Rage, dead and error clicks by element, and a 0–100 score per session.

  • Developer tools

    Optional: console, every request and app state. Never bodies or headers.

  • Tickets and helpdesk

    Jira and Linear tickets from the player or Automate. Helpdesk lookup API.

  • Retention and deletion

    14 to 90 days by plan, more on Enterprise. Delete by recording, visitor or user (GDPR).

  • Linked to Identify and Reveal

    Open the replay from any visitor or company profile.

  • Page performance

    Core Web Vitals per page and session, slowest pages first.

  • Feedback widget

    CSAT or NPS plus a comment, each opening the replay of that moment.

  • Share and comment

    A link to the exact moment, notes on the timeline, saved filters.

  • Sentry, Zendesk, Intercom

    Replay links in Sentry errors, sessions next to every ticket.

  • In your own admin

    Your team sees a customer’s sessions by company or user inside your back office.

  • Export

    CSV or NDJSON for your warehouse; raw masked events by API.

  • Bots are free

    Crawlers and automated browsers are never recorded nor billed.

Page text outside forms is recorded unless you mask it. Console and requests only if you turn on developer tools.

Prynt Replay

Pricing

Start free with 1,000 sessions a month. Pro plans go from 10,000 to 1,000,000 sessions, each a little under LogRocket Pro at the same volume, with Py included.

Prynt Replay from $279 / month 14-day free trial
Plan limits
  • 10,000 recorded sessions / month
  • 1,000 Py requests / month
  • 30 days of retention
  • 3 sites

Billed monthly through Stripe, on your Prynt account. All plans on the pricing page

Plans by volume

Sessions / monthPricePy requestsRetentionSites
1,000Free $0 / month 25 14 days 1
10,000 $279 / month 1,000 30 days 3
25,000 $389 / month 2,000 30 days 5
50,000 $579 / month 3,000 30 days 10
100,000 $689 / month 5,000 60 days 10
250,000 $969 / month 8,000 90 days 25
500,000 $1,379 / month 12,000 90 days 25
1,000,000 $2,179 / month 20,000 90 days 50

Every plan includes Py, heatmaps, errors and failed requests, issue alerts, developer tools and Jira / Linear tickets. Paid plans start with a 14-day trial; if one ends, Replay keeps recording on Free.

Start free →
Platform

How it connects to the platform

Same snippet, account and consent rules as the rest of Prynt. That is why a replay knows who the visitor is, and if it was a bot.

How the platform connects
  • One snippet: Prynt.replay() loads on demand.
  • Identify and Reveal tell you who each session is.
  • Same account, team, billing and consent.
FAQ

Frequently asked questions

Is Prynt Replay available?

Yes. Free up to 1,000 sessions a month; Pro from $279 a month with a 14-day free trial.

What is Py?

Prynt's AI. It sums up each session and answers questions about your sessions, citing the recordings. Included, up to 1,000 requests a month.

What does Py see?

Only structured facts: page paths, clicked elements, errors, duration, device and country. Never page text, form values, IPs, emails or user ids.

Do bots count toward my sessions?

No. Crawlers and automated browsers are refused before recording; if Identify later flags a session as a bot, it is given back.

Does it work on mobile apps?

Yes: iOS, Android, React Native and Flutter. Text fields are masked on the device, before a frame leaves it.

Can my team watch sessions inside our own admin?

Yes. Tag sessions with your user and company ids, list them from your backend with the API and play them in an iframe with a link that expires in minutes. Guide: pryntid.com/docs/replay/embed.

How is it different from other session replay tools?

It knows who the visitor is (Identify and Reveal), masks forms twice with no way to unmask, and every plan includes Py, starting free; Pro costs a little less than LogRocket Pro at the same volume.

What does each plan include?

Free: 1,000 sessions a month, 25 Py requests, 14 days of retention, 1 site. Pro: from 10,000 to 1,000,000 sessions, every feature, Py from 1,000 requests a month, 30 to 90 days of retention.

What is never recorded?

Form values, elements you mark, excluded pages, request bodies and headers, and visitors without consent or with Global Privacy Control.

What happens when I reach my sessions?

New sessions stop recording until next month, or move up a volume from the console. No surprise charges. If a paid plan ends, Replay keeps recording on Free.

How heavy is it?

About 0.5 kB on every page; the 29 kB recorder loads only where you call Prynt.replay().

See why your users get stuck

Start free with 1,000 sessions a month. Pro from $279 a month when you need more.