Render

render.com · United States

Render brings website deployment, application hosting and managed databases into one platform. Static sites build automatically from Git and run behind a global CDN; paid web services can also cache static assets at the edge. It suits frontend projects, documentation sites and small teams managing a full application, with workspace plans and resource usage billed separately.

Static site hostingGlobal CDNGit deploymentEdge cachingApplication platform
Service marketsMultiple regions
BillingFree / Monthly / Usage
Free trialSupported
Payments
银行卡 / Bank cardACH
Overall rating
★★★★★★★★★★3.5

On-site interest
3,800index
01

Company introduction

About Render
Founded
2018 (incorporation); public launch in April 2019
Co-founders
Anurag Goel
Headquarters
San Francisco, California, United States
Listing
Venture-backed company

An application platform with integrated delivery

Render is a cloud application platform founded by Anurag Goel and operated by Render Services, Inc. The company is headquartered in San Francisco, California, with a distributed team. It brings application deployment, managed data services and static website delivery into one platform; CDN delivery for static content forms part of its hosting service.

The corporate and product timelines differ. Render Services, Inc. was incorporated in Delaware in 2018 and was previously named Cove Studios, Inc. Goel began developing the prototype in 2017, followed by an invitation-only beta in 2018 and public signups at the end of April 2019.

Render announced an $80 million Series C led by Georgian in January 2025. A further $100 million extension of that round followed in February 2026, bringing total funding to $258 million. The extension supports development of the cloud platform and infrastructure for AI applications.

Choose delivery around the way your site runs

Static Sites hosts frontend builds, blogs and documentation. Connect a Git repository and set the build command to deploy on pushes. Each site receives an onrender.com address and supports custom domains. The global CDN includes HTTPS, Brotli compression, redirects, rewrites and custom response headers. Successful deployments invalidate the CDN cache, while pull request previews let a team check changes before merging.

Use Web Services for server rendering, APIs or persistent application processes, deployed from Git or a Docker image. Paid web services can enable the same global edge cache used by static sites to offload eligible assets. Free web services do not include edge caching.

Web service edge caching is off by default. You can cache common static files or all eligible responses, subject to request methods, Cache-Control and Set-Cookie handling. When caching all files, explicitly protect signed-in pages, personal data and other dynamic content with appropriate response headers. Successful deployments and manual purges clear the service’s edge cache.

Global delivery and regional application hosting

Static sites use the global CDN without a region selection. Applications and databases can run in Oregon, Ohio or Virginia in the United States, Frankfurt in Germany, or Singapore. These are application regions rather than a list of CDN locations. Projects targeting mainland China or requiring particular regional latency should validate their own access paths, domains and business requirements.

Application services and databases in the same workspace and region can communicate over a private network; static sites are excluded. Cross-region communication requires secured public-network connections. An existing service cannot simply switch regions: create resources in the destination and migrate the application and data. Place applications and databases in the same region where appropriate and check private-network connectivity, while budgeting any external-service transfer charges.

Render provides DDoS protection for hosted websites and applications using Cloudflare infrastructure, alongside automatically managed TLS certificates. Teams purchasing advanced traffic policies, specified locations or a separate CDN contract should confirm that the platform meets those requirements.

Workspace plans, free allowances and buying terms

Render separates the workspace subscription from service compute. Hobby has no workspace fee, Pro costs USD25/month and Scale costs USD499/month; Pro and Scale have no seat charges. Static sites have no server compute fee, but consume workspace bandwidth and build allowances. Web services, private services, workers, datastores and other paid instances are charged by their own configurations, including applicable replicas and preview environments.

Free instances let you try the platform. Free web services sleep after 15 idle minutes and share 750 hours per workspace each month. Free Postgres has 1GB of storage and expires after 30 days; upgrade within the following 14-day grace period or the database and its data are deleted. A paid workspace subscription does not remove Free instance limits.

Self-service billing uses payment cards. Adding a card can trigger a temporary USD1 authorization rather than a service charge; the billing address is used to calculate applicable sales tax. Accounts in India may need to pay invoices manually under local rules. Card networks, issuing countries and cross-border acceptance depend on the account payment page and issuer approval.

