Skip to main content
Replayfy records what your users actually do — pixel-accurate session replays, taps and clicks, screen navigation, network activity, console logs, crashes, and performance vitals — then turns it into funnels, cohorts, crash reports, and AI answers so you can see how your product is really used and fix what’s broken. Drop in one SDK per platform and you’re recording in under two minutes. These docs are the complete how-to for the whole platform — from your first session to funnels, crash triage, alerts, and Replayfy AI.

Quickstart

Install an SDK and watch your first real session in under two minutes.

What's in Replayfy

Replay, analytics, crash monitoring, alerts, and Replayfy AI — one platform.

The platform

Everything below shares the same recordings and events, so a session you watch is the same session that powers a funnel, a cohort, a crash report, and an AI answer.

Session Replay

Watch pixel-accurate replays of real web and mobile sessions.

Product Analytics

Events, segments, and retention from your identified users.

Analytics

Build metric trends, retention grids, breakdowns, and Core Web Vitals.

Funnels

Measure conversion, timing, and drop-off across ordered steps.

Cohorts

Living groups of users, built from traits or behavior.

Crashlytics

Crashes, exceptions, and ANRs — with the replay attached.

Alerts

Get an email when conversion drops or an issue spikes.

Replayfy AI

Ask questions in plain language — grounded in your real data.

Integrations

Connect your issue tracker, chat, and incident tools.

Install an SDK

One SDK per platform, apiKey + apiHost, and you’re recording.

Web

iOS

Android

React Native

Flutter

All SDKs

Make the data yours

Recording is automatic. These three guides connect sessions to real people and events, and keep sensitive data off the wire.

Identify users

Track events

Privacy & masking

How it works

Each SDK captures on-device, batches efficiently, and streams to your Replayfy ingest host. Recording, tap capture, screen detection, crash handling, and performance monitoring all begin from a single init / start call — no manual wiring. Settings you configure in the dashboard are fetched at startup and take precedence over the values passed in code, so you can tune masking, sampling, or pause recording without shipping a new build.

Get help

Community & support

Reach the team, report a security issue, or join the community.

Open the dashboard

Sign in to watch sessions and manage your workspace.

Contribute to docs

These docs are open — suggest an edit on GitHub.