Recently I needed some really infrequently executed background workers. Basically just generate a CSV from our DB, email it somewhere. Historically I'd setup a Redis backed worker queue for background jobs. However, right now the aforementioned job is my only background processing requirement and it's massively overkill since serverless is supposed to take care of the infra headache for me. What I found was a surprising amount of BS to get serverless runners doing what you want - there's execution limits, trigger limits, terrible developer experiences (depending on the platform) etc. If you're already invested in a serverless ecosystem, this isn't a huge deal, but for the odd one-off task, the current options are kind of terrible. Supabase edge workers for example are way too limited for this use case. Cloudflare Workers (with the queuing stuff in beta) are probably the best option. But your batteries included approach seems super appealing for this kind of stuff. That said, I think you're in for a hard time marketing this. It requires devs to have "learnt the hard way" before they understand your value proposition.