Render Compute Costs, Discounts & Real Spend: 2026 Guide

The flat plan fee is only part of it. Hobby is free, Pro is $25 a month, and Scale is $499, with Enterprise quoted separately. On top of that fee, compute bills per service: a Standard web service is about $9.70 a month always-on, a Pro instance around $33. Managed Postgres runs $7 to $135 by tier, and bandwidth past the plan allowance bills per GB. So a real app on Pro is the $25 fee plus its compute plus any databases, which usually lands well above the sticker. Budget from your own services, not the plan price.

For static sites and prototypes, yes; for production, no. Hobby is generous, with 25 services and 5 GB of bandwidth at no cost, but two limits make it unsuitable for real users. Free web services spin down after about fifteen minutes idle, so the next request is slow, and the free Postgres database is wiped after 90 days. That is fine for a demo and dangerous for anything with data you need to keep. Use Hobby to build and evaluate, then move web services and databases to paid tiers before you put real traffic on them.

Three main ones. Compute is billed per service by instance size and active minute, separate from the plan fee, so a Standard service is about $9.70 a month always-on. Managed databases are their own line, with Postgres from $7 to $135 and Redis extra. Bandwidth past the plan's included egress bills per GB. On the free tier, the 90-day database wipe is an implicit cost too, since keeping data forces a paid tier. None of these sit next to the plan price, so the real bill is the fee plus compute plus databases plus overage.

Because the free Postgres database on the Hobby tier is deleted after 90 days by design. Render offers it for prototyping, not permanent storage, so it expires on a clock whether or not you are using it. Anything you need to keep must move to a paid database tier before the deadline, starting at $7 a month for Starter. If a project has grown past the prototype stage, migrating the data to a paid tier early is the safe move. Losing a free database to the 90-day wipe is one of the most common and avoidable Render surprises.

Managed Postgres is priced by tier, separate from your plan. Starter at 256 MB is $7 a month, Standard at 1 GB is $32, and Pro at 5 GB is $135, with larger tiers above that. Redis and other stores carry their own charges. Each database is an independent line, so an app with a primary database and a cache is paying for both alongside its compute. The free Hobby Postgres exists but expires at 90 days, so any production database is a paid tier. Pick the smallest that fits, since databases are often the second-largest line after compute.

Yes. Each plan includes some outbound bandwidth, 5 GB on Hobby, 25 GB on Pro, and 1 TB on Scale, and traffic beyond that allowance is billed per GB. For a low-traffic app the included amount is plenty, but a popular service can push past it and add a transfer line the flat plan fee never showed. The fix is the usual one: cache aggressively and offload static assets so egress stays inside the allowance. Check the bandwidth figure against the plan you are on before assuming transfer is free, especially as traffic grows.

At Enterprise, yes; on Pro and the per-service rates, no. Enterprise is quote-based, which puts rate, support terms and committed usage on the table for a large account. A competitor figure from Railway or DigitalOcean and an annual commitment anchor the ask, and quarter-end timing helps. Scale at $499 has some room on a big account too, mainly around committed usage. Below that, the plan fee and unit rates are fixed, so the saving on Pro is architectural: right-size instances, sleep idle services, and run only the databases you need.

Right-size every instance so compute matches the load, and let services that idle scale to zero rather than billing around the clock. Run only the managed databases you truly need, and pick the smallest tier that fits, since databases are a major line. Keep bandwidth inside the plan allowance by caching and offloading static assets. Move anything real off the free tier before the 90-day database wipe. For heavy, steady workloads, compare a fixed-price rival or negotiate at Enterprise. Together, those habits keep a Render bill near the work actually done.