Your Global Repositories,
Always in Sync
Run Git Without Downtime
- No Single Server Vulnerability: Multiple writable sites remove the central Git bottleneck. If one location goes offline, development continues elsewhere.
- Built-in Disaster Recovery: Every site maintains a live copy of the repositories, keeping work moving, even during infrastructure outages.
- Automatic Catch-up After Outages: When a site reconnects, it automatically synchronizes the changes it missed — no manual intervention required.
Work at Local Speed
- Fast Access: Developers interact with the Git server closest to them, reducing delays when cloning or fetching repositories.
- Consistent Repositories: All sites remain synchronized so teams work from the same repository state across locations.
- Reliable Global Pushes: Changes propagate safely across the network, balancing performance and redundancy.
Scale Your Git Infrastructure
- Add New Sites: Bring new Git servers online as your organization expands — without redesigning your infrastructure.
- Control Where Repositories Live: Choose which repositories are available at each site to support security policies and reduce infrastructure overhead.
- Simplify Operations: Active MultiSite automatically handles synchronization, so platform teams spend less time managing replication and infrastructure.
What ActiveMultiSite Makes Possible.
Active MultiSite works behind the scenes to keep every Git, Gerrit, and Subversion server in sync while developers work locally.
Here are the core capabilities that make that possible.
Single "upstream" repository consistency
Each replica in a repository family is updated using a family operations stream enabling 100% consistency of all replicas after replication.
Automatic catch-up after offline events
Network and server outages happen. Git AMS enables fully automatic catch-up of all write operations done at the sites that remained up. No administrator interaction involved.
High availability
When Git AMS is deployed in a cluster it will enable a fully highly available environment.
Disaster recovery
When a remote disaster recovery site is configured all repositories replicated to it will be kept up to date with all of the other operational replicas.
Selective replication
You can choose which sites get which repositories. This enables access policies required in specific industries. It also enables lower cost (smaller size) servers for locations that require access to fewer repositories.
Fast local clones
Repository “read” operations are latency close to your users minimizing the time required to do those clones.
Fastest robust pushes
Configurable data redundancy policies enable best performance for the compromise between redundancy, recoverability and speed.
Enables Git authorization control
Git itself has not built-in access control mechanism. Git Active MultiSite enables a simple yet effective access control mechanism enabling proper control of your intellectual property.
How Global Engineering Teams Scale
Customer Success Stories
Scalability solution for a major phone manufacturer

Challenge
- Horizontal scalability issues with 9,000+ users and 11,000+ repositories.
- The Gerrit "high availability" plugin, which supports multiple read-only sites, was insufficient to handle the high access load on the read-write server.
Results
- Implemented a DConE solution, deploying 7 multi-primary sites across various locations to distribute and manage the end-user load effectively.
- Continued use of the Gerrit "high availability" plugin to offload simple Git clones and fetches.
Efficient global collaboration for an electronics manufacturer

Challenge
- Need for efficient collaboration across global development sites.
- Requirement for fast access to large files during Git checkouts.
Results
- Enabled efficient global collaboration by replicating Git LFS storage across development sites. This ensures large files are latency-close, allowing for quick downloads and improved productivity.
- Allowed for cost-effective management by locating Git project repositories only where needed, optimizing server usage for specific use cases.
Robust, no-failure software development for an automotive manufacturer

Challenge
- Eliminate single points of failure in a single data center setup.
- Ensure seamless maintenance without downtime.
Results
- Deployed 3 primary-primary sites with single-copy identical data. This setup allows any one site to be taken down for maintenance while the other two remain fully operational in read-write mode.
- Prevents server stalls by ensuring data is not locked in a down site, maintaining smooth operations.
- Proxy server positioned in front of the three sites to ensure seamless availability and access.

Resources
Datasheet
Published July 2025
User Guide
v.1.14 (latest)
Git Binaries
Stay ahead: receive every BlueOptima certified Git binary release as soon as it’s live.
Git Version | Operating System (OS) | Download |
|---|---|---|
2.39.1 | CentOS 6 - Git 2.39.1 | Download |
2.39.1 | CentOS 7 - Git 2.39.1 | Download |
2.39.1 | RedHat Enterprise Linux 6 - Git 2.39.1 | Download |
2.39.1 | RedHat Enterprise Linux 7 - Git 2.39.1 | Download |
2.39.1 | SUSE Linux Enterprise 11 - Git 2.39.1 | Download |
2.39.1 | SUSE Linux Enterprise 12 - Git 2.39.1 | Download |
2.39.1 | Ubuntu 12.04 - Git 2.39.1 | Download |
2.39.1 | Ubuntu 14.04 - Git 2.39.1 | Download |
2.31.1 | Windows x64 | Download |
2.31.1 | Ubuntu 20.04 Focal | Download |
Ready to Supercharge Your Global Git?
Stop letting infrastructure slow you down. See how BlueOptima Git Active MultiSite can revolutionize your team's collaboration and efficiency.
