DEV Community

Discussion on: Why Paying For Something You Can Get For Free?

Collapse
byrro profile image
Renato Byrro • Edited on

I can say about my experience with AWS. I have multiple sites hosted there in a similar fashion to Netlify using S3 & CloudFront. When I need anything dynamic, I can easily attach Lambda for computing, DynamoDB for persistence, SQS for queuing, all serverless.

Haven't tested Netlify, their pricing page scares me away:

If you need SLA (as probably all professional sites do), Netlify costs $500. AWS gives that for free.

If you collaborate with co-workers, Netlify costs $45 (for only 3 users), AWS IAM provides multiple users for free and a fine grained access control logic.

If you need premium support, Netlify costs $500, while on AWS you can get support for few dozen bucks.

Global CDN is free by default on AWS CloudFront (pay-per-use), but costs $500 on Netlify.

I could go on here, but you get the idea: anything a little more advanced than what a personal website needs is free on AWS and very expensive on Netlify.

So, I ask you: why would someone pay Netlify when it's free on AWS? I guess people like how it works, find it easier to work with... I don't know...

Apart from financials:

AWS also offers private repo, CI/CD, infra-as-code, everything for free and in one place. It's not just Netlify that offers that type of deployment experience.

And sometimes it's better to have everything in one place. If you use a DB service in AWS, for example, hosting your site there can make more sense.

Collapse
bayuangora profile image
Bayu Angora Author

Thanks for response. I think AWS is better choice for pay per usage too. By the way, how about free monthly bandwidth of AWS compared to (100gb free monthly bandwidth) of Netlify?

Collapse
byrro profile image
Renato Byrro

AWS offers 50 GB/mo free only for the first 12 months. Then pricing depends on the region you deploy. In the US & Canada, 100 GB will cost you around $8.