Introducing Replayly

We built Replayly as a privacy-first session replay platform: a Microsoft Clarity-style way to watch real user sessions, with input masking and Do Not Track on from the first snippet. It records how people use a website so a product or support team can watch the visit, find friction, and fix it. You can create a hosted workspace and start on the Free plan.

This post is the product introduction. The fact sheet is the source of truth for plans, prices, and limits. Nothing here invents customer counts, reviews, or a promise of a #1 Google ranking.

What is Replayly, and what problem does it solve?

A tracker on your site captures an event stream of the page, and a player in the dashboard reconstructs the visit. The problem it solves is a simple one that screenshots miss. A customer says checkout is broken, or a campaign page is "confusing," and you cannot see the path they actually took. Watching the session, with sensitive fields already masked, shortens that guesswork.

The tracker uses rrweb. A recording is not a camera video or a screen-share file. It is a stream of DOM events, which is why masking can be applied before data leaves the browser. The session replay feature page describes the player: speed controls, skip inactivity, a metadata panel, and markers such as rage clicks or console errors.

We are a small team based in Pakistan, as the about page states. That is the business location. It is not a claim of a US headquarters, a large research department, or a panel of outside legal experts.

What do you get on day one?

A single script tag, conservative privacy defaults, and a dashboard that can play sessions. After you create a project, you paste a snippet such as:

<script src="https://your-replayly-host/t.js?pid=PROJECT_PUBLIC_KEY" async></script>

The project id is read from the script URL. Events go to /api/ingest on the same origin. Use Verify installation on the project page after you deploy the snippet. If you prefer a tag manager, we also document a Google Tag Manager path. Those are the integrations that exist today. We are not going to invent a WordPress or Shopify plugin that is not in the catalog.

Privacy starts on. Input values are masked. Do Not Track is respected unless you explicitly opt out with dnt=0 on a test page. The longer explanation is in Privacy defaults, not privacy settings and the privacy controls guide.

On the Free plan you can watch sessions on a single project, with 1,000 sessions per month and 7-day retention. If you go over the monthly limit, Free samples further visits rather than blocking immediately. That is enough to validate the workflow. It is not an unlimited recording tier.

How is Replayly priced, and what sits on each plan?

Four monthly USD list plans, taken from the same catalog the product uses to bill and enforce quotas. The current numbers, also printed on pricing and facts as of 13 November 2026, are:

Every plan includes session replay with input masking on. Heatmaps are not included on Free or Starter. They start on Pro, and they are generated from the same recordings rather than from a second tracker. Session filters (device, browser, operating system, country, rage clicks, dead clicks, console errors) start on Starter.

We are not a free-unlimited Microsoft Clarity clone. Clarity, per its official pricing page checked on 13 November 2026, is free forever and includes heatmaps. If that is what you need, stay on Clarity. Pay for Replayly when you want these defaults, a public paid catalog, longer retention, or filters and heatmaps on the published plans.

Who is Replayly for?

Product and UX teams who need to watch real visits. Agencies who need to show a client what happened, with fields already masked. SaaS teams debugging their own product UI. Privacy-conscious teams who will not turn a recorder on unless the defaults are conservative.

Those jobs are spelled out on the use-case pages. The product is a poor fit if you need surveys and feedback widgets (look at Hotjar or a similar UX suite), a full product-analytics platform with feature flags (look at PostHog), or front-end monitoring bundled with replay (look at LogRocket). Compare us on replay, privacy, and price, not on a feature list we do not have.

If you are leaving a free tool, start with Best Microsoft Clarity alternatives in 2026. If you are leaving a UX suite, start with Best Hotjar alternatives. Both posts are written to say when you should not switch.

What does Replayly not try to be?

We do not try to be a complete digital experience platform, a survey product, or an error-monitoring suite. We also do not try to match Microsoft Clarity on "free and unlimited heatmaps." Those are deliberate limits. They are not temporary gaps this post should paper over.

If a team needs interviews and feedback widgets, they should keep a research tool for that work. If a team needs product analytics and feature flags, they should use a platform built for that. Replayly can sit next to those tools: watch the visit, with inputs already masked, and leave the rest of the stack alone. That narrower job is easier to price, easier to explain to a privacy reviewer, and easier to turn off if it is not helping.

How do you try Replayly without surprises?

Start on staging. Confirm masking. Only then touch production traffic.

1. Create a free workspace and a project.
2. Install the snippet from the install guide on a staging page that includes a form.
3. Submit test values and open the replay. The values should be masked.
4. Turn on consent mode and block selectors on Starter if your production site will need them.
5. Use Verify installation, then repeat on production.
6. When you have a bug report, filter (on Starter and above) for console errors or rage clicks instead of watching sessions at random.
7. Add heatmaps on Pro only after the recording workflow is already useful.

If something about plans, retention, or defaults changes, the changelog and a dated update on facts are the places that should move first. For questions, use the contact form. For the definition of the category itself, What is session replay? is the companion guide.

We will not promise that every site will rank first in Google, or that every team will prefer this to a free Microsoft product. We will keep the defaults on, keep the prices public, and keep the fact sheet honest. That is the product we are introducing here.

Sources

• Replayly facts, pricing, about, privacy controls, and install, checked 13 November 2026.
• Microsoft Clarity pricing, checked 13 November 2026, used only to be honest that Clarity is free.