Data integration is made simple, secure, and extensible. The new open-source standard to sync data from applications, APIs & databases to warehouses, lakes & other destinations.
Airbyte is on a mission to make data integration pipelines a commodity.
- Maintenance-free connectors you can use in minutes. Just authenticate your sources and warehouse, and get connectors that adapt to schema and API changes for you.
- Building new connectors made trivial. We make it very easy to add new connectors that you need, using the language of your choice, by offering scheduling and orchestration.
- Designed to cover the long tail of connectors and needs. Benefit from the community's battle-tested connectors and adapt them to your specific needs.
- Your data stays in your cloud. Have full control over your data, and the costs of your data transfers.
- No more security compliance process to go through as Airbyte is self-hosted.
- No more pricing indexed on volume, as cloud-based solutions offer.
Here's a list of our connectors with their health status.
git clone https://github.com/airbytehq/airbyte.git
cd airbyte
docker-compose upNow visit http://localhost:8000. You will be asked for a username (default: airbyte) and password (default: password). You should update these values by changing BASIC_AUTH_USERNAME and BASIC_AUTH_PASSWORD in your local .env file.
Here is a step-by-step guide showing you how to load data from an API into a file, all on your computer.
- Built for extensibility: Adapt an existing connector to your needs or build a new one with ease.
- Optional normalized schemas: Entirely customizable, start with raw data or from some suggestion of normalized data.
- Full-grade scheduler: Automate your replications with the frequency you need.
- Real-time monitoring: We log all errors in full detail to help you understand.
- Incremental updates: Automated replications are based on incremental updates to reduce your data transfer costs.
- Manual full refresh: Sometimes, you need to re-sync all your data to start again.
- Debugging autonomy: Modify and debug pipelines as you see fit, without waiting.
We love contributions to Airbyte, big or small.
See our Contributing guide on how to get started. Not sure where to start? We’ve listed some good first issues to start with. If you have any questions, please open a draft PR or visit our slack channel where the core team can help answer your questions.
Note that you are able to create connectors using the language you want, as Airbyte connections run as Docker containers.
Also, we will never ask you to maintain your connector. The goal is that the Airbyte team and the community help maintain it, let's call it crowdsourced maintenance!
For general help using Airbyte, please refer to the official Airbyte documentation. For additional help, you can use one of these channels to ask a question:
- Slack (For live discussion with the Community and Airbyte team)
- Forum (For deeper conversations about features, connectors, or problems)
- GitHub (Bug reports, Contributions)
- Twitter (Get the news fast)
- Weekly office hours (Live informal 30-minute video call sessions with the Airbyte team)
Airbyte takes security issues very seriously. If you have any concerns about Airbyte or believe you have uncovered a vulnerability, please get in touch via the e-mail address security@airbyte.io. In the message, try to provide a description of the issue and ideally a way of reproducing it. The security team will get back to you as soon as possible.
Note that this security address should be used only for undisclosed vulnerabilities. Dealing with fixed issues or general questions on how to use the security features should be handled regularly via the user and the dev lists. Please report any security problems to us before disclosing it publicly.
Check out our roadmap to get informed on what we are currently working on, and what we have in mind for the next weeks, months, and years.
See the LICENSE file for licensing information, and our FAQ for any questions you may have on that topic.