Feature Requests

Currently, static outbound IPs are shared with other users, which might lead to being blocked because of a misbehaving neighbor using the same IP. It would be great to have dedicated static outbound IPs that can be used in a project. This would be something like Quotaguard, but built inside Render. All web services within the same project or environment could use the same outbound IP.

For application with primarily Indian users, it makes much more sense to allow hosting apps in a Indian region.

#1 DONE 0.0s Menu #2 [internal] load metadata for docker.io/library/maven:3.9.11-eclipse-temurin-21-alpine #2 ... #3 [auth] library/eclipse-temurin:pull token for registry-1.docker.io #3 DONE 0.0s #4 [auth] library/maven:pull token for registry-1.docker.io #4 DONE 0.0s #5 [internal] load metadata for docker.io/library/eclipse-temurin:21.0.9_10-jre-alpine-3.23 #5 ERROR: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://us-west1-docker.pkg.dev/v2/token?scope=repository%3Alibrary%2Feclipse-temurin%3Apull&scope=repository%3Arender-prod%2Fdocker-mirror-repository%2Flibrary%2Feclipse-temurin%3Apull&service=us-west1-docker.pkg.dev : 403 Forbidden #2 [internal] load metadata for docker.io/library/maven:3.9.11-eclipse-temurin-21-alpine #2 ERROR: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://us-west1-docker.pkg.dev/v2/token?scope=repository%3Alibrary%2Fmaven%3Apull&scope=repository%3Arender-prod%2Fdocker-mirror-repository%2Flibrary%2Fmaven%3Apull&service=us-west1-docker.pkg.dev : 403 Forbidden ------ > [internal] load metadata for docker.io/library/eclipse-temurin:21.0.9_10-jre-alpine-3.23 : ------ ------ > [internal] load metadata for docker.io/library/maven:3.9.11-eclipse-temurin-21-alpine : ------ Dockerfile:28 -------------------- 26 | 27 | # Stage 2: The final production image 28 | >>> FROM eclipse-temurin:21.0.9_10-jre-alpine-3.23 29 | 30 | # Set the working directory -------------------- error: failed to solve: failed to fetch anonymous token: unexpected status from GET request to https://us-west1-docker.pkg.dev/v2/token?scope=repository%3Alibrary%2Feclipse-temurin%3Apull&scope=repository%3Arender-prod%2Fdocker-mirror-repository%2Flibrary%2Feclipse-temurin%3Apull&service=us-west1-docker.pkg.dev : 403 Forbidden I don't understand what the issue is. Keep on failing my deployment.

For financial services products (UK is a FinTech hub) many agreements require that data be located within the UK.

It would be nice to have GPU instances on Render for easy ML training.

for claude

I often write my apps with docker-compose to specify all the docker options. I would render to be able to read my docker-compose file, create all the services, and appropriately coordinate between them, as if I had simply run docker-compose up

Render advertises static sites as > Instant Cache Invalidation > Render insulates your site against failure by offering zero downtime deploys. Your site is built on every push to your repo and each build is fully atomic. As soon as a build succeeds, we deploy it and invalidate our CDN caches instantly so your users always see the latest working version of your site. That's misleading as render will still serve deleted assets, see https://community.render.com/t/deleted-files-are-still-served/399/17 I've been pulling my hair out over this on why we were still seeing old versions of our static site when the cache invalidation was described as "fully atomic". Please at least an option to make "every build should invalidate cache". Arguably this should also be the default behavior.

Support for IPv6 would be an ideal feature.