Recent changes
We've rolled out new workspace plans to make Render’s pricing more scalable for modern, fast-growing teams. Each new workspace plan corresponds to a legacy plan: Hobby (free) replaces the legacy Hobby plan. Pro ($25/month flat) replaces Pr…
Newly created Node.js services now use Node.js 24.14.1 by default. You can always specify a different version. Existing Node.js services keep their original default version to prevent breaking changes.
You (and your agents) can now create new services directly from the terminal using the Render CLI's services create command: render services create \ --name hello-world \ --type web_service \ --runtime node \ --region virginia \ --plan fre…
Render's native Go environment now automatically updates to the latest stable Go 1.x version, usually within 24 hours of a new release. After an update, your service starts using the new version with its next deploy. Previously, we handled…
Render Workflows is now in public beta, with SDK support for TypeScript and Python. Define durable tasks and chain them into long-running background processes for agent logic, data pipelines, billing flows, and more. Deploy your task defin…
Workspace audit logs now include the EndShellEvent event type, which indicates that a workspace member closed an active dashboard shell or SSH session to a Render service. Audit logs already included StartShellEvent, which is logged when a…
Free web services now spin down after going 15 minutes without receiving either of the following: An incoming HTTP request An incoming WebSocket message from an existing connection Previously, only incoming HTTP requests delayed spindown.…
Newly created Python services now use Python 3.14.3 and uv version 0.10.2 by default. You can always specify a different version of both Python and uv. Existing Python services keep their original default versions to prevent breaking chang…
New command: render workspaces By default, render workspaces lists your available workspaces in an interactive menu. Optionally, you can also list workspaces in plaintext, JSON, or YAML format. For example, the following command lists work…
Blueprints (Render's infrastructure-as-code model) now support custom filenames and paths for YAML configuration files. Previously, Blueprints required a file named render.yaml in your repository's root directory. You can specify a custom…
In rare cases, Render would erroneously emit an Autoscaler starting to scale down to 0 instances event for services with autoscaling enabled. These events were triggered by momentary latency in scaling metrics, and they did not modify the…
