HNHacker News
TopNewBestAskShowJobs

jeanlaf

322 karma · joined September 3, 2016

submissionscomments
jeanlaf··on The deck we used to raise our seed funding
Will try to find some time for that. Will post it on HN, if I do
jeanlaf··on The deck we used to raise our seed funding
We're a pretty transparent company, so we published our strategy and future business model. You can find it here: https://docs.airbyte.io/company-handbook/business-model

Let me know if you have any questions on it!

jeanlaf··on The deck we used to raise our seed funding
Sorry about that. Hope your fundraise was still successful. Don't hesitate to reach out to john [at] airbyte.io, if we can help.
jeanlaf··on The deck we used to raise our seed funding
Thanks!
jeanlaf··on The deck we used to raise our seed funding
Ah ah! We liked this diagram, because it explained how the product works. Also, we already used our own infographic on the cover page (https://airbyte.io/wp-content/uploads/2021/03/Airbyte-Seed-D...), so we needed something different.

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.

jeanlaf··on The deck we used to raise our seed funding
There are 3 ways we got connections:

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.

jeanlaf··on The deck we used to raise our seed funding
So within 2 weeks, we met with 45 investors (76 calls in 7 days, that's our record ;) ). Our goal was to identify the 10 VCs that understood the best our vision and industry and that could bring the most value.

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.

jeanlaf··on The deck we used to raise our seed funding
No limits. Full remote :)
jeanlaf··on The deck we used to raise our seed funding
We are :)! Don't hesitate to apply: https://docs.airbyte.io/career-and-open-positions/senior-sof...
jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
Very true. We're thinking about offering some kind of volume-based for small companies but with a limit that we won't go over. There are some solutions and we will try to offer the pricing the most adapted to the needs of our users. It will be an iterative process for sure!
jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
Sure, we do: https://github.com/airbytehq/airbyte/issues/new/choose
jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
Thanks!
jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
Yes, indeed, we do. This should come within the next 3 months. Here's the issue if you want to keep track of our progress on the matter: https://github.com/airbytehq/airbyte/issues/768
jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
Yes, we'll definitely be looking at having an Amplitude source connector, the issue is already here: http://github.com/airbytehq/airbyte/issues/1457
jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
Yes we do. You can check our connectors here: https://docs.airbyte.io/integrations
jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
The pricing depends on the number of connectors you need (but not the volume of data), the features you use, and the SLA. We already saw that there was a great willingness to pay, so we’re not really worried about that part. We will learn a great deal about that next year. Our sole focus in 2021 is the open-source part of the project, and becoming the new standard to replicate data.

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.

jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
Sure! Those are actually great questions!

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.

jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
This is something we will definitely offer as well, with an SLA. And because the maintenance is not only done by us, but the community as well, fixes will be propagated throughout all users much faster than if it has to go through customer support.

Open-source doesn't mean you can't have both. You can check how Databricks or Confluent are doing.

jeanlaf··on Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
The main difference is that Meltano is based on Singer while Airbyte is based on the Airbyte Protocol.

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...

jeanlaf··on Airbyte: Simple and extensible open-source EL(T)
In all honesty, in that particular case, we'd honestly think about merging it. If that happens, we're facing 2 options. Either we merge it, and at that point the real business model for our business is about hosting, management, support, SLAs, etc. Or we don't, and that contributor could very well publish it in another repo. And then, what's the point?

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.

jeanlaf··on Airbyte: Simple and extensible open-source EL(T)
(Airbyte engineer) Agreed. Thanks for notifying us about that. We fixed it. We started by supporting only full refresh at the very start, as it was easier to support more connectors, but have been ramping up incremental across all the sources for a month now. Incremental should be supported for all sources within a few weeks.
jeanlaf··on Don't measure developers, measure projects
Completely agree! Love the quote "Code is a liability. Functionality and business value are assets."
jeanlaf··on Don't measure developers, measure projects
Indeed. Plus, I would add that measuring the outcome (definitely a must-do, not arguing on this) is more about the product. The article was more focusing on metrics for the engineering organization, how it performs as a team. Could you say that your engineering organization is collaborating effectively, only based on the outcomes?
jeanlaf··on Don't measure developers, measure projects
Thanks for the book recommendation! Will definitely read it :).

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...

jeanlaf··on Don't measure developers, measure projects
Fixed!
jeanlaf··on Don't measure developers, measure projects
Oh let me check this! Sorry about that.
jeanlaf··on Show HN: How to start a business in France
Have been working in San Francisco for 6 years. Actually, contrary to what you believe, there are approximately the same rules. You cannot fire people in the US without reason too.
← PreviousPage 3 of 3