Hey Matt - You hit the nail on the head with "Zapier for data/analytics engineering teams" and your example scenario. Our goal is to make it as simple as possib

Hey Matt - You hit the nail on the head with "Zapier for data/analytics engineering teams" and your example scenario. Our goal is to make it as simple as possible to get any quick data scripts up and running. However, we are positioning this as a tool where you can accomplish bulk ETL. The infrastructure is designed to scale for long-running jobs with heavy data usage. It's easier to demo and understand the "quick solutions", but we have teams running Fleets that download and process 100s of GBs of data every day. Agreed on the need to allow self-hosting the code. It's currently on our roadmap to build in native Github connections so that teams can host the code and version manage it there, connecting Shipyard as part of their CI/CD flow. Having to copy/paste the code, or upload it, is a means to an end right now, but not much different than the flow for something like AWS Lambda. As for Prefect, we've heard a lot of great things about their setup. However, there's a few areas that we find it lacking: - Python Only. We want to enable workflows that can connect solutions built in multiple different languages (which we support through Bash for now). - Infrastructure management is your responsibility, so you still might hit snags and resource constraints. - Their workflow as code setup requires you to change how you write your scripts to make them work in Prefect... and it's my understanding that all the steps of a workflow have to live in a single script. We're opting for a more modular approach, where code could easily be run on your local machine, or your own infrastructure, without needing to rewrite it. I'd love to get more feedback about your current setup and experience. Feel free to hit me up at blake[at]shipyardapp.com