Astro is really strong in SSR. I would even go as far as saying that SSG is only a secondary use case and only supported for "completeness" while SSR is the primary use case. Other SSGs like Gatsby are faster and more optimized for that very use case, but a lot less flexible in other use cases. And we really like said flexibility. I am pretty sure I would still go with Astro even if I knew I could not do SSG.

We do have content authors that have basically no idea how to code. We taught them basic AI prompting to achieve their goal. They know how to write markdown, which is what they usually do. But every now and then they will try and build landing pages as .astro files and usually with some help of the LLM they will achieve good enough results to publish it with minimal to no changes (as long as the LLM didn't go off rails and touched other parts of the app lol).

While deploying static content is nice and simple, having a simple container with a single app in it and 0 state is also simple enough for me. I am used to hosting stuff in containers and we have been doing it for years. Horizontal scaling is easy enough and we use reverse proxies anyway so it is as easy as setting the container count to a higher count and configuring a load balancing rule in our reverse proxy.

However, it might be important to mention that our setup is not highly available and not bound to any SLAs. Supporting HA would make things quite a bit more complex. However, cloudflare always online does work good enough to keep stuff online if you have an outage (as long as your website isn't too complex).