

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."
First, pull the desired Docker image from Docker Hub and run the container. You can achieve this with:
```bash
docker pull
docker run
```
This step ensures you have the environment and data you wish to transfer available on your local system.
Access the running container to extract the data. Use the command:
```bash
docker exec -it /bin/sh
```
Navigate to the directory containing the data and use commands like `cat`, `cp`, or other utilities to prepare the data for transfer. If the data is in a file, you can copy it to your local system using:
```bash
docker cp :/path/to/data /local/path
```
Once you have the data on your local system, you need to format it according to Firestore's requirements. Typically, this involves converting it into JSON format. Use a script or tool to serialize the data:
```python
import json
# Example dictionary
data = {"key": "value"}
# Convert to JSON
formatted_data = json.dumps(data)
```
To interact with Google Firestore, you need to authenticate your requests. Set up a service account in Google Cloud Console with Firestore access and download the JSON key file. Set the environment variable:
```bash
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/your/service-account-file.json"
```
Use Python with the `requests` library to write a script that uploads the data to Firestore using its REST API. Example:
```python
import requests
# Firestore URL
url = "https://firestore.googleapis.com/v1/projects/YOUR_PROJECT_ID/databases/(default)/documents/YOUR_COLLECTION"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer " + "YOUR_ACCESS_TOKEN"
}
# Load JSON data
data = {"fields": {"key": {"stringValue": "value"}}}
# Send POST request
response = requests.post(url, headers=headers, json=data)
print(response.status_code, response.json())
```
Replace placeholders with your project details and access token.
Use Google OAuth 2.0 to get an access token for authorization. You can obtain this token via the `gcloud` command-line tool:
```bash
gcloud auth application-default print-access-token
```
Use the token in the authorization header of your HTTP requests.
Run your script to transfer the data. Verify the success of the operation by checking the HTTP response and inspecting the Firestore database via the console or another script that retrieves the data:
```python
import requests
url = "https://firestore.googleapis.com/v1/projects/YOUR_PROJECT_ID/databases/(default)/documents/YOUR_COLLECTION/YOUR_DOCUMENT_ID"
response = requests.get(url, headers=headers)
print(response.status_code, response.json())
```
This approach allows you to move data manually from a Docker container environment to Google Firestore, leveraging the REST API for a direct, hands-on transfer without third-party tools.
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.
Docker Hub is the world's easiest way to create, manage, and deliver your team's container applications. Docker Hub assists developers bring their ideas to life by conquering the complexity of app development. It can easily search more than one million container images, including Certified and community-provided images. Docker Hub gets access to free public repositories or choose a subscription plan for private ropes. It is entirely a trusted way to run more technology in containers with certified infrastructure, containers and plugins.
Dockerhub's API provides access to a wide range of data related to Docker images and repositories. The following are the categories of data that can be accessed through Dockerhub's API:
1. Repositories: Information about the repositories available on Dockerhub, including their names, descriptions, and tags.
2. Images: Details about the Docker images available on Dockerhub, including their names, tags, and sizes.
3. Users: Information about the users who have created and contributed to the repositories and images on Dockerhub.
4. Organizations: Details about the organizations that have created and contributed to the repositories and images on Dockerhub.
5. Webhooks: Information about the webhooks that have been set up for repositories and images on Dockerhub.
6. Builds: Details about the builds that have been performed on Dockerhub, including their status and logs.
7. Collaborators: Information about the collaborators who have access to the repositories and images on Dockerhub.
8. Permissions: Details about the permissions that have been set for repositories and images on Dockerhub, including read, write, and admin access.
Overall, Dockerhub's API provides a comprehensive set of data that can be used to manage and monitor Docker images and repositories.
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: