Changelog

Blueprints now support projects and environments

Blueprints (Render's infrastructure-as-code model) now enable you to define projects and environments in your workspace, and to assign resources to those environments:

Defining a project with two environments using Render Blueprints

Your render.yaml file now supports two new top-level fields:

• projects: an array of project definitions, each with one or more environments and their associated resources
• ungrouped: an object for defining resources that belong to no environment

If you define a resource under one of these new fields, do not duplicate it in your file's top-level services / databases / envVarGroups fields. These fields remain supported, and resources in them keep their currently assigned environment (if any).

Learn more about Blueprint support for projects and environments in the documentation.