Where Does Self-Hosted OpenReplay Store Data?
Self-hosted OpenReplay keeps server config in /var/lib/openreplay with session data in Docker volumes.
Last updated
OpenReplay stores everything inside your own infrastructure. Configuration lives under /var/lib/openreplay on the host. Session data spreads across Docker volumes for Postgres, ClickHouse and object storage.
Small installs keep recordings on the instance. Larger ones point at S3-compatible buckets for recordings, assets, sourcemaps and spots. Uninstalling wipes the config dir, so export database dumps before removing anything.
Where OpenReplay stores this, by platform
/var/lib/openreplay (Docker volumes for data)
Host config plus Docker volumes for database and storage. Recordings default on-instance, movable to S3 buckets. Back up volumes before upgrades.
Frequently asked questions
How do I back up self-hosted OpenReplay?
Back up the database volume plus object storage buckets holding recordings. Config in /var/lib/openreplay travels with them. Dumps compress well, so check disk space before starting.
How do I move recordings to S3 storage?
Create the S3-compatible buckets first, then point the backend services at them. Recordings, assets, sourcemaps and spots each get their own bucket. Keep default on-instance storage for small trials.
Notice an outdated path? Let us know.