ACH is limited to billing accounts with that method enabled. Confirm eligibility, supported regions and payment deadlines with Render. Any separately agreed enterprise payment terms should be included in the contract.

Before leaving, review both the workspace subscription and each service, export data you need and delete paid resources you no longer require. Downgrading Scale requires removing secondary workspaces and resolving organization settings. Confirm refund eligibility, cancellation timing and enterprise settlement terms before purchasing.

02

Who is this provider for?

Frontend, documentation and publishing projects

Developers building static pages with tools such as React, Vue or Hugo who want Git deployment, HTTPS, domains and CDN delivery in one place.

Static sites have no separate compute-instance charge, but builds, outbound traffic and domains still draw on workspace allowances.

Product teams running a frontend and API

Teams that want to deploy websites, web services, background tasks and databases together with less infrastructure configuration.

Budget for the workspace plan, each service’s compute and database resources. Web service edge caching requires paid compute.

Businesses needing team controls or a contract

Organizations seeking broader permissions, organization management, support or contractual arrangements within a managed application platform.

Compare Pro, Scale and Enterprise against workspace count, resource needs and support requirements. Plan regional delivery and migrations in advance.

Consider Render when deployment, application hosting and content delivery belong in one workflow. Separate static sites from dynamic web services, then estimate workspace count, compute, builds and outbound traffic. Validate regional delivery with representative pages and the networks your users rely on.

03

Services and products

Core products from official sources

Explore products by use case: what they do, how to use them and whether they are billed separately.

Static Sites

Static hosting and global CDN

Builds frontends, blogs and documentation from Git, with previews, domains, automatic TLS, redirects and response headers. Successful deployments update the site and invalidate its CDN cache.

No separate static-site compute charge. Outbound traffic, builds and custom domains use the applicable workspace allowances.Official product information

Web Services + Edge Caching

Dynamic apps and static asset caching

Runs public HTTP applications, APIs and Docker images. Paid instances can enable edge caching with response-header controls; free instances cannot use the edge cache.

Compute is billed by the selected instance resources and running usage, alongside workspace and additional usage charges.Official product information

Private services and background tasks

Backend processes and job execution

Private Services provide internal service addresses, Background Workers run continuous jobs, and Cron Jobs execute scheduled work. Render Workflows supports composable, long-running tasks and data processing.

Persistent services, scheduled jobs and Workflows each follow their own compute and execution billing rules.Official product information

Render Postgres / Key Value

Managed databases and shared caching

Postgres provides relational storage, with continuous backups and point-in-time recovery on paid instances. Redis-client-compatible Key Value supports queues and shared caches, with persistence on paid instances.

Databases, storage and applicable network usage are billed separately. Free instances have capacity, persistence or expiry limits.Official product information

Blueprints

Infrastructure configuration

Describes services, databases and environment configuration in a repository’s render.yaml file, bringing related resources into version control with CLI and API validation.

Underlying services and databases remain subject to resource charges and the workspace plan.Official product information
Sources: Render official product pages and developer documentationVerified: 2026-11-16
04

Plans and pricing

Official public pricing
Website delivery and security plans · monthly and annual billing shown separatelyUSD

Hobby

Personal projects and trying the platform

USD0/month

No workspace subscription fee; paid compute, storage and excess usage are charged separately.

  • 1 member and up to 25 services
  • 5GB of outbound bandwidth per workspace each month
  • 500 monthly Starter pipeline minutes
  • 2 custom domains included
  • Free instances have separate sleep, retention and usage limits

Pro

Production applications with team collaboration

USD25/month

A flat monthly workspace fee with no seat charges; service compute and storage cost extra.

  • Unlimited workspace members
  • 25GB of outbound bandwidth per workspace each month
  • 1,000 monthly Starter pipeline minutes
  • 15 custom domains included
  • Autoscaling and the Performance pipeline are available, with applicable usage charges

Scale

