Render

What do you like best about the product?

On Render, we split our system into Web Services, Private Services, Background Workers, and Cron Jobs, each with its own commands, environment variables, and resource settings. That kept us from cramming long-running work into the API just because it was already deployed, and it also let us scale the worker independently without paying for the same capacity on the frontend. Render also offers Static Sites, Workflows, and managed datastores in the same platform, but the Git-based deployment flow is what we depend on most. Pushes can trigger builds and deploys, and Zero-Downtime Deploys take a lot of the stress out of releasing web services, private services, workers, and cron jobs. Preview Environments have been especially valuable because they can recreate the resources defined in a Blueprint, not merely publish another frontend URL. For a checkout change, we were able to test the API, the worker, and a seeded database together before merging, instead of hand-maintaining yet another temporary environment. At this point, our render.yaml versions services, commands, regions, variables, and scaling rules alongside the repository, while Environment Groups prevent shared configuration from being duplicated across every service. The unexpected win is that the Blueprint has turned into solid architecture documentation: a new developer can read the file and quickly understand what runs where, without having to reverse-engineer the platform from a pile of dashboard screens.

What do you dislike about the product?

The plan boundaries start to show as soon as an application needs more than basic hosting. Features like autoscaling, Preview Environments, HTTP logs, and several organization-level controls are gated behind the Pro tier or higher. That feels reasonable for a small product running only a couple of services, but teams can outgrow the Hobby plan quickly once temporary environments, stronger observability, and shared access controls become part of everyday delivery. Render does remove a lot of operational overhead, yet the bill begins to reflect that convenience as the architecture becomes more mature and demanding.

What problems is the product solving and how is that benefiting you?

We built an import feature where users upload a CSV in the frontend, the API validates it, and then thousands of records get processed afterward. Our first implementation kept the HTTP request open until everything finished. It looked great with small test files, but it fell apart as soon as real data showed up. Larger imports started timing out, and a deployment could restart the process halfway through a job, with no clean way to explain what had already completed. We kept the frontend and API as Web Services, moved the heavy processing into a Background Worker backed by a queue in Render Key Value, and used a Private Service for an internal API that had no reason to be publicly reachable. A Cron Job cleaned up abandoned imports, while One-Off Jobs handled schema changes before deployment. The whole setup lived in a Blueprint, and Preview Environments let each pull request run the workflow against seeded data. That preview setup paid off quickly: the first preview caught a configuration mistake that local testing had missed. The worker was reading a different queue variable than the API, so jobs were being created correctly and then waiting forever for a consumer that was listening somewhere else. We centralized the environment configuration before going to production and added a health check around queue connectivity.

What do you like best about the product?

It has a great beginner price point and it effortlessly works with GitHub when connected to Replit so I can still update it.

What do you dislike about the product?

I have not found something wrong with it yet.

What problems is the product solving and how is that benefiting you?

Starting my website app service with a great price point and adaptable project migration from Replit to GitHub to Render.

What do you like best about the product?

What I like most about Render is how simple it makes deployments. Connecting a GitHub repository and having automatic deployments on every push saves a lot of time during development. I also like that databases, backend services, environment variables, and logs are all available in one dashboard, which makes managing multiple services much easier.

What do you dislike about the product?

The free tier limitations can occasionally get in the way for side projects and student work. Services may spin down after inactivity and resource limits can sometimes slow down testing and experimentation. Pricing also scales quickly once multiple services and databases are involved.

What problems is the product solving and how is that benefiting you?

Render helped me deploy backend APIs, databases, and supporting services without needing to manage infrastructure manually. Having automatic deployments, centralized logs, and managed databases allowed me to focus more on development rather than server configuration and maintenance.

What do you like best about the product?

I really enjoy how Render makes the infrastructure life cycle very easy to manage. It's got great visibility and is straightforward to set up, deploy, and configure using YAML files. The experience with domain management and environment variables is seamless, which is a dream for a back-end engineer like me. Render helps avoid the complexity and overload associated with platforms like AWS, GCP, and Azure. Switching to Render has been beneficial as it's faster, simpler, and doesn't require much human expertise. The initial setup process was smooth and seamless, and its intuitive UI makes it very easy to view and edit configurations.

What do you dislike about the product?

The pricing can get high if I need to scale something. I wish there was more visibility around why things cost the way they do. Since they're a reseller of clouds and provide the UX, understanding how much it would cost elsewhere would make me think about it less.

What problems is the product solving and how is that benefiting you?

I use Render for end-to-end infrastructure, making setup and deployment easy with visibility. It's seamless for environment and domain management, simpler than AWS or GCP with less need for expertise.

What do you like best about the product?

I used to like Render for its ease of use and reliability. Specifically, it was easy to set up. but turns out it is not realible

What do you dislike about the product?

Render's customer support is non-existent. My server has been crashed for 4 days on there side, and no customer support will respond to me despite reaching out 4 times. I used to like Render for its ease of use and reliability, but that's not true anymore. The initial setup was kind of easy, but their MCP was not the best or most robust.

What problems is the product solving and how is that benefiting you?

Render was supposed to provide a safe, reliable cloud environment, but it fails due to poor customer support. Initially, it was easy to set up.