Yeh I still appreciate the callout / opinion though. It's not obvious to me who is best to target. As a full stack engineer with analytics experience one of the main uses of the tool is scheduling, running pipelines remotely vs the UI for data munging which I can write pretty easily. But for non technical users the data munging piece might be really helpful (e.g. no code). Its a little hard to serve both a marketer and a developer given the needs are so different. But then on the other hand I assume a marketer is more likely to pay for the tool (and thus keep it going) vs a dev who might be a harder sell. I built this tool with the hope of being able to serve both which is where maybe I bit off more than I could chew.

I actually use Stitch so I don’t have to host orchestration, which is how I came to know about Singer in the first place.

It’s true that Stitch got acquired by Talend, but Singer seems independent enough. I don’t understand why Stitch would “abandon” Singer. They’re a sponsor, and seems like they have an incentive to keep that ball rolling. Their bread and butter seems to be hosting orchestration, so more taps means more customers for them. There’s other stakeholders in Singer, too, like Meltano, and all the self-hosters.

The GitHub activity seems robust to me, but I don’t really have any in depth knowledge about the Singer community. Saying it’s “dying” doesn’t seem accurate, though.