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.

Projects are really useful, but at the moment they are only accessible in the dashboard. I'd like to be able to configure them via blueprint yaml as well (so that I have a record of it and can version it in source control)

Add Sao Paulo region

Explanation of how to deploy these types of projects as typescript gets increasingly popular.

Projects are good but it's one more level of indirection which makes it hard to quickly go back and forth between multiple projects and/or organizations and browse deploy status. Therefore in many cases I end up deleting projects and go back to all-flat because the UX trade-offs favor the ability of browse by simple scrolling. It would be great if the top-level dashboard shows all services expanded by default, potentially in a tree-like collapsible sections / group headers per projects and environments. (better yet, save the last collapse state for next visit) Also want to add that, looking back, the most frequent reason to visit Render Dashboard is to check the deploy status and check logs. I can easily identify services that need my attention when the spinner is animating.

Right now the billing is on a global level. But it would be most useful when billing multiple clients, that this is per project (or from a other feature request, each project linked to a client) Shared services like render minutes could be calculated with the amount of minutes used by each project And of course there would be a section for non-project.

Current metrics are great, but they take up way too much space. It would be nice to be able to have a compact version, where metrics are shown in a grid. It should be a quick feature to add, even simply using TailwindCSS grid classes gets us half way there

I'd be happy to have a default project that opens when navigating to the dashboard, as I always have to click from my dashboard into my project right now :)

When I send a document to one of the APIs deployed on the Render server through the API body, the server is not able to access that document for processing. However, the copy of the server hosted on my local system is capable of performing the operation. The issue arises after hosting it on render.com , as it starts to throw errors.

It was counterintuitive to not be able to link the .env group to a service during the service set-up process, and only after. The pane for linking to .env groups should be accessible when setting up a service.