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. Here's an example:services: - type: workflow name: my-workflow runtime: python region: oregon repo: https://github.com/render-examples/render-workflows-examples-python branch: main rootDir: hello-world buildCommand: pip install -r…
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.Previously, deploys were only visible on the Events page, interspersed with other events, and capped at a 90-day history. The Events page…
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.The flex compute plan replaces the starter and standard compute plans for Render Workflows. Tasks that previously used sta…
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.Telemetry includes the following:Commands run (e.g., render services list)Command performance and completion statusCLI versionSystem informationExecution contextThe Render CLI does not collect sensitive user data, s…
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. For example a web service compute plan with 4 CPU and 32GB RAM now ca…
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. Since July 27 (the first full week post-rollout), the highest observed weekly median is 21 seconds,…
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.To configure either provider, connect Render as an identity provider, map the appropriate service…
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.
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.Get started with the Render MCP server and learn about all of its capabilities in the documentation.
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.
OpenID Connect (OIDC) authentication for AWS is now generally available for Pro workspaces and higher.Render services can use OIDC to assume an AWS IAM role at runtime, giving them secure access to AWS resources without long-lived credentials. Render automatically issues and rotates the temporary credentials used by each service.To configure OIDC for AWS, connect Render as an identity provider in…
Paid Render Postgres databases now support connection pooling using PgBouncer at no additional cost. Enable connection pooling if your database needs to handle more concurrent client connections than its instance type allows:Render runs PgBouncer on the same underlying host as your database to minimize the latency introduced by the additional hop.Enable connection pooling from your database's Info…
You (and your agents) can now create, update, delete, suspend, and resume Render Postgres and Key Value instances using version 2.21.0 or later of the Render CLI.Use render kv commands to manage Key Value instances:render kv create \ --name jobs-cache-staging \ --region oregon \ --plan starter \ --memory-policy queue \ --confirm Use render pg commands to manage Postgres databases:render pg create…
In recent weeks, we've gradually rolled out a number of optimizations for Dockerfile-based service builds on Render. These optimizations include:Tuning chunk size and parallelism for build image uploadsSpeeding up build scheduling on Render infrastructureParallelizing generated image upload with export to build cacheStoring build cache in Render's own image registry with automatic pruningTogether,…
Paid Render Key Value instances now support three different disk persistence modes:Journal + Snapshot: Append writes to a journal and periodically save full snapshots. This matches the behavior of all paid Key Value instances before this release.Snapshot only: Disable journaling while continuing to save periodic snapshots.Off: Disable all disk-backed persistence.Reducing persistence can improve wr…
Now in beta, Pro workspaces and higher can configure OpenID Connect (OIDC) to authenticate their Render services with AWS. This enables your services to securely access AWS resources at runtime using automatically rotated credentials.The setup flow looks like this:Add Render as an OIDC identity provider in AWS IAM.Create or update IAM roles that trust the Render OIDC provider.Add an AWS_ROLE_ARN e…
In recent weeks, we've gradually rolled out a number of build optimizations for Render's Node.js native runtime, including:Tuning chunk size and parallelism for build image uploadsCaching of commonly used Node.js versionsSharing universal layers across build imagesSpeeding up build scheduling on Render infrastructureTogether, these optimizations have reduced median build time for Node.js services…
You can now SSH into an ephemeral instance of your service, which Render spins up specifically for your SSH session. This enables you to inspect your service's runtime environment and execute one-off commands without affecting your production instances.Previously, all SSH sessions connected to one of a service's running instances (except for cron jobs). This remains the default behavior.Using vers…
Pro workspaces and higher can now create sets of dedicated IPs to send outbound service traffic through static, reserved addresses:Use dedicated IPs to simplify allowlisting your Render services with external providers.Each dedicated IP set includes three IPv4 addresses in a single region. You can scope a set to your entire workspace or to specific environments.Services outside a set’s scope conti…
You can now change an existing service's backing Git repository or Docker image in the Render Dashboard. Previously, these changes required the Render API.In the Render Dashboard, open your service's Settings page.Under Build > Source, click Edit:The Update Source dialog appears.Select a new build source.If you're using a Git repo, confirm the Runtime, Build Command, and Start Command to use:(For…
In recent weeks, we've gradually rolled out a number of build optimizations for Render's Python native runtime, including:Tuning chunk size and parallelism for build image uploadsOn-disk caching of commonly used Python versionsSharing universal layers across build imagesTogether, these optimizations have reduced median build time for Python services by 27%:Before these optimizations (week of March…