---
name: Render Changelog
slug: render-changelog
type: feed
source_url: https://render.com/changelog
organization: Render
organization_slug: render
total_releases: 39
latest_date: 2026-11-04
last_updated: 2026-11-10
tracking_since: 2025-12-17
canonical: https://releases.sh/render/render-changelog
organization_url: https://releases.sh/render
---

<Summary type="rolling" window-days="90" release-count="9">
Render shipped Workflows, a durable task orchestration system now in public beta with TypeScript and Python SDKs for building long-running background processes—handling queuing, retries, state management, and parallel execution on Render's private network. Beyond that, the platform expanded Blueprint flexibility by supporting custom file paths and added validation via CLI and API, while the CLI itself gained workspace listing and non-interactive database querying. Audit logs now capture session closures and connection metadata (source IP, user agent), and free web services extended their spindown logic to respect active WebSocket traffic alongside HTTP requests.
</Summary>

<Summary type="monthly" period="March 2026" release-count="1">
Audit logs gained visibility into shell session lifecycles and client context. The `EndShellEvent` type now complements existing `StartShellEvent` tracking, while new `source_ip` and `user_agent` metadata fields let you see where shell access originated.
</Summary>

<Release date="November 4, 2026" published="2026-11-04T00:00:00.000Z" url="https://render.com/changelog/upcoming-service-preview-and-preview-environment-support-for-github-stacked-prs">
## Upcoming service preview and preview environment support for GitHub stacked PRs

On **November 18, 2026**, Render will begin supporting separate [service previews](https://render.com/docs/service-previews) and [preview environments](https://render.com/docs/preview-environments) for each pull request in a GitHub PR stack:

Currently, Render creates previews only for PRs that *directly* target your service's linked branch. This means that only the bottom PR in a stack can generate previews.

Beginning November 18, Render will apply your existing preview mode to all PRs in a stack:

- **Automatic**: Render will create previews for *each* PR in the stack, *except* for any that include `[skip preview]` in their title.
- **Manual**: Render will create previews only for PRs in the stack that include `[render preview]` in their title.

**Each preview creates new resources that are billed according to their compute plans and other specs.** If you use automatic previews, this change might increase your preview-related costs.

- Learn more about previews in the documentation for [service previews](https://render.com/docs/service-previews#stacked-pull-requests) and [preview environments](https://render.com/docs/preview-environments#stacked-pull-requests).
- To enable previews for stacked PRs sooner, reach out to our support team in the [Render Dashboard](https://dashboard.render.com?contact-support).
</Release>

<Release date="October 22, 2026" published="2026-10-22T00:00:00.000Z" url="https://render.com/changelog/updated-default-versions-of-node-js-and-bun">
## Updated default versions of Node.js and Bun

Newly created services that use Node.js or Bun now default to the following versions:

- [Node.js 24.22.1](https://nodejs.org/en/blog/release/v24.22.1)
- [Bun 1.4.4](https://bun.com/blog/bun-v1.4.4)

You can always specify a different version of [Node.js](https://render.com/docs/node-version) or [Bun](https://render.com/docs/bun-version).

*Existing* services keep their original default versions to prevent breaking changes.
</Release>

<Release date="October 16, 2026" published="2026-10-16T00:00:00.000Z" url="https://render.com/changelog/added-support-for-bun-canary-builds">
## Added support for Bun canary builds

Render now supports [canary builds](https://bun.com/docs/installation#canary-builds) for Bun. Canary builds let you preview upcoming Bun features before they reach a stable release.

To use canary builds, do one of the following:

- Set your service's `BUN_VERSION` environment variable to `canary`.
- Add a `.bun-version` file to the root of your repo with the single line: `canary`.

**Don't use Bun canary builds for production services.** Canary builds are untested pre-releases. Learn more about [setting your Bun version](https://render.com/docs/bun-version).
</Release>

<Release date="October 1, 2026" published="2026-10-01T00:00:00.000Z" url="https://render.com/changelog/added-two-key-value-plans-and-lowered-prices-for-larger-existing-plans">
## Added two Key Value plans and lowered prices for larger existing plans

Render now supports two additional [compute plans](https://render.com/docs/compute-plans#render-key-value-plans) for Key Value instances:

- **3 GB RAM** with up to 3,000 simultaneous connections
- **50 GB RAM** with up to 50,000 simultaneous connections

We've also reduced pricing for existing Key Value compute plans that provide at least 1 GB RAM. The reduced pricing takes effect for all applicable Key Value instances starting October 1.

View all available plans and their latest pricing on the [pricing page](https://render.com/pricing#key-value). Learn more about Render Key Value in the [docs](https://render.com/docs/key-value).
</Release>

<Release date="September 16, 2026" published="2026-09-16T00:00:00.000Z" url="https://render.com/changelog/added-blueprint-support-for-render-workflows">
## Added Blueprint support for Render Workflows

You can now manage your workflow services using [Blueprints](https://render.com/docs/infrastructure-as-code), Render's infrastructure-as-code model.

Define workflows alongside other service types in your Blueprint YAML. Here's an example:

```
services:
  - type: workflow
    name: my-workflow
    runtime: python
    region: oregon
    repo: https://github.com/render-examples/render-workflows-examples-python
    branch: main
    rootDir: hello-world
    buildCommand: pip install -r requirements.txt
    startCommand: python main.py
```

Workflows support *most* of the same configuration fields as other service types, with exceptions noted in the [Blueprint YAML Reference](https://render.com/docs/blueprint-spec#service-fields). Notably, you don't provide a `plan` field for workflows, because you instead specify compute plans per task [directly in your code](https://render.com/docs/workflows-defining#compute-plan).

**Note the following:**

- Workflows do not yet support [preview environments](https://render.com/docs/preview-environments), which *skip* replicating any workflows present in your Blueprint (other services are replicated as usual).
- Render rejects a Blueprint that would create a workflow with the same name as an existing Blueprint-managed workflow in your workspace.

Learn more about Render Workflows in the [documentation](https://render.com/docs/workflows).
</Release>

<Release date="September 3, 2026" published="2026-09-03T00:00:00.000Z" url="https://render.com/changelog/see-your-service-s-deploys-on-a-new-page">
## See your service's deploys on a new page

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

The **Deploys** page features:

- Your service's deploy history, without a date cutoff.
- A **Live** badge indicating the current deploy.
- Status of in-progress deploys.
- A banner flagging when auto-deploys are disabled.

Previously, deploys were only visible on the **Events** page, interspersed with other events, and capped at a 90-day history. The **Events** page continues to show all service events, including deploys.

Cron jobs also have new **Builds** and **Runs** pages that separate build and run history.

Learn more in the [documentation](https://render.com/docs/deploys).
</Release>

<Release date="September 1, 2026" published="2026-09-01T00:00:00.000Z" url="https://render.com/changelog/added-usage-telemetry-to-the-render-cli">
## Added usage telemetry to the Render CLI

The [Render CLI](https://render.com/docs/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.

Telemetry includes the following:

- Commands run (e.g., `render services list`)
- Command performance and completion status
- CLI version
- System information
- Execution context

The Render CLI does *not* collect sensitive user data, such as command arguments, environment variable values, passwords, or the contents of your files.

You can disable telemetry at any time by setting either the `RENDER_CLI_DISABLE_ANALYTICS` or `DO_NOT_TRACK` environment variables. For example:

```
export DO_NOT_TRACK=1
```

Learn more in the [documentation](https://render.com/docs/cli#usage-telemetry).
</Release>

<Release date="September 1, 2026" published="2026-09-01T00:00:00.000Z" url="https://render.com/changelog/introduced-the-flex-compute-plan-for-render-workflows">
## Introduced the Flex compute plan for Render Workflows

[Render Workflows](https://render.com/docs/workflows) uses a new default compute plan for task runs: **`flex`**.

The `flex` compute plan provides up to 1 CPU and 4 GB of RAM. Task runs on `flex` are billed only for the CPU and RAM they actually use, resulting in significantly lower costs for computationally inexpensive runs.

The `flex` compute plan replaces the `starter` and `standard` compute plans for Render Workflows. Tasks that previously used `starter` or `standard` now automatically use `flex` instead.

For tasks with higher resource requirements, you can assign a different compute plan in your [task's definition](https://render.com/docs/workflows-defining#compute-plan):

```
const myTask = task(
  {
    name: 'myTask',
    plan: '2c-4g' //highlight-line
  },
  function myTask(ctx: TaskContext, a: number): number {
    return a * a
  }
)
```

Learn more about compute plans for Render Workflows in the [documentation](https://render.com/docs/workflows-limits#compute-plans).
</Release>

<Release date="August 26, 2026" published="2026-08-26T00:00:00.000Z" url="https://render.com/changelog/new-compute-plans-and-new-ids-for-existing-plans">
## New compute plans, and new IDs for existing plans

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.

To support the expanded catalog, we're also changing compute plan IDs to a spec-based format that includes the relevant specs. For example a web service compute plan with 4 CPU and 32GB RAM now carries the ID `4c-32g`. This convention allows you to more easily intuit the specs of compute plans as we add additional options.

**No action is needed to continue using your current compute plan(s).** While you will see the IDs for plans change in the Render Dashboard and documentation, you can continue to use old plan IDs with the Render API, SDK, CLI, and Blueprints. To avoid any issues when you start using the new plan IDs, we recommend updating to the latest versions of Render clients and integrations, including the CLI and Terraform provider.

You can see the mapping of old plan names to new plan IDs in the Render Dashboard.

**What’s new:**

- **Increase memory without increasing CPU.** At each 2+ CPU tier (2 CPU, 4 CPU, 8 CPU, etc.) we are adding multiple plans with more RAM. For example, at 2 CPU you can now choose between web service plans with 4 GB, 8GB, and 16 GB RAM.
- **12-CPU plans for heavy workloads.** For customers running agent platforms or other heavy workloads, we are adding a set of 12-CPU plans with up to 96GB RAM.
- **New compute plan IDs.** To keep plan IDs intuitive as we add more options, we are replacing legacy IDs (Pro Plus, Pro Ultra, etc) with simple spec-based IDs. For example, the 2 CPU 4 GB web service plan now has an ID of `2c-4g`. **The Render API, CLI, SDK, and Blueprints will remain backward compatible with legacy plan IDs. No action is required.**
- "Compute plan" replaces "instance type" across the dashboard, API, CLI, and docs.
</Release>

<Release date="August 7, 2026" published="2026-08-07T00:00:00.000Z" url="https://render.com/changelog/reduced-median-service-build-time-by-40-all-runtimes">
## Reduced median service build time by 40% (all runtimes)

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:

Before this rollout (week of July 13), median build time was 38 seconds, consistent with prior weeks. Since July 27 (the first full week post-rollout), the highest observed weekly median is 21 seconds, a conservative 40% reduction. Build times remain in this range.

This global build improvement follows recent single-runtime improvements for [Node.js](https://render.com/changelog/reduced-median-build-time-for-node-js-services-by-25-percent), [Python](https://render.com/changelog/reduced-median-python-service-build-time-by-27-percent), and [Docker](https://render.com/changelog/reduced-median-docker-image-build-time-by-60-percent).
</Release>

<Release date="July 24, 2026" published="2026-07-24T00:00:00.000Z" url="https://render.com/changelog/managed-oidc-now-supports-anthropic-and-openai">
## Managed OIDC now supports Anthropic and OpenAI

Render’s managed [OpenID Connect (OIDC)](https://render.com/docs/oidc) authentication now supports **Anthropic** and **OpenAI** in addition to AWS.

Render services can authenticate to both providers without storing long-lived API keys. Render instead issues short-lived identity tokens for each service and automatically rotates them as needed.

To configure either provider, connect Render as an identity provider, map the appropriate service account, and add the required environment variables to your Render service. After you redeploy, Render automatically makes the service’s OIDC token available at runtime.

Managed OIDC requires a **Pro** workspace or higher. Get started in the [documentation](https://render.com/docs/oidc).
</Release>

<Release date="July 22, 2026" published="2026-07-22T00:00:00.000Z" url="https://render.com/changelog/render-mcp-now-supports-oauth-for-claude-code-codex-and-cursor">
## Render MCP now supports OAuth for Claude Code, Codex, and Cursor

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

The MCP server continues to support API key authentication for other applications and non-interactive environments, such as CI/CD.

See setup instructions for each supported tool in the [documentation](https://render.com/docs/mcp-server#1-connect-to-the-mcp-server).
</Release>

<Release date="July 17, 2026" published="2026-07-17T00:00:00.000Z" url="https://render.com/changelog/trigger-service-deploys-with-the-render-mcp-server">
## Trigger service deploys with the Render MCP server

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.

Get started with the Render MCP server and learn about all of its capabilities in the [documentation](https://render.com/docs/mcp-server).
</Release>

<Release version="1.3.14" date="July 16, 2026" published="2026-07-16T00:00:00.000Z" url="https://render.com/changelog/default-bun-version-updated-to-1-3-14">
## Default Bun version updated to 1.3.14

Newly created services now use [Bun 1.3.14](https://bun.com/blog/bun-v1.3.14) by default. You can always [specify a different version](https://render.com/docs/bun-version).

Existing services keep their original default Bun version to prevent breaking changes.
</Release>

<Release date="July 15, 2026" published="2026-07-15T00:00:00.000Z" url="https://render.com/changelog/render-to-aws-oidc-authentication-now-generally-available">
## Render-to-AWS OIDC authentication now generally available

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

Render services can use OIDC to assume an AWS IAM role at runtime, giving them secure access to AWS resources without long-lived credentials. Render automatically issues and rotates the temporary credentials used by each service.

To configure OIDC for AWS, connect Render as an identity provider in AWS IAM, create the appropriate trust relationships, and assign an IAM role to each service using the `AWS_ROLE_ARN` environment variable.

Get started in the [documentation](https://render.com/docs/oidc).
</Release>

<Release date="July 1, 2026" published="2026-07-01T00:00:00.000Z" url="https://render.com/changelog/add-connection-pooling-to-your-render-postgres-database">
## Add connection pooling to your Render Postgres database

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:

Render runs PgBouncer on the same underlying host as your database to minimize the latency introduced by the additional hop.

Enable connection pooling from your database's **Info** page in the [Render Dashboard](https://dashboard.render.com):

You can also enable connection pooling using Blueprints or the Render API.

**Enabling connection pooling requires a database restart.** After the restart, update your clients to use your database's new connection pool URL (port `6432`) instead of its direct connection URL (port `5432`).

Learn more in the [documentation](https://render.com/docs/postgresql-connection-pooling).
</Release>

<Release date="June 30, 2026" published="2026-06-30T00:00:00.000Z" url="https://render.com/changelog/manage-postgres-and-key-value-instances-using-the-render-cli">
## Manage Postgres and Key Value instances using the Render CLI

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](https://render.com/docs/cli).

Use `render kv` commands to manage Key Value instances:

```
render kv create \
  --name jobs-cache-staging \
  --region oregon \
  --plan starter \
  --memory-policy queue \
  --confirm
```

Use `render pg` commands to manage Postgres databases:

```
render pg create \
  --name app-db-staging \
  --region oregon \
  --plan basic_256mb \
  --version 17 \
  --confirm
```

Run `render kv --help` or `render pg --help` for a list of supported commands, or see the full [generated command reference](https://render.com/docs/cli-reference).

With these additions, the Render CLI now provides management capabilities for every Render [service type](https://render.com/docs/service-types#summary-of-service-types).

Get started with the Render CLI in the [docs](https://render.com/docs/cli).
</Release>

<Release date="June 11, 2026" published="2026-06-11T00:00:00.000Z" url="https://render.com/changelog/reduced-median-docker-image-build-time-by-60-percent">
## Reduced median Docker service build time by 60%

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

- Tuning chunk size and parallelism for build image uploads
- Speeding up build scheduling on Render infrastructure
- Parallelizing generated image upload with export to build cache
- Storing build cache in Render's own image registry with automatic pruning

Together, these optimizations have reduced median build time for Docker-based services by 60%:

Before these optimizations (week of March 15), median build time was 87 seconds, consistent with prior weeks. After all optimizations landed, the highest weekly median observed has been 32 seconds (a conservative 60% reduction). Build times remain in this range.
</Release>

<Release date="June 11, 2026" published="2026-06-11T00:00:00.000Z" url="https://render.com/changelog/specify-disk-persistence-behavior-for-paid-key-value-instances">
## Specify disk persistence behavior for paid Key Value instances

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

- **Journal + Snapshot:** Append writes to a journal and periodically save full snapshots.
    -   This matches the behavior of *all* paid Key Value instances before this release.
- **Snapshot only:** Disable journaling while continuing to save periodic snapshots.
- **Off:** Disable all disk-backed persistence.

Reducing persistence can improve write performance for loss-tolerant use cases, such as a shared cache.

You specify your instance's persistence mode on creation:

You can change your instance's persistence mode in the Render Dashboard or using the [Render API](https://api-docs.render.com/reference/update-key-value). Note the following:

- Changing your persistence mode requires a restart, during which your Key Value instance is unavailable for a few seconds.
- If you change your mode to or from **Off**, all data in your instance is lost after the restart.

Learn more about Key Value persistence modes in the [documentation](https://render.com/docs/key-value#data-persistence).
</Release>

<Release date="June 5, 2026" published="2026-06-05T00:00:00.000Z" url="https://render.com/changelog/authenticate-render-services-with-aws-using-oidc">
## Authenticate Render services with AWS using OIDC

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.

The setup flow looks like this:

1. Add Render as an OIDC identity provider in AWS IAM.
2. Create or update IAM roles that trust the Render OIDC provider.
3. Add an `AWS_ROLE_ARN` environment variable to each Render service with the IAM role ARN it should assume.
4. Redeploy each service. Render starts issuing and rotating OIDC credentials automatically.

Get started in the [documentation](https://render.com/docs/oidc).
</Release>

<Pagination cursor="2026-06-05T00:00:00.000Z|2026-06-06T02:02:17.339Z|rel_wRtRr7UzZ16vThryIy8jU" next="https://releases.sh/render/render-changelog.md?cursor=2026-06-05T00%3A00%3A00.000Z%7C2026-06-06T02%3A02%3A17.339Z%7Crel_wRtRr7UzZ16vThryIy8jU&limit=20" />
