Supavisor vs TiCDC
Supavisor
github.comTiCDC
docs.pingcap.comSide by side
| Figure | Supavisor | TiCDC |
|---|---|---|
| Price from | $25/mo | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | Yes | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 5 | 1 |
| Spec score · Database Proxy Software | 8.5 (#4) | 8.1 (#6) |
| Availability | The README describes cluster behavior that can restart tenant pools when clients reconnect after a node goes down. | TiCDC has no single point of failure and supports dynamically adding and deleting TiCDC nodes. |
| Founded | 2020 | 2015 |
| Funding news | Supabase announced an $80 million Series B in May 2022, bringing reported total funding to $116 million at that time. | 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. |
| High availability | Cluster nodes monitor tenant pools and reconnecting clients can start replacement pools after a node failure. | TiCDC has no single point of failure and supports dynamically adding or deleting TiCDC nodes. |
| Licence | The repository is distributed under the Apache-2.0 licence. | The public TiCDC repository is licensed under Apache-2.0. |
| Purpose | Supavisor is a scalable, cloud-native Postgres connection pooler. | TiCDC replicates incremental data from TiDB by capturing TiKV change logs, sorting the changes, and exporting row-based data to downstream systems. |
| What it does | Supavisor is a scalable, cloud-native connection pooler that proxies many PostgreSQL client connections into pooled database connections. | TiCDC captures TiKV change logs, orders them, and exports row-level incremental changes from TiDB to downstream systems. |
Plans
Supavisor
- FreeFree
- Open-source SupavisorFree
- Pro$25 a month
- Team$599 a month
- EnterprisePriced on request
In their own words
TiCDC
TiCDC is a free, open-source, self-hosted tool for replicating incremental data changes from TiDB. It captures TiKV change logs, sorts the changes, and exports row-based data to systems including TiDB, MySQL-compatible databases, Kafka, Amazon S3, GCS, Azure Blob Storage, and NFS. Recommended Kafka formats include Canal-JSON, Avro, and Debezium. Filters can select databases, tables, DMLs, and DDLs, while the Open API can check task status, change task configuration, and create or 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 cluster or added to an existing one; production guidance recommends at least two instances. The system has no single point of failure and allows nodes to be added or removed dynamically. Delivery is at least once, so failures can lead to repeated statements or Kafka messages.