Appearance
Editions
Replora comes in two editions built from the same application. Single user is self-hosted for you and the people you invite. SaaS adds everything you need to sell Replora as a service: a public website, sign-up, plans with limits and payments. Recording, replays and every report are the same in both.
At a glance
| Single user | SaaS | |
|---|---|---|
| What it is | Self-hosted for one owner and their team | A hosted service you sell to customers |
| Package | replora-single-<version>.zip | replora-saas-<version>.zip |
| License | A Single site purchase code | A purchase code of the SaaS plan (Single site codes are refused) |
| Who gets an account | Administrators add users and invite team members | Anyone can sign up (switch off with REPLORA_SIGNUP=false for an invitation-only launch) |
| Plans and limits | No plans; no limits (installation defaults are unlimited) | Plans with limits per account: websites, sessions and replays per month, retention, features |
| Payments | No | Subscriptions through Stripe or Paddle (BILLING_PROVIDER) |
| Public website | No (only the dashboard and its sign-in page) | Home, feature pages with demos, pricing, contact and your own pages (terms, privacy…) in every language |
| Affiliate program | No | Referral links, commission, monthly payouts |
| Support desk | No | Customers open tickets; your team answers with departments, saved replies and response-time targets |
| Recordings, heatmaps, funnels, forms, surveys, A/B tests, errors, events, alerts, insights, AI | (per plan) | |
| Team roles, API tokens, webhooks, HubSpot | ||
| Administration: overview, users, System, translations, announcements, help center | ||
| 13 interface languages |
How the edition is chosen
Both editions are the same code. Everything SaaS-only lives in one folder, saas/ (its modules Affiliates, BillingPaddle, BillingStripe, Landing, Pages, Plans, Signup and Tickets, plus the dashboard pages that belong to them). One line in .env picks the edition:
ini
REPLORA_MODE=single # or saassaas/ folder | REPLORA_MODE | The site runs as |
|---|---|---|
| missing (Single user package) | anything | Single user: it can never run as SaaS |
| present (SaaS package) | single | Single user: private, no sign-up or billing |
| present (SaaS package) | saas | SaaS |
- The Single user package doesn't contain
saas/at all. - With the SaaS package the installer's last step asks which edition you want (Single user or SaaS);
php artisan replora:install --mode=saasdoes the same on the command line. - If
.envsayssaasbut the folder is missing, the site runs as Single user andphp artisan replora:doctorwarns: REPLORA_MODE=saas but the saas/ folder is missing: running as Single user.
The edition is shown on Administration › System under This installation.
Switching later
- Edit
REPLORA_MODEin.env(singleorsaas). - If you cache configuration (
php artisan config:cache), runphp artisan config:clear(or cache it again). - Reload the dashboard.
Data of the other edition (plans, subscriptions, sign-ups, tickets) stays in the database untouched, so switching back brings it back. Deleting the saas/ folder is enough to turn the SaaS edition off for good.
Updating a SaaS site
Always update a SaaS site with the SaaS package (one-click updates do this for you). Uploading the Single user package's files would leave the saas/ folder out and the site would run as Single user.
Which license do I need?
Each edition needs a purchase code of its own plan. The SaaS edition's installer checks the code's plan: a Single site code is refused with This purchase code is for Replora Single site. These are the files of the SaaS edition, which needs a SaaS license. See Your purchase code.
