not sure how this differs with AWS, you can do more at less cost than Vercel
Consider Image Optimization. In this post, there's a `/_vercel/image` URL made available to send an image and return it compressed with a format like `.webp`, if possible based on the browser.
With AWS, this would be a combination of S3 (store images), Lambda (compute the image transformations), Cloudfront (CDN), and Route53 (DNS). With the Build Output API, the entire infrastructure is defined by a JSON object (similar to Terraform). I do think the AWS CDK and Copilot[2] are making infra-as-code easier, but infra-as-filesystem[3] is an interesting twist.
[1]: https://vercel.com/blog/build-output-api
also I'm not sure if I'm alone in this but I set up everything through the web console and then generate CDK or Terraform.
I haven't built anything big on Vercel, but from my test drive, I'd be happy to use them in the future, and this is coming from someone who works AT the A in AWS. AWS does NOT make the easy things easy; though you are right, it does make the "more" possible, but it all depends on what you're optimizing.
In what world does a 11 person team qualify as an Enterprise? Though pedanticism aside, my problem is more with the opaque pricing than the naming.
Now it's not fully baked yet. DNS configuration is broken if you want to use your own domain (see https://github.com/aws/apprunner-roadmap/issues/37 and https://github.com/aws/apprunner-roadmap/issues/65 ) but you can get around that by putting cloudFront in front with just a few more clicks (and you get the benefit of having some of your files cached if you want).