Feature Requests

We build agents that run phone calls. They're long lived (a websocket connection for the duration of the call), so deployments are weird. What I would like is to be able to spin up new instances on deploy, THEN send a SIGINT to the old instances, but wait up to 30 minutes for them to finish existing calls and shut down.

Certain builds can benefit from more cores and increased RAM. Allow selecting build CPU and RAM configurations by service.

Currently if you enable PR previews or preview environments for a service, Render generates a preview for every PR unless you skip it with a title string like [skip render] . Add the ability to instead opt _in_ to previews per-PR, making _no_ preview the default behavior.

Can you add support for Bun applications? i have an express node js app and i want to migrate to Bun. Thank you

I would like to have an easy way to run certain things right before something gets deployed, similar to the "release phase" on Heroku ( https://devcenter.heroku.com/articles/release-phase ). I'm thinking of migrating the db or uploading assets.

Some PRs don't need a preview. It'd be nice if I could indicate this by putting something like [skip preview] or [preview skip] in the PR title or description.

It seems the only way to cancel a deploy is to manually deploy a new one. I would like to be able to cancel a deploy without deploying a new one.

Ability to set render preview available for a limited time (e.g. 6hrs) after which it turns off on its own

The ability to restart servers via the UI was just completed ( https://feedback.render.com/features/p/ability-to-restart-servers ) but it isn't possible to trigger a restart via the API. For those of us who are currently running scheduled restarts because of memory leaks or other issues, it'd be great to be able to trigger a restart - not a redeploy - via the API.

Sometimes we have stale PRs that hand around for a long time without being worked on, before being picked up again and merged. The way render works right now, the services for those PRs keep running so long as the PR is open and that can get expensive. Could we configure PR previews to expire after a specific number of days in render.yml ? (After which they are deleted automatically)