npx @buildinternet/releases get renderRecently cut Key Value prices by up to 45%, added two larger plans, and opened a build-reuse private beta.
Key Value got cheaper and bigger. Every paid Key Value plan at 1GB or above costs 20–45% less as of October 1, applied automatically to services already running. Two new tiers fill the gaps: 3GB with up to 3,000 simultaneous connections, and 50GB with up to 50,000. Paid instances also choose their own persistence mode — journal+snapshot, snapshot-only, or off — so cache-style workloads can skip write overhead.
Build reuse across services entered private beta. Services built from the same repository or image can share build artifacts instead of rebuilding identical code, so a commit promoted from staging to production ships the same artifact rather than a fresh compile. Access is request-only for now.
Workflows can be defined in Blueprints. Workflow services now sit alongside other service types in Blueprint YAML, with compute plans set per task in code rather than through a plan field. Preview environments aren't supported yet.
Earlier ships still in play.
- Docker build medians fell from 87s to 32s; Node.js from 42s to 31s; Python from 76s to 55s.
- Pro workspaces authenticate to AWS with OIDC, rotating credentials at runtime instead of storing long-lived keys.
render ssh --ephemerallaunches an isolated copy of a production build, runs no start command, and disappears on disconnect.- Workspace pricing dropped seat fees: Pro is $25/month flat with unlimited members; Scale is $499/month flat, adding SSO, SCIM, HIPAA-enabled workspaces, and advanced RBAC.
- Dedicated IPs give Pro workspaces three static IPv4 addresses per region for allowlisting with external databases.
Render now supports two additional compute plans for Key Value instances:
By default, Render rebuilds your code every time you deploy, even if the code hasn't changed from the previous build. But if you're deploying the same commit to staging then promoting to production, or running multiple services from one repository, you shouldn't have to wait for…
You can now manage your workflow services using Blueprints, Render's infrastructure-as-code model.
Services now have a new Deploys page in the Render Dashboard.
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.
Render Workflows uses a new default compute plan for task runs: flex.
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.
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: