https://blog.prequel.co/introducing-prequel-shifting-the-etl-paradigm-26cb26d6e1c1 Here's another one re https://meltano.slack.com/archives/C01NPCGEL48/p1663345576456689?thread_ts=1663345576.456689&cid=C01NPCGEL48 , vendors do have a great option, write a tap, offer meltano in your product :)

vendors do have a great option, write a tap, offer meltano in your product 🙂

💯 I think it’s more reasonable for vendors to build their own connectors to an open standard, just like they often publish API client libraries for Python, JavaScript etc, than to tie themselves to a specific proprietary tool for their data exports.

Best of both worlds, they support what they know (their tap), the targets are supported by a community and are open source. Hosting of the taps/targets can be handled N number of ways, vendor could do it, vendor could have anyone do it, client could host it etc etc

@matt_chudoba Curious to hear your thoughts on this as Postscript is a launch partner for Prequel! Do you think there’d be interest in collaborating on an official tap-postscript? Users could then use that with their own Meltano (or any other Singer-compatible tool), or you could even run Meltano for them and just have them connect their destination (although I’m sure Prequel makes that much easier).

that sounds like a really cool idea! there is definitely an appetite at Postscript to build out a more robust and customizable platform for our customers to sync our data with them. I think using Singer as an approach would be great. we already have a public API accessible, but not necessarily for syncing data (yet). we will definitely look at using Singer/Meltano as an approach, whether it’s a public tap or something we do behind the scenes for customers