Render

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.

OpenID Connect (OIDC) authentication for AWS is now generally available for Pro workspaces and higher.

OpenClaw starts from a specific premise: your personal AI assistant should run on machines you control. Local-first. Single-user. Always-on. Reachable through the channels you already use.

Every product team knows the moment. The launch goes well. The demo lands. And then the real work begins — the work that never makes the announcement.

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:

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.

The Render Team

In recent weeks, we've gradually rolled out a number of optimizations for Dockerfile-based service builds on Render. These optimizations include:

Paid Render Key Value instances now support three different disk persistence modes:

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.

In recent weeks, we've gradually rolled out a number of build optimizations for Render's Node.js native runtime, including:

We're excited to announce that LaunchPad Lab, a Chicago-based digital product consultancy with over 12 years of experience building mission-critical software, has joined the Render partner ecosystem.

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.

You push code, Render deploys it. Zero downtime, health checks, built-in rollbacks, no fuss. For most teams, that workflow is perfect.

Dedicated IPs for your services on Render

Pro workspaces and higher can now create sets of dedicated IPs to send outbound service traffic through static, reserved addresses:

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.

This guest post is kindly contributed by LlamaIndex, who help teams automate document processing with agent-powered OCR.

In recent weeks, we've gradually rolled out a number of build optimizations for Render's Python native runtime, including:

This guest post is kindly contributed by Descope, who help developers build secure, frictionless authentication and user journeys for applications.