Releasesby IbisUpdated default versions of Node.js and Bun
Update2 days agoUnverifiedAdded Oct 24, 2026
Newly created services that use Node.js or Bun now default to the following versions: Node.js 24.22.1 Bun 1.4.4 You can always specify a different version of Node.js or Bun . Existing services keep their original default versions to prevent breaking changes.
More Render releases
Every Render releaseAdded 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 .
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.
Added 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.
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.
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.
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.
Also shipped on Oct 22, 2026
Render in October 2026Trace and evaluate Cursor agents with Langfuse, powered by ClickHouse
Users can now connect Cursor to Langfuse to trace agent turns and analyze model and tool calls, with ClickHouse providing the underlying analytics infrastructure.
The AI.TRANSLATE function lets you translate text strings between languages
The AI.TRANSLATE function lets you translate text strings between languages. AI.TRANSLATE supports standard Neural Machine Translation (NMT) workloads and Translation LLM (TLLM) capabilities. This function is generally available (GA).
Replit Monitoring Agent: Your very own software engineering team
Replit Monitoring Agent is an autonomous tool that investigates production alerts, identifies causes, applies fixes, and deploys them to production for internal apps.
Microsoft Entra ID connector is available in Beta
The managed Microsoft Entra ID connector is now available in Beta in Databricks Lakeflow Connect. Use the connector to ingest Microsoft Entra ID users, groups, applications, service principals, directory roles, identity configuration, and audit and sign-in logs into Databricks.
You can configure Direct VPC ingress for Cloud Run instances ( Preview )
You can configure Direct VPC ingress for Cloud Run instances ( Preview ). Direct VPC ingress lets Cloud Run instances on a VPC network use their own ephemeral private IP address to communicate with each other and with other resources on the VPC network.
Gemini Enterprise: Single-user quota limits
Gemini Enterprise administrators can configure single-user quota limits on the Usage & Spending > Usage page in the Google Cloud console to prevent an individual user from using all of an edition's shared subscription quota pool.