3 ms·

That's fantastic! I'll have to take a look. Thanks for showing me. I was aware of Heroku, but this seems like the modern equivalent which I had in mind. (I do t

by samhw 5y ago

That's fantastic! I'll have to take a look. Thanks for showing me. I was aware of Heroku, but this seems like the modern equivalent which I had in mind. (I do think you could likely go even simpler, though - there's a whole spectrum of complexity which could accommodate different services at each point.) Edit: Apropos of "there's a point in time where you'll need to evaluate other options": I think a good selling point would be a well-designed flow for 'ejecting' to a self-hosted or AWS/GCP environment. Yeah, yeah, it's not good for lock-in, but by the exact same token it would be a strong selling point. Done well, you could assuage the "we may as well get it out of the way now" concerns by saying that you'll make it easier to set up shop on AWS.

eropple 5y ago
You could go simpler than Render, and some folks do--but you go simpler at the cost of drastically reducing the value of a thing for whole categories of non-toy projects. For example, if you want to host a static thing there are a lot of pretty easy options, but the second you need something as foreign to the "JAMstack ideal" as "a datastore" like "for a blog with comments" now you're in multiple control panels and you're shuttling secrets around and you're confronted with paying multiple companies just to launch a blog and the whole thing physically hurts. Some mild complexity in deploy (and it is mild, a render.yaml file in your repo's super easy) comes from having the options to actually do things, I think.
cldellow 5y ago
I've been running a SaaS on Render for about a year now. In past lives, I managed ~$50k/mo of AWS spend for one company and $1k/mo of Heroku spend for another. Render's great for letting us just focus on the app. There are things I want them to improve, but I'm confident they'll get there eventually.
- anurag 5y ago
  Lots of improvements and additions planned for the coming months. Thank you for sticking with us.

by samhw 5y ago

eropple 5y ago

You could go simpler than Render, and some folks do--but you go simpler at the cost of drastically reducing the value of a thing for whole categories of non-toy projects. For example, if you want to host a static thing there are a lot of pretty easy options, but the second you need something as foreign to the "JAMstack ideal" as "a datastore" like "for a blog with comments" now you're in multiple control panels and you're shuttling secrets around and you're confronted with paying multiple companies just to launch a blog and the whole thing physically hurts. Some mild complexity in deploy (and it is mild, a render.yaml file in your repo's super easy) comes from having the options to actually do things, I think.

cldellow 5y ago

I've been running a SaaS on Render for about a year now. In past lives, I managed ~$50k/mo of AWS spend for one company and $1k/mo of Heroku spend for another. Render's great for letting us just focus on the app. There are things I want them to improve, but I'm confident they'll get there eventually.

anurag 5y ago
Lots of improvements and additions planned for the coming months. Thank you for sticking with us.