Introducing Render Sandboxes: a computer for every agent.

Learn more
pricing

Render Hobby vs Pro vs Scale: Which Plan Do You Need?

TL;DR

  • Choose Hobby when you manage deployments yourself and its service and environment limits fit your application.
  • Choose Pro for shared workspace access, multi-service pull-request testing, autoscaling, or separating staging and production networks.
  • Choose Scale for centralized workspace management, company sign-in, organization audit logs, or a HIPAA-enabled workspace.
  • Hobby has no subscription fee. Compute, storage, and metered usage are billed separately on every plan.

Your first deployment is just the beginning. As your app and team grow, Render’s workspace plans support new ways to build and ship together. This guide helps you choose with confidence: you’ll learn what the subscription covers, how compute and metered usage shape your bill, and which capabilities matter for the way you work.

Render Hobby vs Pro vs Scale at a glance

Workspace subscriptions and service compute are separate

Choose the plan for the access and operational features you need. Choose resource compute for the capacity your application needs.

You choose Hobby or Pro for an individual workspace. Scale lets you bring multiple workspaces together in an organization for centralized administration. Its subscription covers the organization, while each workspace keeps its own resources and member access.

The workspace or organization subscription pays for platform features and included usage. Pro's subscription is flat, with no per-seat fees. Compute for web services, workers, databases, and preview resources is billed separately, so choose a compute plan for each resource.

Each plan includes outbound bandwidth, custom domains, and Starter-tier pipeline minutes at no extra charge. Compute, storage, and usage beyond those included amounts still add to your bill.

A custom domain is your own address, such as app.example.com, connected to a Render web service or static site instead of using its default onrender.com address.

Starter is the default build pipeline tier. Pipeline minutes measure time spent preparing deployments, such as installing dependencies, building your application, or running pre-deploy commands. They don't measure how long your deployed application runs.

With a payment method on file, extra outbound bandwidth adds to your bill, and unused bandwidth doesn't roll over. Without a payment method, exhausting the included bandwidth spins down your services for the rest of the month.

Pipeline tasks stop when included minutes run out without a payment method, or when you reach your pipeline spend limit. Existing deployments keep running. Set the limit high enough to support the builds you need, while controlling additional build charges.

Compare prices, allowances, and feature gates

All three plans include projects and environments and core deployment tools: Git-based deploys, managed TLS, a global CDN, private networking, Blueprints, and protected environments. Resource restrictions and the limits below still apply.

Included usage is counted per workspace, even inside an organization. Each workspace gets its own included amounts, so a busy workspace doesn't consume another's share. The trade-off is that unused amounts in a quiet workspace can't cover overages elsewhere. Plan details checked October 21, 2026.

Cost and included usage

Dimension
Hobby
Pro
Scale
Monthly subscription
$0 per workspace
$25 per workspace
$499 per organization
5 GB/month
25 GB/month
1,000 GB/month
2
15
25

Team and release workflow

Dimension
Hobby
Pro
Scale
Workspace members
1
Unlimited
Unlimited
Workspace services
25
Unlimited
Unlimited
Unavailable; single-service previews available
Available, resources billable
Available, resources billable
Unavailable; manual scaling available
Available
Available
Network-isolated environments
Unavailable
Available
Available

Organization and governance

Dimension
Hobby
Pro
Scale
Unavailable
Workspace-level
Workspace- and organization-level
Unavailable
Unavailable
Unlimited workspaces, no extra workspace subscription
SAML SSO and SCIM
Unavailable
Unavailable
Available
Unavailable
Unavailable
Available, BAA and additional fees required

See Render's live pricing for the complete plan comparison and current allowances.

Across all three plans, usage beyond the included amounts costs $0.15/GB for public-internet outbound bandwidth, $0.25/month for each custom domain above your workspace's included count, and $5 per 1,000 additional Starter-tier pipeline minutes.

When to choose Hobby

Choose Hobby when you manage deployments yourself and need core tools such as Git-based deploys, custom domains, and private networking. For example, a booking application with a Node.js API, background worker, and Render Postgres database can run within Hobby's service and environment limits.

Keep the workspace on Hobby, add a payment method, and choose a paid compute plan for each service or database that needs it. You pay for those resources and any metered usage, with no subscription fee.

As booking traffic grows, use CPU and memory measurements to size each resource. You can increase a service's compute capacity as your workload needs it.

A qualifying paid Render Postgres database can use high availability or read replicas on Hobby. These features depend on the database's compute requirements, with the extra datastore resources billed separately.

For production, choose paid compute for the affected services and datastores. Free web services sleep when idle, and Free Render Postgres databases expire. Changing the subscription alone doesn't remove those resource restrictions.

Check Hobby's service and environment limits against your application, then choose compute for each resource.

When to choose Pro

For a booking application, choose Pro when a teammate needs shared workspace access. That teammate can manage deployments and test changes across the API, worker, and database before a release. Full preview environments, autoscaling, or environment isolation can also justify Pro.

A migration that accidentally deletes bookings may take time to discover. Pro's longer recovery window gives paid Render Postgres databases more history to restore after this kind of data loss.

Use HTTP request logs and response-latency metrics to investigate which requests are slow or failing. Metrics streaming brings service metrics into an existing OpenTelemetry-compatible monitoring setup, helping you investigate alongside data from other systems.

The Performance pipeline runs build and pre-deploy tasks on machines with more CPU and memory than the default Starter tier. Choose it if the booking application's builds run out of memory or need more CPU. Performance pipeline minutes are billed separately.

