Skip to main content
Data residency controls where your captured session data is physically stored. By default, all accounts use the standard US region. Paid users can choose between US and EU storage. Enterprise customers add a third option: running RCLM entirely on your own infrastructure.

​
Available regions by plan

Region selection takes effect for all new session ingests immediately after you save your choice. A background migration moves your existing session history to the new region without interrupting your access.

​
Choosing your region (Paid)

1

Open your account profile

Select Settings from the top navigation and scroll to Data Residency.
2

Select your data residency region

Under Data residency, choose US or EU from the dropdown. Read the confirmation message before proceeding — region selection is currently treated as permanent in the UI.
3

Confirm your selection

Confirm the change. RCLM immediately routes all new session ingests to your chosen region’s storage and begins an asynchronous migration of your existing session history.
4

Monitor migration progress

The migration runs in the background. New sessions appear in the new region right away. Existing sessions migrate incrementally — they remain accessible throughout the process.
Region changes are currently permanent in the UI. RCLM prevents back-and-forth migrations to avoid data consistency issues. Choose your region carefully before confirming.

​
How regional routing works

Once you select a region, RCLM’s backend routes every relevant operation to that region’s storage:

New session ingests

All sessions captured after you set your region are written directly to your chosen region’s storage. No data touches any other region.

Existing session migration

RCLM automatically migrates your historical sessions to the new region in the background: copying them, verifying integrity, then removing the originals. The migration is resumable — if interrupted, it picks up where it left off.

Background services

Session summarization, statistics calculation, exports, and all other background jobs respect your region setting. Your data stays within your chosen region throughout its entire lifecycle.

Search and analytics

Hybrid search, semantic search, usage dashboards, and session filters all operate within your region. No cross-region data access occurs for normal product usage.

​
Enterprise: on-premises deployment

Enterprise customers can run RCLM entirely within their own infrastructure, keeping session data inside their network boundary.

Open-source server

The RCLM server (rclm-server) is open source. You can self-host it on any infrastructure you control today using Docker.

Packaged Helm deployment

A fully packaged Helm chart for Kubernetes-based on-premises deployment is coming soon. This will be the supported enterprise deployment path for VPC and air-gapped environments.

​
On-premises deployment options

Run rclm-server as a Docker container on your own infrastructure. This is the current self-hosted path. The server is open source and documented in the rclm-server repository.Point your capture tools (hooks, proxy, browser extension) at your self-hosted server by setting the API endpoint in your RCLM config. All session data stays within your infrastructure.
A packaged Helm chart is in development for teams that run Kubernetes in their VPC or on-premises data center. This will include:
  • Pre-configured deployment manifests
  • Integrated database and object storage configuration
  • Enterprise feature parity with the hosted product
  • Support for air-gapped environments
Contact [email protected] to discuss your deployment timeline and requirements.
If you are evaluating RCLM for a regulated environment (HIPAA, FedRAMP, SOC 2, or similar), reach out to [email protected] before self-hosting. The enterprise team can provide guidance on deployment architecture, data handling documentation, and compliance requirements.

​
Frequently asked questions

Yes. Paid users can change their region from the Data residency section on Settings. After confirming, RCLM routes new sessions to the EU immediately and migrates existing sessions in the background. The migration is resumable and does not interrupt normal product use.
Region changes are currently treated as permanent in the UI to prevent inconsistent back-and-forth migrations. If you need to change your region after an initial selection, contact support.
Migration time depends on how many sessions you have. For most users, the migration completes within minutes to a few hours. Large accounts with extensive session histories may take longer. New sessions land in the new region immediately regardless of migration progress.
No. Encryption and data residency are independent controls. You can enable encrypted session storage and choose a specific region independently. Encrypted session blobs are stored in your chosen region’s storage.
RCLM currently supports US and EU regions. Additional regions are on the roadmap, with priority determined by demand. Contact [email protected] if a specific region is a requirement for your deployment.