Render

Has projects running perfectly on Render but finds it gets expensive when load balancing, since each instance costs the full plan price, and Redis prices hiked.

“Render is perfect for smaller projects like a worker endpoint or something but gets expensive quite quickly when you need to load balance concurrent connections.”

Gave up on Render after it started charging 19 a month per person on team plans, even with a single person.

“Render charges 19$ for every person every month if you use a team plan, even the team has only one person. Of course that doesn’t include the server cost. It’s”

Uses Render as the best option, easy to deploy with database and Redis options and easy to scale.

“We use render.com it’s the best IMO. Easy to deploy, has database and redis options and easy to scale and can start for free”

Render’s change that charges single-person teams was annoying, but after contacting them they gave a year free on the team plan.

“I agree. It's an annoying change. I spoke with them about it and they gave me a year for free on the team plan”

Calls Render their favorite hosting site by a massive margin, running 14 and later nearly 20 services on it for two years with zero issues.

“my favorite hosting site by a massive margin - and i've tried everything. 14 services/sites hosted on render atm including my storage and mailing service.”

Has been very happy at Render but finds costs add up for many small apps, with 7 dollars per app and per database and a 20 dollar Pro tier, so is switching to Railway.

“someone who has been very happy at render.”

Has had zero problems with Render for hobby projects.

“Had 0 problems with render for hobby projects.”

A simple API function would not run on Vercel but ran fine on Render, which also handles their cron jobs and databases alongside the web deployment, so they stick with Render.

“I had a simple API function that just wouldn't run in Vercel but ran just fine in Render. No idea why. Add to that, I can handle cron jobs and”

Has used Render for over a year, loved it, and had a good customer service experience as well.

“I’ve used Render for over a year and have loved and had a good customer service experience as well”

Uses Render with a cron job to keep the free instance alive and has been enjoying the experience so far.

“i use render and cron-job to keep it alive - been enjoying the experience so far”

Uses Render and has had a good experience with no surprises, noting a recent one-click CDN option.

“+1 for Render. This is what I use and I have had a good experience with no surprises.”

Migrated a hobby project to Render but finds the 15 minute timeout annoying and the jump to the first paid plan big.

“Migrated my hobby project. Thank you.”

Loves Render, scaled a company on it over almost four years, and is choosing it again for their new job.

“Love Render. Scaled a company over almost 4 years on it.”

Found Render quick to switch to but suffered big Redis and Postgres outages, a four-hour deploy outage, unpredictable autoscaling and costs near Vercel prices (about 2,000 dollars a month), so plans to move to GCP.

“Render is alright - switching to Render was quick, and scaling out was fairly easy.”

Uses Render for the frontend and most of the backend, only putting an always-running process on DigitalOcean.

“I know it's not in the list, but I use Render.”

Switched a backend from Vercel to Render after CORS configuration trouble and so far likes it.

“switched to render cloud services for the backend and so far I like it.”

Moved a slow OpenAI chatbot to Render, which charges by compute time so requests can take as long as needed.

“Render! I had the same sort of issue.”

Found Render a bit unreliable for an API, with downtimes when there was no activity.

“Render to be a bit unreliable, with downtimes when there”

Has loved Render so far because they always know what they will spend every month.

“loved Render so far.”

Deploys a Next.js app on Render and is pretty happy with it so far.

“Using Render to deploy my Next.js app.”