Replication in ProGet

Replication helps distribute packages across environments, regions, and teams while maintaining package availability and supporting disaster recovery workflows.

For organizations migrating from Sonatype Nexus, replication workflows in ProGet will feel familiar. Packages can be synchronized across multiple ProGet instances to support distributed development teams, regional infrastructure, and backup environments.

This article covers:

• feed replication in ProGet
• edge and federated development workflows
• replication management and monitoring

Replication In ProGet

Replication in ProGet is available with Enterprise licensing and operates at the feed level.

Unlike Sonatype Nexus, which relies on scheduled replication tasks and optional pre-emptive fetching, ProGet uses near-continuous synchronization to automatically replicate package changes between instances.

Replication currently focuses on package synchronization across feeds and environments. ProGet also supports replication between different ProGet versions, allowing organizations to migrate or synchronize environments while maintaining package availability across instances.

Common replication scenarios include:

• synchronizing packages between regional environments
• supporting distributed development teams
• maintaining backup or disaster recovery environments
• separating development, staging, and production infrastructure

ProGet supports both hub-and-spoke and bi-directional replication models.

In hub-and-spoke environments, a central ProGet instance distributes packages to multiple downstream instances across regions or teams.

Bi-directional replication allows multiple environments to exchange packages between instances, supporting collaborative or federated development workflows.

Configuring Replication

Replication can be configured through the ProGet UI or API.

Once configured, synchronization runs automatically in the background without requiring manually scheduled replication jobs.

ProGet also includes monitoring and status visibility through the Replication Overview page, allowing administrators to review replication health, synchronization activity, and environment status across instances.

Replication Patterns

Edge Locations

Edge Location replication uses a hub-and-spoke model to distribute packages from a central ProGet instance to multiple edge servers.

This helps reduce latency and improve package availability for teams operating across multiple geographic regions by keeping packages closer to the environments where they are consumed.

Federated Development

Federated Development replication supports collaborative workflows between separate teams or environments.

By configuring both incoming and outgoing feed replication, teams can maintain local package availability while still sharing packages across organizational boundaries or development environments.

Replication Management in ProGet

For Sonatype Nexus users, replication concepts in ProGet remain familiar while reducing operational overhead.

Replication is managed directly through feeds and synchronized automatically, eliminating the need to manage separate replication scheduling workflows or pre-emptive fetch configurations.

ProGet also supports replication across different ProGet versions, helping simplify migrations, upgrades, and multi-environment synchronization strategies.

Together, these replication capabilities support distributed development, package availability, and disaster recovery workflows while maintaining centralized package management across environments.