SYSTEM Cited by 1 source
PlanetScale Connect¶
What it is¶
PlanetScale Connect is PlanetScale's first-party CDC / ELT feature, built on top of the VStream API. Connect exposes a PlanetScale MySQL database as a source for popular ETL / data-warehouse / data-lake destinations by composing the upstream VStream gRPC surface with open-source per-vendor drivers — notably Airbyte (via planetscale/airbyte-source) and Fivetran (via planetscale/fivetran-source).
Why it exists¶
PlanetScale customers' databases are the operational-truth OLTP tier; Connect's job is to stream changes out to customers' analytical systems (data warehouses like Snowflake / Redshift / BigQuery, data lakes, integration targets) without requiring those customers to run their own Debezium + Kafka + Kafka-Connect stack. Connect is the managed, productised consumer of the VStream API that the 2024-07-29 Matt Lord post canonicalises.
Why it shows up on this wiki¶
Connect is the first-party wrapper of the CDC driver ecosystem Vitess exposes. It demonstrates the "build a vendor-managed consumer of your own public CDC API" shape — PlanetScale both publishes the upstream primitive (VStream, in open-source Vitess) and ships a managed, customer-facing integration on top of it.
Stub page. Expand when a PlanetScale post disclosing Connect's internals (scale numbers, target support matrix, failure semantics, schema-change handling) is ingested.
Seen in¶
- sources/2026-04-21-planetscale-building-data-pipelines-with-vitess — named as a PlanetScale-built consumer of the VStream API: "PlanetScale also uses the VStream API to build the Connect feature, using additional open source drivers for popular CDC/ETL services such as Airbyte and Fivetran." No internals disclosed in this post; the link points to a separate Connect launch post (extract-load-and-transform-your-data-with-planetscale-connect) not yet ingested.