Appearance
Introduction
Replora records what visitors do on your websites and lets you watch it back: every page, scroll, click and typed field (masked), in a replay that looks like the real page. Around the recordings it builds heatmaps, funnels, form analytics, error reports, on-site surveys and A/B tests. It runs on your own server, so the recordings never leave it.
What it does
Session recordingsReplays of real visits with the console, network requests, page list, AI summary, notes, tags and share links. Live visitors as they browse.
HeatmapsClick, movement and scroll heatmaps drawn on the real page, and a ranking of the elements people click.
FunnelsOrdered steps (pages, session tags) with conversion and drop-off per step, and the sessions behind every number.
Form analyticsForms started and submitted, time and hesitation per field, blank and corrected fields, where people gave up. Never what was typed.
SurveysNPS, ratings, choices and free text shown to targeted visitors, each answer linked to its replay.
A/B testsPage variants (text, hidden elements, styles, another URL) shown by the tracker, with conversion, lift and confidence.
Errors & eventsJavaScript errors grouped by cause with their sessions; custom events your site sends.
Alerts & insightsEmail, Slack or webhook alerts on errors, rage clicks or pages; frustration insights and common journeys.
AI (Claude)Session summaries, site digests, Ask AI and plain-words search, with your own Anthropic API key.
The parts of an installation
| Part | What it is |
|---|---|
| Dashboard | The web app where you add websites, watch replays and use every report. Administrators also manage users, settings, updates and (SaaS) plans and billing. It is served from your domain, for example https://analytics.example.com. |
| Tracking script | t.js, served by your Replora installation. You paste a short snippet into the websites you want to record; it sends compressed event batches to /i/<site key>. |
| Background worker | php artisan queue:work: processes the recording batches, sends alerts and announcements. See Background worker & email. |
| Scheduler | One cron line (php artisan schedule:run) that deletes expired recordings, checks for updates and services, sends digests and reminders. See Scheduler. |
| Database | PostgreSQL: accounts, websites, sessions and every report. |
| Recording storage | The recorded events themselves: on the server's disk (storage/app/recordings) or in S3, Cloudflare R2 or MinIO. See Recording storage. |
| REST API | Everything the dashboard does, under /api/v1, for scripts, other apps and the mobile app. See REST API. |
| Public website (SaaS) | Home, feature pages, pricing, sign-up and your own pages, for selling Replora as a service. |
How this documentation is organised
Getting started & installationPick an edition, check the server, install, start the worker and cron, choose storage, update, back up and scale.OpenAdministrationFor administrators: overview, users, the System page, service status, settings, email, AI, branding and languages.OpenSaaS businessPlans and limits, Stripe and Paddle, sign-up, the public website, affiliates and the support desk.OpenDevelopersThe tracking script, JavaScript API, privacy attributes, single-page apps, webhooks and modules.OpenREST APIAuthentication, tokens and every endpoint, generated from the OpenAPI description.OpenReferenceEvery .env key, every command, plan limits, the FAQ and the changelog.Open
Using the dashboard
How to watch replays, read heatmaps, build funnels and surveys is in the separate User Guide. These docs are for whoever installs and runs Replora.
Names in commands
Package files (replora-single-1.0.0.zip), commands (php artisan replora:install) and .env keys (REPLORA_MODE) all carry the Replora name. Type them exactly as shown.
