Hey, thanks for the kind words, and for the idea! Bridgy is indeed busy, but it’s had time to evolve a pretty scalable architecture, so load isn’t really a problem. Some details here, including costs. I actually increased its poll frequency the other day, which doubled its load, and it’s still fine.

(I do love GitHub Actions! But it’s more for CI, CD and other heavy, infrequent, repo-based tasks. Bridgy’s task volume is much higher, and the tasks themselves are lighter, so its current task queue probably fits better.)