Your environment. Your control.

Your migration and modernization program should work within your security and operational requirements. RiverMeadow Private Deployment brings the Workload Mobility Platform into your own environment, so you can control where the platform runs while moving workloads to the destinations you choose.

Private Deployment has been part of RiverMeadow for years. What has changed is its relevance. Sovereignty requirements, VMware exits, and modernization across data centers and edge locations are making the deployment model an important part of migration planning.

The full platform in your environment

RiverMeadow Private Deployment runs in your data center, private cloud, or partner-operated environment. It brings discovery, planning, migration, validation, governance, and reporting together in one platform. Private Deployment delivers the same platform capabilities and workflow as RiverMeadow’s Hosted Solution, within an environment you control.

That includes agentless migration, operating system upgrades, SQL Server edition optimization, workload right-sizing, and configuration of security, monitoring, and backup tooling for supported workloads and destinations.

With RiverMeadow’s clone-first approach, teams can modernize and validate the workload on the clone before cutover. The purpose is practical: modernize the workload, preserve the application, and reduce uncertainty before moving production.

Why private deployment matters now

Sovereignty and regulated environments

For financial services, healthcare, public sector, and critical infrastructure organizations, the location of credentials, workload configurations, and migration metadata can influence procurement and security approval. Private Deployment lets teams place the platform within an environment selected to meet their jurisdictional and organizational requirements.

VMware exits within the data center

A VMware exit can lead to another platform in the same facility. Organizations moving to Red Hat OpenShift Virtualization, Nutanix, HPE VME, or Microsoft Azure Local can run RiverMeadow alongside their source and destination infrastructure. That keeps orchestration close to the workloads and can keep migration traffic local when the source and target are local.

Cloud infrastructure and edge locations

Platforms such as AWS Outposts and Microsoft Azure Local extend infrastructure choices into customer facilities. Private Deployment gives teams a way to run migration orchestration locally. Connectivity requirements still depend on the selected infrastructure, destination, and workflow.

Partner delivery

System integrators and managed service providers can deploy RiverMeadow in their own environments to deliver repeatable migration and modernization programs. Customer isolation, access controls, and data handling remain essential parts of the delivery design.

Control over credentials and migration metadata

In a Private Deployment, credentials are stored encrypted within the deployment environment, and migration metadata is retained there. Access can be managed through role-based controls, with TLS protecting UI access and data in transit.

The platform can sit behind your network boundary without public internet exposure. The deployment design should account for installation, licensing, updates, support access, and the connectivity required by each source and destination.

There is an important distinction between where the platform runs and where workloads move. Credentials and migration metadata stay within the deployment environment; workload data moves to the destination you select. If that destination is public cloud or another location, the migration transfers workload data there.

RiverMeadow has also completed an independent SOC 2 Type II examination. This provides an additional assurance reference alongside the security and operational controls established for each deployment.

AWS GovCloud (US)

RiverMeadow Private Deployment enables customers to move to AWS GovCloud while retaining control of their migration environment. It gives organizations control over where the platform runs, with encrypted credentials and migration metadata retained within the deployment environment, alongside governance and reporting throughout the program.

Customers and partners can contact RiverMeadow to discuss an AWS GovCloud migration and confirm supported workloads, deployment options and regional availability.

Discuss your AWS GovCloud project

Discuss Private Deployment

Where RiverMeadow runs should support your migration program. Private Deployment gives you control of the platform environment while retaining the modernization, validation, governance, and reporting capabilities needed to complete the move.

One software platform. Any source to any target.

Talk to a RiverMeadow expert about Private Deployment for your next migration and modernization program. Visit rivermeadow.com or contact sales@rivermeadow.com.

Discuss Private Deployment with our team