hairyhenderson
You're in luck! :D
https://hub.docker.com/_/caddy
Note that the v2 images were _just_ pushed a few minutes ago, so the description might still point to rc3.
See "Adding custom Caddy modules" on that page for instructions on how to use the `caddy:builder` image.
My experience as a contributor has been nothing but positive. But if anyone's had a bad experience, I'm sure the Caddy team is more than willing to talk it out and reconcile.
Not in my experience... It's impossible to predict the kind of usage you're going to need over the next 1-3 years, especially when you're first getting started with AWS. If you underestimate, you waste money. If you overestimate, you waste even more money. Google's concept of "sustained use" discounts is _much_ more appealing to me.
As for which platform? IMO the most important factor is which platforms the developer(s) are most comfortable/familiar with. The last thing a new SaaS startup needs is to waste time while the engineers figure out a new platform they've never used... Doesn't really matter how easy or cheap it is to deploy if there's no product ready to deploy ;)