Releasesby GlyphIntroduced 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.
Also shipped Sep 1, 2026Render in September 2026 →
Fivetran connection cron scheduling enters beta
Connections can now use one or more cron expressions to control exactly when they sync, giving finer control than fixed sync frequencies.
Fivetran Connection Warnings REST API enters private preview
New endpoints retrieve active warnings for a connection, grouped by destination table with codes, messages and timestamps, and dismiss all instances of a warning type, enabling programmatic warning management.
Snowflake App Runtime (General availability)
Snowflake App Runtime is now generally available and is no longer in Preview .
Apache Arrow support for Zerobus Ingest is now generally available
Apache Arrow support for Zerobus Ingest in Lakeflow Connect is now generally available. See Use Arrow Flight with Zerobus Ingest .
Genie One web search is in Beta
Genie One can now search the public web to answer questions that need current information, such as recent release notes, third-party documentation, or news. Genie One cites the external sources it uses as links in its response. See Search the web .
More from RenderEvery Render release →
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.
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.
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 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.
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.
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.
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.
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 .