Data and AI releases

548 this month · 176 companies

Reduced median service build time by 40% (all runtimes)

UpdateNot yet verified

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.

Performance

Read on render.com

Also shipped Aug 7, 2026Render in August 2026 →

DCM Projects (General availability)

DCM Projects are now generally available and are no longer in Preview . DCM Projects enable a declarative approach to managing Snowflake objects as code. You define the desired target state of your databases, tables, tasks, and other Snowflake objects in definition files, and Snowflake determines and applies the necessary changes to reach that state.

GA
Source ↗

Tag automations (Beta)

Tag automations are now in Beta . A tag automation assigns or removes governed tags on the Unity Catalog tables or volumes that match conditions you define, so tags stay accurate as your data and metadata change.

Beta
Source ↗

Change data feed on materialized views (Beta)

You can now read a change data feed from a materialized view created in a Lakeflow pipeline or in Databricks SQL, using Databricks Runtime 18 LTS or above. Use this to replicate materialized view changes to destinations outside Databricks, or to keep a history of materialized view changes for auditing and reporting.

Beta
Source ↗

More from RenderEvery Render release →

Managed OIDC now supports Anthropic and OpenAI

Render’s managed OpenID Connect (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.

Update
Source ↗

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 .

Update
Source ↗

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.

Pricing
Source ↗

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.

Update
Source ↗

Default Bun version updated to 1.3.14

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.

Update
Source ↗

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.

Update
Source ↗

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.

Update
Source ↗

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.

Update
Source ↗