Second question. Seed looks very nice and SST docs overall look very high quality. Particularly impressed by the bit on apigw and cors which helped me out a lot. But you're just a startup. If we get hooked on seed and it fails (as a business), what's our escape hatch / fall back plan ? Do we have generated cloudformation templates we can fall back on ?

SST has no dependency on SEED for deployments. You could configure a custom build process on a CI/CD service of your choosing. The reasons to choose SEED instead of other providers are as follows: 1. To support an organisation financially and socially that made something like SST. 2. SST projects, under certain limits, build for free on SEED. 3. SEED just raised $1M in funding. 4. SEED has features to monitor your lambdas and report issues to you via emails/slack. 5. Since, SEED is a small group of very talented people and not an enterprise their development decisions won’t be marred by business decisions. I am hoping that this would stay the same even when SEED goes big. These points are valid enough for me to trust SEED and rely on SST that’s open source.

Really appreciate the support @Ashishkumar Pandey! The one thing I’ll add @Justin is that if SEED goes down, you can continue deploying as is. It’s deploying on your behalf and you are not locked into using it.