Destinations
Pick one of our high-quality destinations and load your data into a local database, warehouse, or data lake. Append, replace, or merge your data. Apply performance hints like partitions, clusters, or indexes. Load directly or via staging. Each of our destinations undergoes several hundred automated tests every day.
- Is a destination or feature missing? Join our Slack community and ask for it.
- Need more info? Join our Slack community and ask in the tech help channel or book a call with a dltHub Solutions Engineer.
Otherwise, pick a destination below:
๐๏ธ Google BigQuery
Google BigQuery `dlt` destination
๐๏ธ Databricks
Databricks `dlt` destination
๐๏ธ DuckDB
DuckDB `dlt` destination
๐๏ธ Microsoft SQL Server
Microsoft SQL Server `dlt` destination
๐๏ธ Azure Synapse
Azure Synapse `dlt` destination
๐๏ธ ClickHouse
ClickHouse `dlt` destination
๐๏ธ Cloud storage and filesystem
The filesystem destination stores data in remote file systems and cloud storage services like AWS S3, Google Cloud Storage, or Azure Blob Storage. Underneath, it uses fsspec to abstract file operations. Its primary role is to be used as a staging for other destinations, but you can also quickly build a data lake with it.
๐๏ธ Postgres
Postgres `dlt` destination
๐๏ธ Amazon Redshift
Amazon Redshift `dlt` destination
๐๏ธ Snowflake
Snowflake `dlt` destination
๐๏ธ AWS Athena / Glue Catalog
AWS Athena `dlt` destination
๐๏ธ Weaviate
Weaviate is an open source vector database that can be used as a destination in dlt.
๐๏ธ LanceDB
LanceDB is an open source vector database that can be used as a destination in dlt.
๐๏ธ Qdrant
Qdrant is a high-performance vector search engine/database that can be used as a destination in dlt.
๐๏ธ ๐งช Dremio
Dremio `dlt` destination
๐๏ธ Custom destination
Custom `dlt` destination function for reverse ETL
๐๏ธ MotherDuck
MotherDuck `dlt` destination
๐๏ธ Create new destination
You can use @dlt.destination decorator and implement a sink function. This is a perfect way to implement reverse ETL components that push data back to REST APIs.