

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."
Ensure you have access to a CockroachDB client that allows you to execute SQL queries. You can use the `cockroach` command-line tool or connect through a SQL client like DBeaver. Verify your connection and permissions to read the data from the required tables.
Write SQL queries to extract the data you need from CockroachDB. Focus on selecting only the necessary columns and filtering rows to minimize data transfer. Export the data into a CSV or JSON format using the `cockroach sql` command or any SQL client capable of exporting query results.
Transform the extracted data into a JSON structure compatible with Elasticsearch. If your data isn't already in JSON format, you will need to convert it using a script or tool like `jq`. Ensure the JSON structure matches the Elasticsearch index mapping you plan to use.
Before importing data, define an index in Elasticsearch that matches the structure of your data. Use the Elasticsearch API or Kibana to create an index with the appropriate mappings. This step ensures that the data types in Elasticsearch match those from CockroachDB.
Create a script in a programming language like Python, Node.js, or Java to automate the data insertion into Elasticsearch. Use libraries such as `elasticsearch-py` for Python or `elasticsearch` for Node.js to interact with the Elasticsearch API. The script should read the prepared JSON data and use the bulk API for efficient data ingestion.
Run the script to transfer data from the prepared JSON files to Elasticsearch. Monitor the process for errors or failed records. If the dataset is large, consider breaking it into smaller batches to reduce memory usage and potential timeouts.
After the transfer, verify that the data has been correctly indexed in Elasticsearch. Use the Elasticsearch API or Kibana to query the index and check for data integrity and completeness. Ensure that all fields are correctly mapped and that no data is missing or corrupted.
Following these steps will help you efficiently move data from CockroachDB to Elasticsearch 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.
Self-proclaimed “The most highly evolved database on the planet,” Cockroachdb helps businesses “scale fast,” “survive anything,” and “thrive anywhere.” Cockroachdb makes it easy for businesses to scale their database quickly and automatically and can be used across multiple cloud platforms or hybridized across clouds and on-prem data centers. They service all sizes of brands, including major companies such as Bose, Comcast and Equifax, providing easy backup, multi-platform deployment, and secure and scalable data storage and retrieval.
CockroachDB gives access to a wide range of data types, including:
1. Structured data: This includes data that is organized into tables and columns, such as customer information, product details, and transaction records.
2. Unstructured data: This includes data that does not have a predefined structure, such as text documents, images, and videos.
3. Time-series data: This includes data that is collected over time and is typically used for analysis and forecasting, such as stock prices, weather data, and sensor readings.
4. Geospatial data: This includes data that is related to geographic locations, such as maps, GPS coordinates, and address information.
5. Machine-generated data: This includes data that is generated by machines and devices, such as log files, system metrics, and IoT sensor data.
6. User-generated data: This includes data that is created by users, such as social media posts, comments, and reviews.
Overall, CockroachDB's API provides access to a wide range of data types, making it a versatile and powerful tool for developers and data analysts.
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: