

Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say

Andre Exner

"For TUI Musement, Airbyte cut development time in half and enabled dynamic customer experiences."

Chase Zieman

“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”

Rupak Patel
"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
Before you begin, ensure you have access to both ClickHouse and Google Cloud. Install necessary tools like `clickhouse-client` for accessing ClickHouse and `gcloud` CLI for interacting with Google Cloud. Also, ensure Python is installed on your system for scripting purposes.
Use the `clickhouse-client` to run SQL queries and extract data. You can use a command like:
```bash
clickhouse-client --query="SELECT * FROM your_table" --format=JSON > data.json
```
This command exports data from ClickHouse to a JSON file. Adjust the query as necessary for your specific dataset.
Since Google Pub/Sub accepts messages in JSON format, ensure the data extracted is in the correct format. If necessary, write a Python script to parse and clean the data file:
```python
import json
with open('data.json', 'r') as file:
data = json.load(file)
# Process data if needed
```
Use the `gcloud` command-line tool to authenticate and configure access to your Google Cloud project:
```bash
gcloud auth login
gcloud config set project your_project_id
```
Ensure you have the necessary permissions to publish messages to Pub/Sub.
If you haven�t already created a Pub/Sub topic, do so with the following command:
```bash
gcloud pubsub topics create your-topic-name
```
This topic will be where you publish the data messages.
Create a Python script to read the JSON data and publish it to your Pub/Sub topic. Use the Google Cloud Pub/Sub client library:
```python
from google.cloud import pubsub_v1
publisher = pubsub_v1.PublisherClient()
topic_path = publisher.topic_path('your_project_id', 'your-topic-name')
with open('data.json', 'r') as file:
data = json.load(file)
for record in data:
message = json.dumps(record).encode('utf-8')
publisher.publish(topic_path, data=message)
```
Run your script and monitor the process to ensure all messages are successfully published to Pub/Sub. You can do this by running the Python script:
```bash
python publish_to_pubsub.py
```
Check for any errors in the script execution and verify message delivery in the Google Cloud Console.
By following these steps, you will be able to move data from ClickHouse to Google Pub/Sub without relying on third-party connectors or integrations.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
An open-source database management system for online analytical processing (OLAP), ClickHouse takes the innovative approach of using a column-based database. It is easy to use right out of the box and is touted as being hardware efficient, extremely reliable, linearly scalable, and “blazing fast”—between 100-1,000x faster than traditional databases that write rows of data to the disk—allowing analytical data reports to be generated in real-time.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey: