Render Changelog

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.

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:

You can now change an existing service's backing Git repository or Docker image in the Render Dashboard. Previously, these changes required the Render API.

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

We've rolled out new workspace plans to make Render’s pricing more scalable for modern, fast-growing teams.

Newly created Node.js services now use Node.js 24.14.1 by default. You can always specify a different version.

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

You (and your agents) can now create new services directly from the terminal using the Render CLI's services create command:

Render's native Go environment now automatically updates to the latest stable Go 1.x version, usually within 24 hours of a new release. After an update, your service starts using the new version with its next deploy.

Render Workflows is now in public beta, with SDK support for TypeScript and Python. Define durable tasks and chain them into long-running background processes for agent logic, data pipelines, billing flows, and more.

Workspace audit logs now include the EndShellEvent event type, which indicates that a workspace member closed an active dashboard shell or SSH session to a Render service. Audit logs already included StartShellEvent, which is logged when a…

Free web services now spin down after going 15 minutes without receiving either of the following:

Newly created Python services now use Python 3.14.3 and uv version 0.10.2 by default. You can always specify a different version of both Python and uv.