Self-hosting
Replayly is built to run on infrastructure you control. Self-hosting is a first-class path, not an enterprise footnote, and it sits beside a hosted workspace if you would rather not operate a VPS.
What you run
A typical self-hosted install is Docker Compose, the Replayly web app, Postgres, and object storage for recording assets. An optional Caddy reverse proxy terminates HTTPS. The self-host documentation covers migrations, environment variables, and how to keep the tracker origin aligned with your public URL.
You choose the region and the buckets. That is the point: recordings do not have to live in a vendor region you cannot name. Hosted Replayly workspaces remain available when you want the same product without operating the database.
What you still have to operate
Self-hosting is not a free lunch. You are responsible for updates, backups, disk, SMTP, and access control on your server. The app can send transactional mail through your own domain SMTP. Billing integrations such as Paddle or Stripe are documented if you sell access to workspaces you operate.
If you want an open-source project with a different scope, OpenReplay is an honest alternative to compare. If you want a full product-analytics platform that also self-hosts, look at PostHog. Replayly stays smaller: session replay, heatmaps, privacy defaults, and the admin surface around them.
Privacy and residency
Putting the stack on your VPS does not remove the need for input masking, consent, or a privacy policy. It does give you a concrete answer to 'where is this data?' that many hosted tools cannot match. Combine self-hosting with the default privacy controls rather than treating infrastructure as a substitute for masking.
Teams in regulated industries often pick self-hosting for residency and procurement reasons. Replayly does not invent certifications this page cannot show. Ask for the current fact sheet and legal pages, and have your own counsel review them.
Get started
Follow the self-host install guide, set SITE_URL to your public HTTPS origin, and confirm that /robots.txt and /sitemap.xml use that origin — not localhost. Then install the tracker on a staging site and record a test session before you touch production traffic.
If you would rather try the product first, create a hosted workspace, use the free plan, and decide later whether to move the same workflow onto your VPS.
See all Replayly features, compare plans on the pricing page, or read Replayly vs OpenReplay. Ready to try it? Create a workspace or follow the install guide.