Render Changelog

Render now supports two additional compute plans for Key Value instances:

You can now manage your workflow services using Blueprints, Render's infrastructure-as-code model.

Services now have a new Deploys page in the Render Dashboard.

The Render CLI now automatically collects usage telemetry to help us understand common use cases and improve user experience. Telemetry is enabled by default in version 2.26.0 or later.

Render Workflows uses a new default compute plan for task runs: flex.

We're introducing new compute plans for Render services, including memory-optimized plans with higher ratios of RAM to CPU and a new 12-CPU tier for web services, private services, and background workers.

Render service builds now run on nodes with faster CPU and disk. These improvements have reduced the median build time for a Render service by 40%, with this reduction reflected across all runtimes:

Render’s managed OpenID Connect (OIDC) authentication now supports Anthropic and OpenAI in addition to AWS.

The Render MCP server now supports OAuth-based authentication for Claude Code, Codex, and Cursor:

The Render MCP server now includes a trigger_deploy tool that enables you (and your agents) to kick off a new deploy of an existing service. This can be helpful for retrying a deploy after a transient failure or forcing a clean rebuild by clearing the build cache.

Newly created services now use Bun 1.3.14 by default. You can always specify a different version.

Existing services keep their original default Bun version to prevent breaking changes.

OpenID Connect (OIDC) authentication for AWS is now generally available for Pro workspaces and higher.

Paid Render Postgres databases now support connection pooling using PgBouncer at no additional cost. Enable connection pooling if your database needs to handle more concurrent client connections than its instance type allows:

You (and your agents) can now create, update, delete, suspend, and resume Render Postgres and Key Value instances using version 2.21.0 or later of the Render CLI.

In recent weeks, we've gradually rolled out a number of optimizations for Dockerfile-based service builds on Render. These optimizations include:

Paid Render Key Value instances now support three different disk persistence modes:

Now in beta, Pro workspaces and higher can configure OpenID Connect (OIDC) to authenticate their Render services with AWS. This enables your services to securely access AWS resources at runtime using automatically rotated credentials.

In recent weeks, we've gradually rolled out a number of build optimizations for Render's Node.js native runtime, including:

You can now SSH into an ephemeral instance of your service, which Render spins up specifically for your SSH session. This enables you to inspect your service's runtime environment and execute one-off commands without affecting your production instances.

Pro workspaces and higher can now create sets of dedicated IPs to send outbound service traffic through static, reserved addresses: