Releasesby GlyphAdded Blueprint support for Render Workflows
You can now manage your workflow services using Blueprints , Render's infrastructure-as-code model. Define workflows alongside other service types in your Blueprint YAML.
Also shipped Sep 16, 2026Render in September 2026 →
BigQuery migration lineage service enters preview
The migration lineage service visualizes data flow and connections in a source database to help plan a BigQuery data warehouse migration.
Cortex Agents object enhancements (General availability)
The following Cortex Agents object enhancements are now generally available:
Include and exclude per-user quota users by name (General availability)
Per-user quotas now accept individual user names, so you can add or remove specific users alongside the quota's tag scope. INCLUDE_USERS is new and takes user names directly, and EXCLUDE_USERS accepts a 'USER' argument alongside its existing 'TAG' form:
Weekly per-user quota limits (General availability)
Per-user quotas now support a weekly credit limit alongside the existing monthly and daily limits. Pass 'WEEKLY' as the cycle argument to SET_PER_USER_LIMIT :
Anthropic models will be removed from AWS GovCloud IL5 workspaces
On September 19, 2026, Anthropic models will be removed from Databricks on AWS GovCloud and AWS GovCloud DoD workspaces that have the DoD Impact Level 5 (IL5) compliance standard selected. After this date, IL5 workspaces can't create or use endpoints that serve Anthropic models.
Unity Gateway API and developer tools are generally available
The Unity Gateway API for managing model services, model provider services, and MCP services is now generally available, with create, read, update, list, and delete support across Databricks developer tools: Terraform provider : 1.132.0 and later Databricks CLI : v1.17.0 and later Python SDK : databricks-sdk 0.136.0 and later Go SDK : databricks-sdk-go...
More from RenderEvery Render release →
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.
Added two Key Value plans and lowered prices for larger existing plans
Render now supports two additional compute 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.
Introduced the Flex compute plan for Render Workflows
Render 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.
Added usage telemetry to the Render CLI
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.
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.
Added support for Bun canary builds
Render now supports 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 .
Updated default versions of Node.js and Bun
New services on Render now default to Node.js 24.22.1 and Bun 1.4.4.
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.