TiCDC
docs.pingcap.com
- Free plan
- Open source
- macOS
- Linux
- API
- Self-hosted
What TiCDC is
TiCDC is a self-hosted, open-source tool that replicates incremental changes from TiDB to downstream systems. It captures TiKV change logs, sorts the changes and exports row-based data to TiDB, MySQL-compatible databases, Kafka, Amazon S3, GCS, Azure Blob Storage or NFS. Recommended Kafka formats include Canal-JSON, Avro and Debezium. Filters can restrict replication by database, table, DML or DDL, and the Open API can report task status, update task configuration, or create and delete tasks. TiCDC supports replication between TiDB clusters for disaster recovery, with second-level RPO and minute-level RTO, as well as bidirectional replication for multi-active deployments. It can be deployed with a new TiDB cluster or added to an existing one; production guidance recommends at least two instances. It supports dynamically adding and removing TiCDC nodes and has no single point of failure. Delivery is at least once, so failures may result in repeated statements or Kafka messages. The software is free, with no paid plans or usage caps stated on its TiCDC pages.
Who it suits
TiCDC suits teams running TiDB that need change-data feeds for recovery, monitoring, caching, indexing, analysis or replication between different database systems. It requires a self-hosted deployment.
Good to know, and what to watch
- Replicates to databases, Kafka and cloud storage
- Filters databases, tables, DMLs and DDLs
- Supports bidirectional TiDB replication
- Nodes can be added or removed dynamically
- Delivery is at least once, so repeats can occur
- Generally replicates only tables with a valid index
- Large transactions have partial support and out-of-memory risk
- Production guidance recommends at least two instances
Plans
Every plan and priceTiCDC (open-source)
Open source
The verdict
TiCDC provides configurable, self-hosted replication for TiDB changes across a range of destinations. Account for its at-least-once delivery and documented transaction limitations when planning a deployment.
What the maker publishes
- API limitation
- TiCDC OpenAPI v1 is deprecated, and its task-creation parameters are less complete than the CLI parameters; the documentation recommends OpenAPI v2. source
- Availability
- TiCDC has no single point of failure and supports dynamically adding and deleting TiCDC nodes. source
- Bidirectional replication
- TiCDC can replicate changes in both directions between TiDB clusters for multi-active deployments. source
- Build requirements
- The repository documents compiling TiCDC on Linux or macOS with Go 1.25.12 using make cdc. source
- Company founding
- LinkedIn states that the TiDB organization was founded in 2015 by three software engineers. source
- Company size
- LinkedIn lists TiDB powered by PingCAP as having 501–1,000 employees and headquarters in Sunnyvale, California. source
- Compatibility requirement
- The new architecture requires TiDB 7.5.0 or later. source
- Delivery semantics
- TiCDC outputs each DDL or DML at least once, so failures can cause repeated statements or Kafka messages. source
- Deployment
- TiCDC can be deployed with a new TiDB cluster or added to an existing cluster using TiUP. source
- Deployment and scale
- TiCDC can be deployed with a new TiDB cluster or added to an existing cluster, and the deployment documentation recommends at least two instances in production. source
- Disaster recovery
- TiCDC can replicate between TiDB clusters with second-level RPO and minute-level RTO. source
- Disaster recovery
- TiCDC supports primary-secondary TiDB replication with second-level recovery-point objectives and minute-level recovery-time objectives. source
- Documentation
- The TiCDC documentation includes deployment, changefeeds, monitoring, alerting, troubleshooting, performance tuning, integration scenarios, APIs, compatibility, FAQs, and a glossary. source
- Download targets
- Published binaries cover Linux amd64 and arm64 plus macOS amd64 and arm64. source
- Downstream sinks
- TiCDC can replicate to TiDB, MySQL-compatible databases, Kafka, Amazon S3, GCS, Azure Blob Storage, and NFS. source
- Filtering
- Replication rules can filter databases, tables, DML events, and DDL events. source
- Filtering and management
- TiCDC can filter databases, tables, DMLs, and DDLs, and its Open API can query task status, modify task configuration, and create or delete tasks. source
- Founded
- 2015 source
- Funding news
- PingCAP announced a $270 million Series D round on November 17, 2020, led jointly by GGV Capital, Access Technology Ventures, Anatole Investment, Jeneration Capital, and 5Y Capital. source
- Headquarters
- Sunnyvale, California, USA source
- High availability
- TiCDC has no single point of failure and supports dynamically adding or deleting TiCDC nodes. source
- Index requirement
- TiCDC generally replicates only tables with at least one valid index, though the force-replicate option can replicate tables without one. source
- Intended users
- Documented use cases include disaster recovery, real-time data feeds for monitoring, caching, indexing and analysis, and replication between heterogeneous databases. source
- Kafka formats
- Recommended Kafka data formats include Canal-JSON, Avro, and Debezium. source
Checked against the maker's pages on 21 Oct 2026.