Feature Requests

Currently, Render only triggers Preview Environments for pull requests where the target base branch is the Blueprint’s linked branch (usually main). With GitHub's introduction of native stacked pull requests, developers can now create linear chains of dependent PRs where a downstream feature branch targets an upstream feature branch instead of main (e.g., feature-B targeting feature-A). Because Render strictly checks for the linked branch on incoming PR webhooks, all intermediate and downstream stacked PRs are ignored, and no Preview Environments are deployed for them. Teams cannot easily preview, test or share progress on individual segments of a stacked PR chain. The only current workarounds are manually changing the PR target branch back and forth in GitHub to trick Render into building it, or maintaining complex custom GitHub Actions with Deploy Hooks. Please add support for triggering Preview Environments on PRs that target non-linked branches or introduce native awareness of GitHub’s stacked PR metadata.

Symptom: Dashboard shows both domains Verified + Certificate Issued, but TLS handshake fails with WRONG_VERSION_NUMBER since ~02:15 UTC today (3+ hours). Removing the domains from the service had no effect on edge behavior. Root evidence: A raw TLS ClientHello to ingress IP 216.24.57.16:443 with SNI= enagafly.cc receives 200+ bytes of 0xFF instead of a ServerHello. The identical ClientHello with SNI= inventory-api.eslitec.com (another custom domain on our account, same IP) receives a normal 16 03 03 ServerHello. A completely unknown SNI receives a proper handshake_failure alert. So the edge recognizes enagafly.cc but its binding is corrupted — this is not a DNS or certificate issuance problem on our side. Ruled out: DNS correct (Cloudflare DNS-only, CNAME → inventory-frontend-uu53.onrender.com , flattened apex, no CAA). Default hostname inventory-frontend-uu53.onrender.com serves fine. Reproduced from 5 clients across 2 networks. Ask: Please purge and re-push the edge hostname binding for these two domains.

automate workflow

Currently (as of Sep 2026), the older packageManager top-level field in package.json is supported, but this is marked as legacy by pnpm docs ( https://pnpm.io/package_json#devenginespackagemanager ). pnpm v11+ self-manages pnpm versions by default using the modern devEngines.packageManager field. The current latest version of pnpm is v12 (the Rust rewrite). Using either v11 or v12 would enable usage of the modern devEngines.packageManager field.

Ok, preview is great but sometime having a staging groups of apps and a production groups of apps is great. And, in my opinion, it should be great to group apps and to allow a easy way to merge a group to another; like merge staging group to production. Voilà.

CNAME removal can be forgotten when a service is deleted from Render. Render should: Alert us if we are still pointing a CNAME without a corresponding service Add a reminder to delete the CNAME when deleting a service NOT allow re-use of service name between tenants even when that service has been deleted Add a tenant ID subdomain to the onrender.com links (eliminates the problem)

Deploying services for better latency.

I am developing a Spring Boot backend for my portfolio. Users in Madagascar experience high latency with current regions (Frankfurt or Singapore). A region in Africa (for example South Africa, Kenya, or Madagascar) would reduce latency and improve the experience for local visitors.

Render currently offers built-in, free DDoS protection powered by Cloudflare. We also offer Inbound IP Rules: https://render.com/docs/inbound-ip-rules . This post is about offering a broader, configurable Web Application Firewall. Please share specific features you'd like to see in a WAF.