The ELT market has a clean split. Managed services like Fivetran sell reliability for the connectors they support and charge accordingly, and you have no recourse when your source is not on the list. Airbyte sells the opposite proposition: a large catalogue including a long tail nobody else maintains, plus the ability to build your own connector when even that is not enough. Whether that trade is worth it depends almost entirely on whether your sources are mainstream, and the documentation is the place you find out.
The connector builder is the part I would push anyone toward. It is a low-code interface for defining a source connector by specifying authentication, pagination, request structure and response parsing declaratively, and the tutorials walk through it properly. The skill is more valuable than it looks. Every data team eventually hits a source, an internal API, a regional vendor, a system too obscure to have a commercial connector, where the choice is a hand-written ingestion script that becomes somebody's permanent maintenance burden or a connector built in a framework that handles retries, incremental state and schema evolution for you.
Learning to build one in an afternoon is a genuinely useful capability and it is the clearest argument for Airbyte's existence. It is also, and this is my main complaint, taught as documentation rather than as a course. There is no Airbyte academy, no structured curriculum, no certification. The material exists and it is scattered across quickstarts, concept pages and tutorials in the order the documentation site happens to present them.
For a capability this specific and this differentiating, a proper course would serve both the learner and the company better than another documentation page. The licensing needs a careful read and the docs do not help enough. Airbyte operates a dual licence, MIT for some components and Elastic License v2 for others, and the footer links the licence documents without explaining which applies where. ELv2 is not an open source licence by the OSI definition.
It prohibits providing the software to third parties as a managed service and prohibits circumventing licence key functionality. For most teams running Airbyte internally that restriction never bites. For anyone considering embedding it in a product or offering it to customers, it very much does, and the distinction deserves a clear page rather than two links. I would apply the same standard I applied to ScyllaDB's licence change: the arrangement may be entirely reasonable, and learners should be told plainly what they are adopting.
Connector quality is the operational reality that the documentation soft-pedals. The catalogue includes connectors maintained by Airbyte to a commercial standard and connectors contributed by the community with varying levels of ongoing attention. Certification tiers exist and are visible, and a team that does not check them will eventually build a production pipeline on a connector that was last updated when the upstream API had a different version. The docs mention support levels.
They do not adequately convey that choosing a connector is a due diligence exercise rather than a checkbox. Self-hosting is the other place where the gap between quickstart and reality is wide. Getting Airbyte running locally with Docker takes minutes. Running it in production on Kubernetes, with job scheduling, resource management, upgrade handling, secret management and monitoring, is a platform engineering project.
The deployment documentation is thorough and honest about the components involved, and the quickstart's simplicity still sets an expectation that the production path does not meet. Cloud pricing by data volume repeats the category's standard problem. Ingest is easy to start and the bill scales with something you are not watching, and nothing in the learning material teaches you to think about which sources are worth their ingestion cost. That is the same silence I have noted with observability vendors, and it comes from the same place.
Three point six. Documentation rather than teaching, hiding one genuinely valuable and specific skill in the connector builder, attached to a licence arrangement that needs a clearer explanation than it gets.