Is there any plans to develop data models for supported integrations for reporting purposes? Fivetran releases dbt packages for common sources as Stripe (https://hub.getdbt.com/fivetran/stripe/latest/) because the extracted data is usually not suitable for reporting.

That’s a great question! At the moment, we’re working hard on the Extraction-Load challenges with connectors and get the data. in the destinations. If you have feedback on the format of the extracted data and think it should be further transformed for reporting usage, we’ll be glad to hear more about it What use case do you have in mind? Is there something stopping you from using the linked dbt packages on top of stripe data extracted with Airbyte for example?

The ultimate goal is to build one-click integration for Airbyte sources at rakam.io. Since we support dbt as our native data modeling language, we can suggest our users to use Airbyte and leverage the dbt project in order to analyze their source data seamlessly. We do have the integration with Segment and Fivetran but as Airbyte already makes use of dbt internally, the integation would be much easier IMO. https://rakam.io/blog/rakam-now-supports-dbt-as-data-modeling-layer/

So having a “Integrate your GIT repository” button in Airbyte would solve your concern there too?