Render.com looks like [1] their "$0 + compute costs" plan would work out to:
∙ $25/mo for a single "Web Services" box of 1 CPU and 2GB RAM
∙ $20/mo for a single "PostgreSQL" box of 1 GB RAM, 1 CPU, and 16GB SSD
∙ TOTAL: $45/mo, and you're assuming they'll magically give you zero-downtime
Those are grim numbers, performance-wise, but let's use them as the standard and see what it'd cost in the scrappy AWS architecture I threw together in a few minutes: ∙ $12.10/mo for a single t4g.small box, which is actually 2 vCPU and 2GB RAM [2]
∙ 3x redundancy on that brings you up to $36.30/mo for compute
∙ $16.20/mo for an ALB [3]
∙ $11.52/mo for a single db.t4g.micro PostgreSQL box, plus $1.84/mo for the equivalent 16GB of storage [4]
∙ TOTAL: $65.86/mo for substantially more CPU, redundancy, and control, or...
∙ TOTAL: $41.66/mo for substantially more CPU and control over your infra, if you're willing to drop the redundancy
So it looks like it's pretty comparable in terms of raw dollars.I'll admit there's a little more "devops" overhead with the AWS setup. Though I think it's not as big of a deal as people make it out to be — it's basically an afternoon of Terraforming, and you'd probably spend an equal or greater amount of time digging through Render's docs to understand their bespoke platform anyway.
(Also, once you contemplate bulk pricing for the underlying commodities, it's easy to see how companies like Render make a healthy margin, even on their low-end offerings.)
Anyway, I guess I've nerd-sniped myself, so I'd better stop here. But that was a fun analysis!
[1] https://render.com/pricing#compute
[2] https://aws.amazon.com/ec2/pricing/on-demand/
[3] https://aws.amazon.com/elasticloadbalancing/pricing/
[4] https://aws.amazon.com/rds/postgresql/pricing/?pg=pr&loc=3