co-founder of Magic Patterns here, saw were were mentioned, figured I'd chime in:
We don't use Trigger for marketing at all and I actually never thought of it for that use case.
We're an AI design tool - prompt to create an interactive mockup - and we use Trigger to take screenshots of designs to provide a preview image. Taking a screenshot sounds easy, but it's not because Puppeteer constantly hits OOM errors. So you need a high-end machine, and so it can get expensive. We originally were using a homegrown solution, a microservice, but it would constantly crash (even though were paying $$$$$ for it).
Trigger spinning up jobs was perfect and we migrated in a day and now I never think about it.
Can you expand a bit on this use case? Why would Puppeteer constantly crash on your own high end machine, but not on Trigger's infra? Puppeteer doesn't care where it runs, so it would be nice to understand how Trigger's infra works around this problem.