322 karma · joined September 3, 2016
Let me know if you have any questions on it!
Regarding the differences between Airbyte and Fivetran, here's an article about it: https://docs.airbyte.io/faq/differences-with/fivetran-vs-air...
But essentially, open-source enables us to:
- address the long tail of integrations (our goal is 200+ by end of 2021) - we're working on a low-code/no-code framework to make it easier to build and maintain connectors
- give you flexibility/customizability to adapt pre-built connectors to your needs
- debugging autonomy (we're standardizing how connectors are being built, so maintenance can be done by us and the community)
- No more security and privacy compliance, as self-hosted and open-sourced (MIT)
- No more super high prices (volume-based) that don't make sense for big data companies.
1) We did have some intros thanks to being a YC company. That definitely helped.
2) For some funds for which we really wanted intros, we asked our investors.
3) We timed these 2 weeks of fundraising to happen 2 weeks after some important product release for us (0.2.0). And we did get some inbound from investors (them reaching out to us).
Also being at the crossroads of data infrastructure and open-source helped a lot, as both are important topics for investors right now.
We tried to keep the meetings with the funds that we liked most at the end. For instance, Accel was the 42nd investor we met with.
On those investors, you could see that 50% didn't know much about data infrastructure, or that it was a fresh topic for them. But for the 10 funds we liked best, they knew A LOT, invested in it, brought a lot of insight and value, just by interacting with them.
So for the next round, we will mostly focus on those 10 funds, keep them posted on our progress, so that the next round is just a question of when and how.
In terms of negotiation, I would say we had a lot of interest, so we could have negotiated the valuation higher, but for us, it was more a question of who we wanted to work with.
But will try to write a blog post on the process for more details, if you think that could be useful.
Regarding cloud providers as AWS, there are several things we can do to monetize this part with them (including with “Powered by Airbyte”). But, honestly, that would be a great problem, as it would indicate that we’ve become the standard way to replicate data.
Regarding monetization, you can see more details here: https://airbyte.io/pricing We consider 2 monetization approaches: Open core (connectors staying open-source forever) with premium features as: hosting & management (cloud-based control panel without access to your data plan), and enterprise features (privacy compliance, SSO, user access management, etc) What we call “Powered by Airbyte” where we enable you to offer integrations to your own customers using our API
Regarding our runway, with the team as is, mid 2025. We intend to grow the team though, given the adoption growth we have. We’ve already been approached for a Series-A, but will consider it in mid 2022.
Regarding self-sustainability, do you mean financially? Possibly at the end of 2023 or 2024.
How does that sound to you? Genuinely curious.
Open-source doesn't mean you can't have both. You can check how Databricks or Confluent are doing.
We don’t believe Singer is a good building block, because it requires a significant time investment from its users to compensate for the absence of centralized enforcement of the Singer protocol. Since it is not enforced, there is often no guarantee that any pair of Singer connectors are compatible. It defeats the point of a specification. All taps live in their own repo, and all contributions are made to address the contributor’s case, not the general use case. The lack of standard makes it very difficult to maintain all those connectors, and you end up with a majority of Singer taps being out of date.
Airbyte doesn’t have the same data protocol as Singer (but we are compatible). Our goal is to make building and maintaining new connectors a lot easier than it is with Singer, and therefore Meltano. That’s why we were able to ramp up our connectors (46 now) within just 5 months, while Meltano is focused on fixing the issues with Singer. We think it’s much harder to patch over Singer and reverse course on an abandonware project than it is to start from the ground up with these issues in mind. We wouldn’t be surprised if Meltano starts supporting Airbyte connectors in the future.
We detail these differences here: https://docs.airbyte.io/faq/differences-with.../meltano-vs-a...
We call this type of business model open core. It is the same one as Confluent or DBT. Without those companies, there would have been nobody to create those open source projects and get them to a place of value for a maximum number of companies. Kafka's impact goes well beyond Confluent's customer base. Similarly, our goal is to solve the data integration problem for every company or project, even if we only convert a small % of them as customers for us. That's why we won't be focusing on any premium features for at least a year and possibly 2. Hope that makes sense to you.
Concerning Gitprime, I completely agree with you. And they do say that the point is to game their metrics: https://help.gitprime.com/general/cant-you-just-game-the-met...