To expand on that, you can build this tooling out internally and many teams do. They just have a team dedicated to building and maintaining something like Seed internally.

What we bring to the table (aside from being more cost effective than staffing for this), is that when we solve an issue for one of our users, it gets solved for everybody else that's using Seed.

In fact, that's how we solved some of the issues around "reliably deploying a large number of serverless services together". One of our users was running up against some errors related to this and we worked with them to figure out the issue and fix it for everybody on Seed.