We're posting an off-schedule Changelog update to share that Render has achieved a significant milestone. Read on to learn more!

This week, we announced that Render raised a $50 million Series B led by Bessemer Venture Partners. This new round of funding empowers us to continue to build toward our vision of making cloud infrastructure management a thing of the past and ushering in a new era of developer productivity.


As reported by <a href="https://www.businessinsider.com/render-pitch-deck-cloud-infrastructure-salesforce-heroku-2023-6">Insider</a> and <a href="https://techcrunch.com/2023/06/20/render-bessemer-ventures-startup-cloud/">TechCrunch</a> today, Render has reached a significant milestone in our journey to build the modern cloud  — we've raised a **$50M Series B** led by <a href="https://www.bvp.com/news/render-ushers-in-a-modern-age-of-application-development-in-the-cloud">Bessemer Venture Partners</a>, with enthusiastic participation from existing investors Addition, General Catalyst, and the South Park Commons Fund.

![Render raises $50 Million in new funding to build the new cloud](https://cdn.sanity.io/images/hvk0tap5/production/f5007dbb9a922be16920e4f0456dbee9308e6e8c-1877x1061.png?w=900)

We've grown quite a bit since launching at TechCrunch Disrupt in 2019. Websites and workloads running on Render now serve over **1 billion visits** every month. Well **over half a million developers** and teams are on the platform; they range from promising early-stage startups like <a href="https://socket.dev/">Socket</a> to venture-backed unicorns like <a href="https://watershed.com/">Watershed</a>.

<figure class="blockquote">
  <blockquote>
    <p>Building on Render has been a superpower for Watershed. It lets us focus on what matters most — delighting our customers, rather than managing our infrastructure. Our engineers can ship features to customers in hours or days instead of weeks or months. Every startup should start on Render.</p>
      <footer>
        – Avi Itskovich, Co-founder at Watershed
      </footer>
  </blockquote>
</figure>

It isn't just new startups; every day, businesses migrate entire application stacks on AWS, Heroku, and other platforms to Render because **they don't want to think about cloud infrastructure anymore**.

And yet, our work remains far from done. Render offers the promise of a powerful, flexible, and intuitive cloud experience for software developers and teams of all skill levels and sizes. Fulfilling this promise means expanding platform functionality rapidly, which is exactly how we'll use the new investment. We're growing the team — see open roles at [render.com/careers](/careers#open-roles).

Over the coming months, we will continue to launch products to help you **ship faster, troubleshoot better, and run more kinds of cloud workloads**, so you can continue to focus on your products and leave even more of your infrastructure needs to us. We're incredibly excited about the next phase, and hope you are, too.


Render's $50 Million Series B

Projects are now available for all developers on the Team, Organization, and Enterprise plans. You can use projects to organize your app’s services, making managing and collaborating with your team easier.

We’re thrilled to share that projects are now generally available. [Projects](https://docs.render.com/projects) make it easier for you and your team to collaborate on apps. Organize all of the services associated with an app in a project and further group services by environment — staging, production, etc. — to make building with your team easier and more streamlined.


Render began with a simple question — how do we make it easier for developers to run code in the cloud? Every day, developers toil with overly complicated cloud configurations that are hard to maintain. As developers, you know you have less time to think about what you’re building if you also need to handle the intimidating complexity of public cloud offerings. Teams are increasingly aware of the cost of managing infrastructure and are choosing Render instead.

While it was easy to set up an app with one or two services, like a database and a server, teams shared that they needed help managing apps on Render with many services. Our overview page featured a long list of services associated with a team or account. We didn’t have a way for teams to express how their services were related or organize them by environment.

Today, Render is announcing our first launch to improve the development team experience — projects. Projects have two essential functions.

First, developers can now group services related to an app together. Say you’ve built an app for recruiting on Render. You can now organize your servers, Redis job queue, database, cron jobs, and other services you’ve configured to support your app together in a project.

![Render Dashboard's homepage, now organized into projects](https://cdn.sanity.io/images/hvk0tap5/production/e8764bc73b280baa36e6af2857e214cdbd6c123a-2558x1062.png?w=900)

Second, projects help developers organize their services into environments. As teams grow on Render, we see them start to create development and staging deployments. Previously, naming was the only way to distinguish between a development or staging service. Developers appended “-staging” or “-stg” to the end of a service’s name. Now, projects have a built-in affordance to group services by environment, making it easier for teams to ensure that they deploy to the right services when testing changes.

![Project overview page, including its Production and Staging environments](https://cdn.sanity.io/images/hvk0tap5/production/73c4b2b46f5243953cbf0af69bb6ce25d125c6d1-2668x1744.png?w=900)

Projects represent a paradigm shift in how apps are developed, tested, and deployed on Render. Allowing developers to group services unlocks new possibilities for how teams build their apps throughout the development lifecycle. We will continue to release new capabilities for projects over the next year, and we can’t wait to share what we have in store.

Projects are now available for all developers on the Team plan or higher. We’re building Render so that teams like yours can collaborate better, so reach out to let us know how we can improve projects.

Projects

Updates to our build retention policy for Instant Rollbacks

Starting on July 5, 2023, we will retain builds only for the most recent deploys of Render services. Based on historical data, this change will not affect most users. The number of builds retained will vary based on plan.

Find more detail under Instant Rollbacks on our 

Build & Deploy

Data Stores

Collaboration

Convenience

Uptime & Monitoring

Networking

Security

Compliance

Support

For hobbyists, students, and indie hackers.

Hobby

For small teams and early-stage startups.

Professional

For larger teams with complex needs.

Organization

For ultimate power and customization.

Enterprise

Cancel deploys, Errors for failed on-off jobs, and more

We've also shipped a ton of small wins over the last week.

 You asked, and we listened. If a deploy was triggered by accident or isn't going as anticipated, click the new Cancel button, and your service will remain as-is

 Now, if a one-off job fails, we publish a meaningful error that should help make debugging easier

 If you need to request Render's SOC 2 report or learn more about our security and compliance posture, all of this is now available self-serve in our 

 explaining how host and port configurations work. We also updated the 

That's it for this week! As always, please let us know how we can improve Render for you. Thank you for choosing Render!

All Render services now use OpenSSH version 9.9 to manage SSH connections. Services previously used version 8.9.

If you initiate SSH connections from your service,

 this upgrade includes one change that might affect those connections. From the 

 are now first-match-wins to match other directives. Previously if an environment variable was multiply specified the last set value would have been used."

 directive in your service's SSH configuration, make sure you don't set the same environment variable multiple times to avoid unexpected behavior.

Learn more about using SSH on Render in the 

OpenSSH updated to version 9.9

 provides command-line support for common platform actions, including:

Triggering service deploys, restarts, and one-off jobs

The CLI supports interactive menu-based navigation, along with a non-interactive mode for use in scripts and CI/CD. 

The Render CLI is now available in public beta

 now provide AI-powered chat trained on our documentation content. Click 

Use the chat to receive fast, focused answers to your questions about the platform, along with links to relevant articles:

AI chat now available in the Render documentation

In-place PostgreSQL upgrades are now generally available for all Render workspaces. This feature upgrades your database to the most recent major PostgreSQL version supported by Render (currently 16).

Upgrading your database requires downtime.

Open the upgrade page for your database in the 

In-place PostgreSQL upgrades now generally available

Render has moved PostgreSQL version 12 to legacy support ahead of its 

Starting today, you cannot create new managed PostgreSQL 12 databases in your workspace unless you already have one.

We strongly recommend upgrading any PostgreSQL 12 databases to an actively supported version to continue receiving important security updates. Render supports 

PostgreSQL 12 moved to legacy support

Newly created Node.js services now use Node.js 22.10.0 by default. You can always 

 Node.js services keep their original default version to prevent breaking changes.

Default Node.js version updated to 22.10.0

Newly created Python services now use Python 3.11.10 by default. You can always 

 Python services keep their original default version to prevent breaking changes.

Default Python version updated to 3.11.10

Render now provides early access support for upgrading your PostgreSQL database's major version in-place. This upgrades your database to the most recent PostgreSQL version supported by Render (currently 16).

Then open the upgrade page for your database by clicking the version number on its 

In-place PostgreSQL upgrades now available in early access

 are now available for all workspaces. These plans enable you to set your database's storage separately from its RAM and CPU.

Starting today, every new database created on Render has a flexible plan. If you have a database on a 

Flexible PostgreSQL plans now available for all workspaces

 for any paid web service in the Render Dashboard:

While in maintenance mode, a web service is not reachable from the public internet (but it remains up and running).

Enable maintenance mode to prevent incoming client requests while rolling out major changes to your infrastructure.

Enable maintenance mode to temporarily disable incoming service traffic

All individual and team accounts on Render are now 

. This unified account model simplifies upgrading from an individual to a team. There are no changes to 

Each team account is now a workspace with its existing plan, seats, and features.

 workspaces gain the ability to create one 

 workspace can add a maximum of two total custom domains.

This limit does not apply to individual accounts created before this date.

You can upgrade or downgrade your workspace's plan at any time.

For details about each workspace plan, see the 

Render accounts are now workspaces

When you update a service's environment variables in the 

, you can now specify whether this triggers a new deploy.

Render triggers a new build for your service and deploys it with the new environment variables.

 build with the new environment variables.

Render saves the new environment variables 

 triggering a deploy. Your service will not use the new variables until its next deploy.

Learn more about environment variables in the 

Specify deploy behavior when modifying environment variables

As part of creating a pull request preview, Render now creates a GitHub deploy on the associated pull request. This matches the behavior for 

 to open the preview instance in your browser.

Before this change, Render instead added a comment with preview details to your pull request. Render continues to use comments for GitLab and Bitbucket repositories.

Pull request previews now create GitHub deploys

 can now override their default log stream settings for individual services:

All teams can disable log streaming for an individual service.

Teams with an Organization plan or higher can stream an individual service's logs to a non-default destination.

 accounts can now configure whether logs from preview instances (service previews and preview environments) are included in their log stream.

Customize log streaming for individual services

You can now opt to create preview instances only for particular pull requests that you specify. This new 

 preview mode is provided alongside the original 

 mode, where Render creates a preview for 

In manual mode, you trigger a preview for a pull request by including the string 

You can enable manual previews for any combination of pull request previews and preview environments. See the documentation for each:

Create preview instances only for specific pull requests

 on Render now enforce the following additional restrictions:

 team members can view the values of environment variables and secret files for resources in the environment.

 team members can view connection URLs and passwords for PostgreSQL databases and Redis instances in the environment.

 of an organization's resources (not just resources in a protected environment).

Added restrictions and audit tracking for viewing secret values

Teams on Render can now configure a project environment to block all private network traffic from entering or leaving that environment. This helps prevent your staging services from inadvertently accessing a production resource (or vice versa).

Toggle this setting from an environment's Settings page in the 

Block private network traffic across environment boundaries

Render's Virginia (US East) region has graduated from early access to general availability.

Select a service's region as part of the creation flow in the 

Render supports deploying services to the following regions:

Virginia region (US East) now generally available

The Render Dashboard now provides a dark display theme:

Additionally, you can toggle a high contrast mode to more prominently highlight certain interactive elements.

Quickly set your theme from the account menu in the top-right corner of the dashboard:

To also toggle high contrast, open your account settings and scroll down to the 

Added dark display theme to the Render Dashboard

 has added over 50 new endpoints to support much more extensive integration with the Render platform.

Endpoints are now available for the following resources that were previously unsupported by the API:

Datastores (PostgreSQL, Redis, and persistent disks)

New endpoints are also available for certain resources that are already supported by the API, such as redirect/rewrite rules for static sites.

With these additions, the API supports almost all functionality available in the Render Dashboard. There are no breaking changes to existing API endpoints.

The OpenAPI spec for the Render API is available in JSON format at 

. You can use this spec to create your own custom clients and other tooling.

API endpoints for datastores, logs, environments, Blueprints, and more

 now emit service logs. As with logs for other service types, Redis logs are available in the 

Redis instances now emit service logs

Newly created Node.js services now use Node.js 20.15.1 by default. You can always 

Default Node.js version updated to 20.15.1

Teams with an Organization or Enterprise plan can now export audit logs of material events that occurred in the account over a given time frame. This includes events related to:

Team admins can export audit log data in the 

For a list of all audit log event types, see the 

Note the following about data availability:

 Organization and Enterprise accounts, audit log data is available starting from 

 Organization or Enterprise account, audit log data is available starting from the date of account creation.

 an account to Organization or Enterprise, audit log data is available starting from the date of the upgrade.

Audit logs for Organization and Enterprise plans

You can now pull and deploy your private Docker images from Google Artifact Registry. Add your credentials in the Render Dashboard during service creation:

With this addition, Render now supports pulling private images from the following registries:

Pull and deploy private images from Google Artifact Registry

Render now provides simplified deployment for popular PostgreSQL admin apps in the 

With a few clicks, you can deploy each app as a standalone web service that's automatically configured to connect to your database.

The following apps are currently supported:

Quickly deploy PostgreSQL admin apps from the Render Dashboard

 is now available in early access. You can use this provider to manage your Render services alongside other systems in your organization's infrastructure.

The provider and its documentation are available in the 

Note that breaking changes might be introduced during the early access period.

 Any such changes will be noted in accompanying release notes.

Official Render Terraform provider now available in early access

You can now change the native runtime for an existing service in any of the following ways:

Changing a service's runtime in the Render Dashboard is not currently supported.

Change an existing service's runtime via API or Blueprint

, newly created Free Render PostgreSQL databases expire after 30 days (previously 90 days). Free databases created prior to this date retain their original expiration date.

The following Free database policies remain unchanged:

Each individual and team account is limited to one Free database at a time.

After your Free database expires, you have an additional 14 days to upgrade it to a paid instance type before your data is deleted.

After your Free database expires, you can create a new Free database.

Learn more about Free PostgreSQL limitations in the 

Free PostgreSQL instances now expire after 30 days (previously 90)

Teams can now require all members to log in to Render via their Google account (instead of using another supported login method, such as username and password).

Admins can enable this feature from their Team Settings page in the 

If a team member does log in to Render using a different method, they cannot access the team's resources or settings.

Teams can now require login via Google account

You can now deploy Render services to the Virginia region (US East).

Note that this region is currently in early access. 

It's available to all users, and it's feature-complete with our other regions. Early access provides us an opportunity to address any one-off issues that might arise with spinning up a new region. We'll announce when this early access period completes.

Added Virginia region (US East) in early access

Powerful new application metrics are available for paid instances in the 

CPU and memory usage over time, segmented by instance for scaled services

HTTP request volume and response latency, segmented by status code, path, and more

Response latency metrics require a team account.

Metrics from the past 7 days are available for individual accounts. Teams can view metrics from the past 14 or 30 days, depending on their plan.

Enhanced service metrics in the Render Dashboard and API

 file from your existing services in the 

Use this file to create a Render Blueprint that manages those existing services, or to replicate your architecture with a completely new set of services.

Create a Blueprint from existing services

Many popular IDEs now provide schema-backed validation and autocompletion for the 

IDE validation for render.yaml files

You can now connect your Bitbucket account to Render and deploy from any Bitbucket repo you have access to.

. After you authorize Render, your Bitbucket repos appear in the selection list:

You can also now sign in to Render using your Bitbucket identity.

Added support for Bitbucket

Teams on Render can now designate individual project environments as 

. Doing so prevents non-Admin team members from performing potentially destructive actions on that environment or its resources, including:

Deleting any of the environment's resources (services, environment groups, etc.), or deleting the environment itself

Modifying environment variables or secret files for any service or environment group that belongs to the environment

Moving resources into or out of the environment

Modifying access control IPs for any PostgreSQL database or Redis instance that belongs to the environment

Accessing the shell for a service that belongs to the environment

Designate environments as protected to prevent destructive actions

 and persists their assets in the same region where you deployed your 

 non-static Render service. Previously, all static site assets were stored in the Oregon region.

Static sites are still cached and served to users by a global CDN, regardless of their region.

 This change primarily improves latency for any 

 that point to a Render web service in the same region.

Static site assets now built and persisted in the same region as other services

You can update your service's build and start commands to use Bun:

Changelog

June 21, 2023 - Changelog

Render's $50 million Series B

Projects are now available for all teams

Updates to our build retention policy for Instant Rollbacks

Cancel deploys, Errors for failed on-off jobs, and more