Pro keeps more recent builds than Hobby, giving you more previous deploys to choose from when rolling back a service.

If the application needs to access a supported cloud or AI provider without storing long-lived credentials, Pro includes OpenID Connect (OIDC) for service authentication.

If you use Render Workflows for booking reminders or confirmation tasks, Pro provides higher task and compute-provisioning limits than Hobby.

Full preview environments and their resource costs

A full preview environment is a temporary test copy of the services that make up your application. For example, a pull request can create a separate web API, background worker, and Postgres database so you can test their changes together before merging.

Use a Blueprint to manage the supported resources from a YAML configuration file and enable previews. Copies update with new commits and disappear when the pull request closes or merges. Hobby's single-service previews copy an individual service instead of a coordinated set. Preview environments skip Render Workflows, so test workflow changes separately.

Preview resources use standard resource rates, with compute prorated by the second. Any bandwidth, custom domains, or pipeline usage associated with a preview follows the usual pricing. The subscription enables the feature, while each preview adds resource usage.

Previews inherit production compute plans and instance counts unless overridden, using the minimum count for autoscaled services. Set smaller preview resources when they suit your tests. Datastores and disks start without production data, so seed the data you need.

Autoscaling and network isolation requirements

On Pro and higher, autoscaling adds or removes eligible service instances between the minimum and maximum counts you set, using CPU or memory targets. It changes the number of running instances, rather than the compute plan assigned to each instance.

Manual scaling is available across workspace plans for eligible services, and each running instance adds its compute charge. Services with attached persistent disks can't run multiple instances, regardless of the workspace plan.

Ordinary private networking connects eligible services in the same workspace and region. Pro adds environment-level isolation, which blocks private traffic across a project's environment boundaries. Static sites are outside the private network, and Free web services can send private requests but can't receive them.

Choose isolation when you need to enforce a boundary between project environments, such as keeping test services from connecting to production datastores.

Pro and Scale also offer dedicated outbound IPs for external allowlists and same-region AWS private links to compatible AWS-hosted providers. These are paid add-ons, and private-link bandwidth has its own rate.

Before moving to Pro, identify the shared-access or release capability you need and include any preview resources or additional service instances in your cost estimate.

When to choose Scale

If a booking application becomes one of several products managed by separate teams, choose Scale when you need central administration across their workspaces, company sign-in through SAML SSO, automated member access through SCIM, or organization audit logs. Scale's Contributor, Viewer, and Billing roles provide more specific permissions for developers, reviewers, and billing staff.

If investigations regularly need metrics older than Pro retains, Scale's longer metrics history gives you more data to inspect.

All plans support inbound IP rules for individual Render Postgres and Render Key Value datastores. Scale extends them to web services, static sites, entire environments, and workspaces, so you can restrict public access to trusted IP ranges.

Security and compliance requirements

Customer contracts, internal access policies, and regulated data can determine which plan you need. Match the required security evidence, login controls, audit coverage, and data-handling features to the plan that provides them.

Customer security reviews

Customer security reviews often require evidence of a hosting provider's security controls. Pro provides access to the SOC 2 Type 2 report, ISO 27001 certificate, and security policy after you sign an NDA. SOC 2 evaluates security controls and their operation over time. ISO 27001 covers information security management. For example, a business customer evaluating a booking application could request these documents during procurement.

Company access and audit policies

Choose Pro when your access policy requires two-factor authentication (2FA), Google login, or both. Pro's Admin and Developer roles separate workspace administration from resource management. Scale adds Contributor, Viewer, and Billing roles when developers, reviewers, and billing staff need different permissions.

Choose Scale for SAML SSO and SCIM when your organization requires access through its identity provider. SAML centralizes sign-in, and SCIM automates adding and removing organization members. For a booking team, a company policy requiring identity-provider sign-in would point to Scale.

Use Pro's workspace audit exports to review changes within an individual workspace. Choose Scale when your audit requirements also cover organization events, such as changes to organization membership or company sign-in configuration.

HIPAA-covered workloads

Hosting a workload subject to HIPAA requires a HIPAA-enabled workspace on Scale or Enterprise. Sign a Business Associate Agreement (BAA), complete enablement, and budget the additional fees. These requirements would matter if a booking application handled protected health information for a healthcare provider subject to HIPAA. See Render's documentation for supported resources and data-handling rules.

Confirm which organization or compliance control your team requires, then compare the full Scale bill with the workspaces and resources you expect to use.

Recent changes to Hobby, Pro, and Scale

The workspace plan update expanded self-serve access to security and organization features. The main changes by plan are:

  • Hobby: The plan keeps its role for individual developers. Included bandwidth and custom-domain billing changed, so compare current usage charges when moving from a legacy plan. Collaboration and organization controls remain reasons to consider a paid plan.
  • Pro: The former Professional plan moved to a flat subscription without seat fees. Security reports and workspace audit exports became available on Pro, so Pro can handle more customer security reviews without Scale. See the plan update.
  • Scale: SAML SSO, SCIM, and advanced member roles became available without an Enterprise contract. Scale also brings multi-workspace management and HIPAA enablement into the self-serve offering. The feature changes make access and governance requirements the main upgrade considerations.

Conclusion

Choose the lowest plan that supports your collaborators, release workflow, and administrative requirements. Then budget the resources and usage separately, including temporary preview resources. For instance sizing and resource costs, use the hosting cost guide.

List the specific access, release, or governance requirement that drives your choice, and check it against current Render pricing. Revisit your plan when collaborators need access, your release process needs additional testing or scaling features, or a customer requires security controls.

Start building on Render

Frequently asked questions