Render review

Render is a cloud platform for deploying and running apps, APIs, databases, and other workloads. The pricing page describes a range of service types: web services, static sites, databases, cron jobs, workflows, and background jobs. You connect a code repository to deploy, then use platform features such as networking, monitoring, and pull request previews.

Previews can create temporary versions of an application’s architecture for each change. Render also lists load-based autoscaling, log streaming and metrics, durable workflows for stateful or asynchronous logic, and isolated sandboxes for agents to run code and work with files.

The key buying distinction is between the workspace plan and the infrastructure running your services. Workspace plans cover items such as seats, bandwidth allowances, and environments; compute is billed separately. So the advertised $25 Pro plan is not a flat price for a production app.

Render’s appeal is that a team can deploy several kinds of services on one platform, rather than treating app hosting, databases, scheduled work, and background jobs as separate products. The pricing page lists full-stack previews on Pro, and the product supports internal networking, logs, metrics, autoscaling, and durable workflows. Those features may reduce the amount of infrastructure a team has to assemble and manage itself.

User reports also point to a straightforward deployment experience, though they are anecdotes, not a guarantee. In one Reddit thread, a commenter said setting up a Next app, Express API, Postgres database, Redis cache, and cron job was easy. Another described deploying Rails apps as simple, while a separate thread includes a developer who preferred Render after trying several alternatives.

The paid workspace plans add room for teams: Pro lists unlimited seats and services, 15 custom domains, and a 7-day PITR window for $25 per month. Scale adds 1 TB of monthly bandwidth, 5,000 build minutes, 30-day log retention, SAML SSO, and SCIM for $499 per month, according to the pricing page.

The workspace price is only part of the bill. Render lists services from $7 per month, Postgres from $6, and Key Value from $10; compute is charged separately from workspace plans. Workflows start at $0.20 per active CPU hour plus $0.05 per active GB hour, while agent sandboxes cost $0.12 per active CPU hour plus memory charges from $0.038 per hour. Add storage, bandwidth, or build overages and costs can rise further.

The free Hobby plan is limited to 25 services, 5 GB of monthly bandwidth, one team seat, two environments per project, and a 3-day PITR window. Pro’s $25 monthly workspace plan includes 25 GB of bandwidth, not unlimited traffic; excess bandwidth is listed at $0.15 per GB. The pricing page does not show annual billing, and Enterprise pricing is custom.

That makes Render less predictable for teams whose usage is hard to forecast. A commenter on r/webdev said lower tiers were less generous than some alternatives. The platform may simplify deployment, but check expected compute and bandwidth costs before comparing workspace prices.

Render’s workspace plans run from free to $499 per month, but the plan price is not the full bill: compute is charged separately, according to the pricing details checked on November 6, 2026. Hobby is $0 and includes up to 25 services, 5 GB of monthly bandwidth, one team seat and two environments per project. Pro costs $25 per month, with unlimited seats and services, 25 GB of bandwidth and full-stack previews. Scale jumps to $499 per month and adds 1 TB of bandwidth, 5,000 build minutes and 30-day log retention. Enterprise pricing is custom.

Budget for metered services too: web services start at $7 per month, Postgres at $6 and Key Value at $10. Bandwidth above plan costs $0.15 per GB; standard build overage is $5 per 1,000 minutes. Workflows and sandboxes have usage-based charges, and persistent disks cost $0.25 per GB monthly. Annual pricing is not shown. If you need predictable all-in costs, estimate compute, storage and overages before comparing Render’s workspace fee with another provider.

Treat a move to Render as a component-by-component migration, not a single hosting change. Inventory your apps, databases, background jobs, cron jobs, workflows, domains, storage and external integrations, then map each to a Render service or an alternative. The published material describes managed databases, workflows, previews and other platform services, but does not specify migration tooling, database export steps, portability guarantees or a typical migration timeline. Confirm those details for your exact stack before scheduling a cutover.

The available published material includes no Reddit reports, so we can’t responsibly say what users there cite as reasons for leaving. Render’s listed add-ons and usage charges do make cost modeling worth doing before a move: compare expected compute, bandwidth, storage and build usage, not just the workspace plan. Before moving away, check how to export each database and retrieve files, logs and configuration; those procedures are not published on the vendor's site. Keep the old environment available until you have verified the replacement and a rollback plan.