Open-Source Observability · signal18

replication-manager

Replication Manager is an open-source tool for monitoring, backing up, and managing high-availability clusters of MySQL, MariaDB, and Percona Server databases. It automates failover, handles replica promotion, integrates with proxies like ProxySQL and HAProxy, and provides comprehensive observability through metrics, alerts, and a web UI.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/signal18/replication-manager

733

GitHub stars

172

Forks

Primary language

GPL-3.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	signal18/replication-manager
Owner	signal18
Primary language	Go
License	GPL-3.0 — OSI-approved
Stars	733
Forks	172
Open issues	143
Latest release	v3.1.31 (2026-07-08)
Last updated	2026-07-08
Source	https://github.com/signal18/replication-manager

What replication-manager is

A Go-based orchestration platform supporting GTID, multi-source, semi-sync, and group replication topologies with automated primary election, logical/physical backup scheduling (mysqldump, mariabackup, xtrabackup, Restic), proxy backend management, and REST/gRPC APIs with RBAC. Integrates with Vault for credential rotation and OAuth2 for SSO.

Quickstart

Get the replication-manager source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/signal18/replication-manager.git2cd replication-manager3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

High-Availability MySQL/MariaDB Clusters

Organizations running critical MySQL/MariaDB replication topologies that require automated failover, replica promotion, and multi-cluster management without manual intervention or custom scripting.

Backup and Disaster Recovery Automation

Teams needing scheduled logical/physical backups with point-in-time recovery, retention policies, S3-compatible storage, and automated purge—reducing manual backup overhead and enabling faster recovery.

Kubernetes-Native Database Operations

Containerized deployments on Kubernetes where automated database provisioning, init containers, rolling restarts, and integrated monitoring are required alongside proxy management.

Implementation considerations

Requires deep understanding of MySQL replication topologies (GTID, semi-sync, group replication, multi-source) and operational procedures to configure correctly and respond to alerts.
Backup strategy must align with retention policies, storage backend (S3 or other object storage), and RTO/RPO requirements; test recovery procedures regularly.
Network prerequisites include stable connectivity between Replication Manager and all monitored instances, plus firewall rules for proxy integration and API access.
Credential management via Vault integration or encrypted config files requires secure key/secret storage infrastructure; plan rotation cycles for replication and monitoring accounts.
Monitoring and alerting require integration with existing observability stacks (Carbon/Graphite, email, Slack, Teams, Mattermost) and on-call runbook updates.

When to avoid it — and what to weigh

Single-server or non-replicated MySQL instances — Replication Manager is designed for replication topologies; it adds unnecessary complexity for standalone databases without replication or failover needs.
Fully managed database services (RDS, Azure Database, GCP Cloud SQL) — Cloud-native managed databases handle replication and failover internally; Replication Manager targets self-hosted or on-premises infrastructure.
Organizations unable or unwilling to adopt GPLv3 licensing — GPLv3 requires derivative works to be open-sourced. If proprietary licensing or BSD/MIT-only policies are non-negotiable, this tool is not suitable.
PostgreSQL, MongoDB, or other non-MySQL RDBMS — Replication Manager is MySQL/MariaDB/Percona-specific; it does not support other database engines.

License & commercial use

Licensed under GPLv3. Derivative works must be open-sourced. Third-party libraries in vendor directory carry their own licenses (MIT, etc.). Refer to LICENSE file and vendor directory for complete details.

GPLv3 permits commercial use, but any modifications or derivative works must be publicly released under GPLv3. Proprietary forks or closed-source extensions are not permitted without explicit licensing from Signal18 Cloud SAS. Requires review if commercial modifications are planned.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Strong
License clarity	Clear
Deployment complexity	High
DEV.co fit	Good
Assessment confidence	High

Security considerations

Supports encrypted secrets in config files, Vault integration for credential rotation, and OAuth2 SSO with RBAC for API access. WebTTY terminal sessions introduce remote access vectors; ensure authentication and audit logging are enforced. No third-party security audit or CVE history is provided; evaluate threat model and apply standard hardening (network isolation, least-privilege accounts, regular patching).

Alternatives to consider

Percona XtraDB Cluster (PXC) + Percona Monitoring and Management (PMM)

Provides synchronous replication and integrated monitoring; simpler for clusters where synchronous consistency is acceptable. Does not automate failover in the same way.

MariaDB MaxScale + MariaDB Replication Manager fork (if available)

MariaDB ecosystem native; may have tighter integration. Replication Manager is a community/Signal18 alternative that offers more topology flexibility.

Orchestrator (by GitHub/Vitess team)

Older, lightweight topology management and failover tool for MySQL replication. Lacks comprehensive backup, proxy, and Kubernetes features; suitable for simpler HA scenarios.

Software development agency

Build on replication-manager with DEV.co software developers

Replication Manager offers powerful automation for MySQL/MariaDB HA, but GPLv3 licensing and operational complexity require careful planning. Let Devco help assess fit, design deployment, and manage integration with your existing stack.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

pmm mydumper dolphie

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Observability DevOps & Infrastructure Automation Cloud Deployment & Kubernetes Custom Software & Integrations Talk to DEV.co

replication-manager FAQ

Can I use Replication Manager with MySQL 5.7 and earlier?

Not clearly stated in provided data. Review documentation and release notes at docs.signal18.io for version compatibility.

What is the cost of commercial support or enterprise licensing?

Not provided. Replication Manager is open-source under GPLv3; contact Signal18 Cloud SAS (https://signal18.io) for support and licensing inquiries.

Does Replication Manager support async, semi-sync, and synchronous replication simultaneously in a single cluster?

Yes. README states support for 'async, semi-sync, multi-master, mesh, wsrep, group replication, and relay topologies,' indicating mixed replication modes are supported.

Can I migrate from an existing MySQL HA setup (e.g., Orchestrator + MHA) to Replication Manager?

Unknown without reviewing migration guides. Recommend consulting documentation and testing in a non-production environment first.

Software development & web development with DEV.co

Need help beyond evaluating replication-manager? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source observability integrations — and maintain them long-term.

Evaluate Replication Manager for Your Database Infrastructure

Talk to DEV.co Schedule a Consultation