Feature Requests

Need to support clients who require Canada-domiciled data storage/processing

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 ).

Having per-environment configs easily comparable to one another. render.production.yaml, render.staging.yaml, render.qa .yaml

While Render supports storing data on disks, it would be great to have a really easy to use object storage feature with the capabilities of AWS S3. This would be accessible via S3-compatible APIs and will be used to store arbitrary blobs like images and videos.

Hello team, I would be nice to display the full hostname instead of just the hostname without the domain on the config page. xxxxxxxxxxxxxxx.frankfurt-postgres.render.com

Allow users to set account-level spending limits for variable factors.

Sometimes you might require packages that are not installed on the system. The only solution right now is to use Docker, which kind of defeats the ease-of-use reason many choose Render for. See: https://community.render.com/t/install-additional-packages/280/4

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

On GitLab, using preview environments to deploy off of every commit on an MR, I'm getting a lot of comments. If there's some way to turn down or off the comments, but keep using preview environments, please let me know. I have 3 services connected (static site, api service, test thing), so that's 6 comments on each push. It's getting in the way of MR reviews. If I'm feature requesting, I'd love (in order of preference): do status updates (like GitHub), but maybe that's a ways off when a new deploy comment comes in, delete any old comments (from the same service) allow turning off the comments (the slack integration duplicates the announcement anyway) allow changing the commenter (I could make a dummy that can't comment on MRs)