Enable maintenance mode to temporarily disable incoming service traffic
You can now enable maintenance mode 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.
Learn more in the documentation.
Render accounts are now workspaces
All individual and team accounts on Render are now workspaces. This unified account model simplifies upgrading from an individual to a team. There are no changes to pricing.
Here's a summary of what's changed:
- Each individual account is now a free Hobby workspace with a single seat.
- Each team account is now a workspace with its existing plan, seats, and features.
- Hobby workspaces gain the ability to create one project with up to two environments.
- A newly created Hobby workspace can add a maximum of two total custom domains.
- This limit does not apply to individual accounts created before this date.
- The Team plan is now named Professional. Paid plans are otherwise unchanged.
- You can upgrade or downgrade your workspace's plan at any time.
For details about each workspace plan, see the pricing page.
Specify deploy behavior when modifying environment variables
When you update a service's environment variables in the Render Dashboard, you can now specify whether this triggers a new deploy.
You can select from three options:
- Save, rebuild, and deploy: Render triggers a new build for your service and deploys it with the new environment variables.
- Save and deploy: Render redeploys your service's existing build with the new environment variables.
- Save only: Render saves the new environment variables without triggering a deploy. Your service will not use the new variables until its next deploy.
Learn more about environment variables in the documentation.
Pull request previews now create GitHub deploys
As part of creating a pull request preview, Render now creates a GitHub deploy on the associated pull request. This matches the behavior for preview environments.
Click View deployment 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.
Learn more in the documentation.
Customize log streaming for individual services
Render teams with a configured log stream 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.
Additionally, all accounts can now configure whether logs from preview instances (service previews and preview environments) are included in their log stream.
Learn more in the documentation.
Create preview instances only for specific pull requests
You can now opt to create preview instances only for particular pull requests that you specify. This new manual preview mode is provided alongside the original automatic mode, where Render creates a preview for every pull request by default:
In manual mode, you trigger a preview for a pull request by including the string [render preview]
in the PR's title.
You can enable manual previews for any combination of pull request previews and preview environments. See the documentation for each:
Added restrictions and audit tracking for viewing secret values
Protected environments on Render now enforce the following additional restrictions:
- Only Admin team members can view the values of environment variables and secret files for resources in the environment.
- Only Admin team members can view connection URLs and passwords for PostgreSQL databases and Redis instances in the environment.
Additionally, Render audit logs track the viewing of these values for all of an organization's resources (not just resources in a protected environment).
Block private network traffic across environment boundaries
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 Render Dashboard:
Learn more in the documentation.
Virginia region (US East) now generally available
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 Dashboard:
Render supports deploying services to the following regions:
- Oregon, USA
- Ohio, USA
- Virginia, USA
- Frankfurt, Germany
- Singapore
Added dark display theme to the Render Dashboard
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 Theme section: