Data and AI releases

548 this month · 176 companies

Trigger service deploys with the Render MCP server

UpdateNot yet verified

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.

AI agentsMCP

Read on render.com

Also shipped Jul 17, 2026Render in July 2026 →

Anthropic managed ingestion connector (Beta)

The Anthropic connector in Lakeflow Connect is now available in Beta. The connector allows you to ingest Compliance API data , audit activity, organizations, users, roles, groups, settings, and Claude chats and messages , from Anthropic into Databricks. See Anthropic connector .

Beta
Source ↗

More from RenderEvery Render release →

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 ↗

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 ↗

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 ↗

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.

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 ↗

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 ↗