How Airbyte Grew on GitHub: Three Funding Rounds in 2021

The first alpha connected Stripe and Postgres

The airbytehq/airbyte repository opened on 27 July 2020. Its first alpha, published on 24 September, listed Stripe and Postgres as sources, with BigQuery and Postgres as destinations. It also included scheduled syncs, logs and monitoring.

These connectors moved data between systems. A team could copy its Stripe payment data into BigQuery for analysis rather than write and maintain that integration itself.

At the end of 2020, the README described "the new open-source standard to sync data from applications, APIs & databases to warehouses."

By its seed announcement on 2 March 2021, Airbyte reported 50 connectors, including 10 contributed by its community. It also reported that 600 companies had replicated data with the product in the preceding four months.

The biggest star month included a public launch

Of the repository's stars still present when we collected its history on 22 October 2026, 4,371 date from 2021. January accounts for 857, the most of any month that year. The seed announcement came in March, the Series A in May and the Series B in December.

January was also a month of publicity. Airbyte launched on Hacker News on 26 January, the same date as a TechCrunch article about the platform. In the daily star history, 614 of January's 857 stars fall in the six days from 26 to 31 January. The timing puts the peak in launch context, though it cannot tell us where each person discovered Airbyte.

May was the second-largest star month, with 551; 379 fall between the Series A announcement on 25 May and the end of the month. December, the month of the largest round, accounts for 383: fewer than half of January's count.

GitHub star history for airbytehq/airbyte, collected on 22 October 2026. Removed stars are not counted, so this is not a reconstruction of the totals displayed in 2021.

These dates establish the sequence, not what caused people to star the repository or investors to fund the company.

Airbyte started building tools for connector builders

The repository added Connector Development Kit scaffolding on 29 April 2021. Publishing infrastructure followed on 3 May.

The toolkit supplied reusable code for building connectors. A developer integrating another HTTP API could use that structure rather than start from scratch. Its year-end README described "a framework for rapidly developing production-grade Airbyte connectors."

In its 25 May Series A announcement, Airbyte reported more than 70 connectors and said roughly 20% came from the community. It had also begun work on Airbyte Cloud for companies that did not want to install and operate the software themselves.

A community-built connector could let other teams connect the same data source without writing the integration again. The toolkit gave contributors a common structure for that work. A larger catalogue meant more integrations were available, though the count alone could not establish their reliability or usage.

Three rounds backed the expansion

Airbyte's three 2021 funding announcements totalled $181.2 million. The Series B valued the company at $1.5 billion.

These are the dates of Airbyte's own announcement posts, not necessarily the closing dates or first press coverage. Its later fundraising account says the seed closed in February.

By the end of 2021, the README's description had expanded from syncing data to warehouses to syncing it to "warehouses, lakes & other destinations."

The Series B pitch separated deployments from repeat usage

Airbyte published a walkthrough of its Series B deck in January 2022. Co-founder John Lafleur wrote that the presentation was lighter on revenue reporting because Airbyte Cloud was only entering private beta. It focused instead on community and usage metrics, alongside the company's plans.

The walkthrough distinguished several kinds of adoption:

• Deployments: installations of the software.
• Activated companies: companies that had successfully synced data.
• Production users: users syncing more than once a day over several weeks, under Airbyte's definition.

The pitch also discussed the amount of data moved. Together, these measures distinguished installing the software from using it regularly.

Airbyte also spoke with activated users who had stopped using the product. It said most of those users wanted Airbyte Cloud so they would not have to host and operate the software themselves. The company described Cloud as a way to increase adoption, rather than a strategy for increasing revenue.

The walkthrough explains what Airbyte presented to investors; it does not let us independently audit the customer usage behind those slides.

Building connectors and using them were different measures of progress

The public record shows an alpha with a few integrations, then a toolkit for developers to build more. The company's announcements report community contributions, while the star history records interest strongest in January, the month of its Hacker News launch.

Airbyte's pitch tracked whether companies had successfully synced data and whether users kept syncing it. Neither GitHub stars nor the number of available connectors establishes that kind of regular use.

How we measured this

• Scope: the repository's launch in 2020 and the three funding announcements in 2021. This is not a complete funding or product history through 2026.
• Stars: GitHub's repository star history API, collected on 22 October 2026. We grouped its daily counts into calendar months using the returned week timestamps and day offsets. GitHub does not guarantee that these boundaries align with UTC. The API counts stars still present, excluding stars subsequently removed; it does not count product users.
• Repository history: GitHub's repository metadata, the first alpha release, dated commits and README snapshots pinned to specific commits, linked above. Repository creation, release and commit dates use UTC.
• Funding and adoption: Airbyte's announcements and published pitch walkthrough. Connector shares and usage figures are attributed to the company. We do not equate community-built connectors with distinct contributors, employees or customers.