Teams needing multiple workspaces and enterprise controls

USD499/month

A flat monthly fee with no seat charges. An organization can contain multiple workspaces at no additional workspace fee; service resources cost extra.

  • Unlimited members and a multi-workspace organization
  • 1TB of outbound bandwidth per workspace each month
  • 5,000 Starter pipeline minutes per workspace each month
  • 25 custom domains included
  • SAML SSO, SCIM and advanced roles; HIPAA adds 20% of compute charges with no minimum surcharge

Enterprise

Organizations needing custom allowances and contractual commitments

Custom quote

Platform terms, resource allowances, support and service commitments are agreed by contract.

  • Configure the organization and purchase with Render sales
  • Custom bandwidth, resources and governance requirements
  • Confirm payment terms and service commitments in the order or contract
  • Existing Enterprise contracts can have separate seat and billing terms

How are separate products billed?

ProductAllowance / base feeUsage prices
Public outbound bandwidthAdditional GB after the workspace allowance;static sites, web services and other public outbound traffic share the allowance.USD0.15/GB
Private Link outbound bandwidthAdditional outbound traffic sent through Private Link, separately priced from public traffic.USD0.03/GB
Excess Starter pipeline minutesHobby, Pro and Scale include 500, 1,000 and 5,000 minutes per workspace each month.Extra Starter minutes are priced per 1,000 minutes.USD5/1,000 minutes
Additional custom domainsDomains above the plan allowance: 2 on Hobby, 15 on Pro and 25 on Scale.USD0.25/domain-month
Web service compute exampleA paid 0.5c-512mb instance with 0.5 CPU and 512MB RAM.Workspace fees and other resources cost extra;compute is prorated by the second.USD7/instance-month
Postgres compute exampleA paid instance with 0.1 CPU and 256MB RAM.Database storage, outbound traffic and replicas cost extra;compute is prorated by the second.USD6/instance-month
Key Value compute exampleA paid 256MB instance with a 250-connection limit.Other instance sizes are priced separately.USD10/instance-month
Workflows Flex CPUActual CPU time consumed by a task run.Memory, state storage and outbound traffic are additional.USD0.20/CPU-hour
Workflows Flex memoryActual RAM usage over the task run, added to CPU charges.USD0.05/GB-hour
Workflows state storageRun and step state is retained for 30 days.Each state is charged once by size, without a second charge when retention crosses a billing month.USD0.25/GB
Cron Job minimumRuntime is billed by the second, with a monthly minimum for each Cron Job service.USD1/service-month minimum

Prices are in USD. Budget for the workspace fee, instance compute, storage, builds, extra domains and outbound traffic together. Compute and storage are prorated by the second; applicable taxes depend on billing details. Bandwidth is shared per workspace and does not roll over. Inbound traffic and same-region private networking are free. A monthly pipeline spending limit can pause new builds while deployed services continue running on their existing build artifacts. Without a payment method, exceeding bandwidth suspends services until the next month. Web service edge caching requires paid compute and is unavailable on Free instances.

05

CdnChart Selection Guide

GoodSelection verdict

A useful option for teams deploying frontends, APIs and databases together

Static sites integrate a global CDN, and paid web services offer edge caching, reducing the work of configuring a separate delivery path. Compare workspace subscriptions with the full resource bill, and plan production use around application regions and free-service limits.

Use casesProductsPricing and termsDocumentationSupport resources

Why we recommend it

  • Git deployment, previews, HTTPS and static delivery form a coherent website publishing workflow.
  • Dynamic services, background tasks and managed databases share one platform, with private networking within each region.
  • Workspace management and compute resources can be selected separately to match individual projects or team requirements.

Considerations

Plan around free web service sleep behavior, build limits and traffic allowances. Enable paid-service edge caching deliberately and protect dynamic responses. Persistent instances, databases, multiple workspaces and external data access can all increase costs. Validate suitability where mainland China delivery, specified edge locations or migration flexibility is essential.

Related articles

Explore Render products, use cases and buying advice

No articles about Render yet.