Feature Requests

When custom domains are active, provide an option to do one of the following: * Disable the onrender.com subdomain * Redirect it to one of the custom domains. * Keep the site as-is but add a noindex header to all responses from the onrender.com subdomain. https://developers.google.com/search/docs/advanced/crawling/block-indexing Benefits: * Security [1] * SEO [2] ---- [1] When using a custom domain one of the benefits is that instead of having the DNS pointing to Render, you can point it to Cloudflare (for example) as a proxy. This reduces load on the origin server and the {project}. onrender.com seems like a bit of a loose-end. Could somebody DDoS this server, bypassing cloudflare's protection? (Similar to https://render.canny.io/features/p/add-option-to-redirect-the-onrendercom-subdomain-to-the-primary-custom-domain-fo ) [2] Add x-robots-tag: noindex header to deploys without assigned custom domains. This would allow testing one's full Web site content on Render without needing to alter a repo's existing "robots.txt" file yet avoid risking the duplicate-content penalty from Google and other search vendors. Similar functionality is provided by Vercel ( https://vercel.com/docs/v2/edge-network/headers?query=robot#inlinecode ).

uv is an extremely fast Python package and project manager, written in Rust. Supporting this will make deployments way faster. Instead of "poetry install" for Build Command, will be great to have available "uv install" This is uv: https://docs.astral.sh/uv/

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

DB + Webservice

It would be super useful to be able to do something like this in the render.yaml file: environments: - name: my-project-prod previewsEnabled: false services: # ... envVarGroups: # ... databases: # ... - name: my-project-staging previewsEnabled: true services: # ... envVarGroups: # ... databases: # ... It's basically "just" nesting the current content of the render.yaml file into the environments array. This would enable workflow such as having prod without preview environments and then having staging with preview environments. Workflow like that is currently impossible to achieve when I want to use infrastructure as a code.

Support compliance with HIPAA and enable requesting a Business Associate Agreement (BAA) from Render

According to the documentation, the deployment downtime with disks is in the order of few seconds. However, with my current test Go app, re-deployment time in frankfurt region takes around a minute and more. I'd love to see this time-span shorter.

Call GitHub Deployments API automatically after a Render deployment is started, canceled, successful, etc. It would be really useful to see all the currently running environments on GitHub with all the details: environment url log url deployment details date & time of deployment commit deployed etc.

Render already caches well known paths for all native language environments. No other directories are cached. Users can also copy and restore extra data they'd like to cache to the directory specified by the $XDG_CACHE_HOME environment variable. But there are other custom directories or files that would benefit from automatic caching without needing to copy and restore files from $XDG_CACHE_HOME . For example, a .node_modules directory in a non-root directory. Enable specification of additional cache directories relative to the root of the project.

I would like to use Render's CDN for static sites to serve static assets for my non-static apps built with frameworks like Rails or Django. This would let me turn off the option for Rails to serve static files. In a typical setup, this would be off and static assets would be served directly from the CDN and these requests would never hit the (comparatively slow) Rails app.