Canal
github.com
- Free plan
- macOS
- Linux
- API
- Self-hosted
What Canal is
Canal is a free, self-hosted project for subscribing to and consuming MySQL changes incrementally. It behaves like a MySQL replica: it requests binary log data from a master database and parses the events. Listed uses include mirroring databases, real-time backup, index maintenance, cache refresh, and business-logic processing. The README lists source support for MySQL versions 5.1.x, 5.5.x, 5.6.x, 5.7.x, and 8.0.x. Change records can be sent to Kafka and RocketMQ; the quick start also lists RabbitMQ and Pulsar server modes. Canal uses a Protocol Buffers 3.0 client-server design, with clients listed for Java, C#, Go, and Python. Canal Admin provides a web interface for configuration, tasks, and logs, while the project also lists native Prometheus monitoring. Docker images and a Docker QuickStart are available, but the default Docker setup runs only one Canal instance per Docker instance. The repository identifies the project as Apache-2.0 licensed. Release notes for v1.1.8 list SSL/TLS connections to source MySQL and RabbitMQ SSL authentication support.
Who it suits
Canal suits technical teams that need to capture MySQL changes and route them to other systems. Its self-hosted deployment and language-specific clients are relevant to teams managing their own data infrastructure.
Good to know, and what to watch
- Captures changes from listed MySQL versions.
- Can route change records to Kafka and RocketMQ.
- Admin web UI manages configuration, tasks, and logs.
- Native Prometheus monitoring is listed.
- Default Docker setup runs one Canal instance.
- The project is self-hosted.
Plans
Every plan and priceCanal
Free plan
Getting started
- Open the Canal GitHub repository
- Prepare a supported self-hosted environment
- Install using the provided Docker images or Docker QuickStart
- Configure Canal to request binlog data from a MySQL master
- Use Canal Admin to manage configuration, tasks, and logs
- Connect Kafka or RocketMQ as a destination
- Implement a client with Protocol Buffers 3.0
Limits to check
The default Docker QuickStart allows one Canal instance per Docker instance. Canal is self-hosted, and the listed source database versions define the documented compatibility range.
The Club's review
Canal is a self-hosted change-data-capture tool for teams that need to turn MySQL binlog events into updates for downstream services. It is best suited to engineering teams comfortable operating database infrastructure and integrating through its client protocol or message-queue outputs. Its focused capture model is useful, but Docker’s default one-instance setup and the need to run it yourself call for deployment planning.
Overview
Canal acts as a MySQL replica: it requests binary-log data from the master database and parses the events for incremental subscription and consumption. That log-based approach supports database mirroring and real-time backup, index maintenance, cache refresh, and business-logic processing. The repository is licensed under Apache-2.0, and deployment is self-hosted.
The README lists MySQL 5.1.x, 5.5.x, 5.6.x, 5.7.x, and 8.0.x as source versions. Release notes for v1.1.8 also describe adaptations for MySQL 8.4, MariaDB 11, Percona 8.0, and PolarDB-X 2.0, giving teams with those databases a basis to evaluate compatibility.
Key features
Destinations and client integration
Canal can deliver change records to Kafka and RocketMQ; its quick start also lists RabbitMQ and Pulsar as server modes. The v1.1.8 release notes announce a ClickHouse adapter. This range gives teams several ways to route changes, though the documented client-server protocol may be the better fit when an application needs to consume changes directly: Canal uses Protocol Buffers 3.0 and lists clients for Java, C#, Go, and Python.
Administration and monitoring
Canal Admin provides a web interface for dynamic management of configuration, tasks, and logs. Native Prometheus monitoring is also supported. These tools suit teams that want an administrative interface and monitoring integration alongside their own deployment, rather than a managed service.
Deployment and security
Docker images and a Docker QuickStart offer a route to containerized deployment, but the QuickStart's default configuration runs only one Canal instance per Docker instance. Teams needing multiple instances should account for that limit when designing deployment. The v1.1.8 notes describe SSL/TLS connections to source MySQL and RabbitMQ SSL authentication support. Vulnerability reports go to Alibaba Security Response Center, which says it will keep reporters informed while fixes are pursued; bugs and feature requests are directed to GitHub issues.
Pricing
Canal is free. Its Canal plan costs free and is an Apache-2.0 open-source project. There are no paid tiers to weigh against the free plan, so the trade-off is operational: teams run the self-hosted software and plan around its deployment model.
Platforms
Canal identifies API, Linux, macOS, and self-hosted as platforms. Its supported-platform list also includes Kubernetes, Linux, ACK Distro, AECP, and SOFAStack. Docker images and a QuickStart can help teams start with containers, subject to the one-instance default setup.
Who it's for
Canal is a practical candidate for teams that need MySQL change capture, already operate self-hosted infrastructure, and can use its supported clients or message destinations. It is also relevant to teams pursuing the stated mirroring, backup, indexing, cache-refresh, or business-logic use cases. Organizations seeking a managed capture service, or that cannot accommodate its instance-level Docker constraint, should consider another fit.
Pros and cons
- Pros: Log-based capture makes incremental MySQL changes available for several database and application workflows.
- Pros: Kafka and RocketMQ delivery, additional RabbitMQ and Pulsar server modes, and clients in four listed languages provide multiple integration routes.
- Pros: Canal Admin and native Prometheus monitoring support operational oversight.
- Pros: Apache-2.0 licensing and a free plan make the project available without a software charge.
- Cons: Self-hosted deployment puts operation on the adopting team.
- Cons: The Docker QuickStart default permits one Canal instance per Docker instance, which can constrain a straightforward container setup.
Alternatives
For database change capture specifically, compare Canal with Change Data Capture Software. If the need is Kubernetes networking rather than MySQL binlog capture, the free, self-hosted Calico Open Source includes in-memory data retention and unlimited clusters; Spiderpool is a free Kubernetes networking solution; and Terway is an open-source option whose trunking is unavailable in self-hosted clusters.
Cilium is a free, open-source Linux option requiring kernel 5.10 or equivalent and AMD64 or AArch64. Flannel is an Apache 2.0 open-source Kubernetes networking project. Antrea is Apache-2.0 software requiring a Kubernetes cluster and the Open vSwitch kernel module on every node. OVN-Kubernetes is another free option for readers comparing networking platforms. For a feature-store category search, see Feature Store Software; for container networking, see Container Networking Software.
Verdict
Choose Canal if your team needs MySQL binlog capture, values its client and queue integrations, and can own a self-hosted deployment. Its focused change-delivery path is the main reason to use it; the operational burden and Docker's one-instance default are the strongest reasons to look elsewhere.
The verdict
Canal offers a focused route from MySQL binary logs to downstream systems, with several client languages and administration tools. Teams should account for its self-hosted setup and the one-instance default Docker limit.
Questions people ask
What does Canal do?
Canal parses MySQL binary logs and provides incremental subscription and consumption of database changes.
Which MySQL versions are listed?
The README lists MySQL 5.1.x, 5.5.x, 5.6.x, 5.7.x, and 8.0.x; release notes also list adaptation for MySQL 8.4.
Which message systems can receive changes?
Canal supports native delivery to Kafka and RocketMQ. RabbitMQ and Pulsar are also listed as server modes, and version 1.1.8 announces a ClickHouse adapter.
Is Canal open source?
Yes. The repository identifies Canal as an Apache-2.0 open-source project and the plan is free.
Which client languages are supported?
The Protocol Buffers 3.0 client-server design lists Java, C#, Go, and Python clients.
How is Canal administered and monitored?
Canal Admin provides a web interface for configuration, tasks, and logs, while native Prometheus monitoring is listed.
What the maker publishes
- Additional adapters
- The v1.1.8 release notes announce a ClickHouse adapter. source
- Administration
- Canal Admin provides a Web UI for dynamic management, including configuration, tasks, and logs. source
- Administration
- Canal Admin provides web based dynamic management, including online configuration, task, and log operations. source
- Client languages
- The project describes a Protocol Buffers 3.0 client-server protocol and lists Java, C#, Go, and Python clients. source
- Client protocol
- Canal uses a client server design with Protocol Buffers 3.0, and clients can be implemented in different languages. source
- Database support
- The README lists MySQL 5.1.x, 5.5.x, 5.6.x, 5.7.x, and 8.0.x as supported source versions. source
- Deployment
- Canal provides Docker images and the repository includes a Docker QuickStart. source
- Deployment
- The README says Canal provides native Docker image support. source
- Deployment limit
- The Docker QuickStart says one Docker instance can run only one Canal instance with the default setup. source
- How it works
- Canal simulates a MySQL replica, requests binlog data from the master, and parses the events. source
- How it works
- Canal emulates a MySQL slave, requests the dump protocol from a MySQL master, and parses the binary log stream it receives. source
- License
- The GitHub repository identifies its license as Apache-2.0. source
- License
- The repository identifies its license as Apache-2.0. source
- Message queues
- Canal can send change records to Kafka and RocketMQ; its quick start also lists RabbitMQ and Pulsar as server modes. source
- Message systems
- Canal supports native delivery to Kafka and RocketMQ, and the README also describes publishing change records to message queues. source
- Monitoring
- The project lists native Prometheus monitoring support. source
- Monitoring
- The README says Canal has native Prometheus monitoring support. source
- MySQL versions
- The README lists source MySQL versions 5.1.x, 5.5.x, 5.6.x, 5.7.x, and 8.0.x as supported. source
- Purpose
- Canal parses MySQL binary logs to provide incremental data subscription and consumption. source
- Purpose
- Canal parses MySQL database incremental logs and provides incremental data subscription and consumption. source
- Recent compatibility
- The v1.1.8 release notes list adaptation for MySQL 8.4, MariaDB 11, Percona 8.0, and PolarDB-X 2.0. source
- Security
- The v1.1.8 release notes list SSL/TLS connections to source MySQL and RabbitMQ SSL authentication support. source
- Security reporting
- The security policy directs vulnerability reports to Alibaba Security Response Center and says reporters will be kept informed while fixes are pursued. source
- Support
- The project asks users to report bugs and feature requests through GitHub issues. source
Checked against the maker's pages on 30 Sept 2026.