Materialization Connectors
Estuary's available materialization connectors are listed in this section. Each connector has a unique set of requirements for configuration; follow the connector link for a full reference on the system's requirements, properties, and best practices.
Estuary is actively developing new connectors, so check back regularly for the latest additions. We’re prioritizing the development of high-scale technological systems, as well as client needs.
At this time, all the available materialization connectors are created by Estuary. In the future, other open-source materialization connectors from third parties could be supported.
Available materialization connectors
Data warehouse and OLAP connectors
Database connectors
- AlloyDB
- Amazon DynamoDB
- Amazon MySQL
- Amazon PostgreSQL
- Amazon SQL Server
- Azure SQL Server
- Google Cloud Bigtable
- Google Cloud MySQL
- Google Cloud PostgreSQL
- Google Cloud SQL Server
- Google Spanner
- MongoDB
- MySQL
- MySQL Heatwave
- Pinecone
- PostgreSQL
- SingleStore
- SQLite
- SQL Server
- Supabase
- TimescaleDB
Lakehouse connectors
File connectors
- Apache Parquet Files in Azure Blob Storage
- Apache Parquet Files in GCS
- Apache Parquet Files in S3
- CSV Files in GCS
- CSV Files in S3
- Google Sheets
- JSON Files in S3
Event connectors
Integrations with streaming services, queues, and event-based systems outside of Estuary's Dekaf connectors.
- Amazon EventBridge
- Amazon SNS
- Apache Kafka
- Elasticsearch
- Google Cloud Pub/Sub
- HTTP Webhook
- OpenSearch
SaaS/reverse ETL connectors
Dekaf connectors
Dekaf is Estuary's Kafka-compatible API. Materializations using Dekaf send data to destinations via the destination's Kafka integration.