IRI Ripcurrent vs PeerDB

IRI Ripcurrent has no write-up on Specifiction yet; its figures are above.

PeerDB streams data from Postgres to data warehouses, queues, and storage engines, using one-way replication. Its supported methods include log-based change data capture, cursor-based replication with timestamps or integers, and XMIN-based replication. A Postgres-compatible SQL interface supports ETL and data movement, and PeerDB handles Postgres data types such as jsonb, arrays, and PostGIS, as well as TOAST columns and schema changes. The actively maintained source connectors are PostgreSQL, MySQL, MongoDB, CockroachDB, and BigQuery; actively maintained destinations are ClickHouse, ClickHouse Cloud, and Postgres. Snowflake, BigQuery, Elasticsearch, Kafka, Redpanda, Confluent, Azure Event Hubs, Google Pub/Sub, and S3 destinations are deprecated and no longer actively maintained. PeerDB is available for free deployment under the AGPL-3.0 license. Paid plans start at $250/mo for Micro, which allows up to two vcores and is recommended for up to 50 million rows moved per month. Larger plans list higher row-volume recommendations and vcore limits. PeerDB states that it is 10x faster than existing tools and reports SOC 2 Type II and GDPR compliance.