Feature Requests

I have tried using the payment web service five times, but it still won't work.

Postgres monitoring tools, such as pganalyze, pgwatch, and pgCustard, ask for a role with pg_monitor. It can read statistics, sessions, and pg_stat_statements, but not table data. On Render, the default Postgres user has CREATEROLE but not ADMIN OPTION on pg_monitor, so since Postgres 16 this fails: grant pg_monitor to monitoring_user; ERROR: permission denied to grant role "pg_monitor" It would be great if the default user could get pg_monitor WITH ADMIN OPTION.

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.

Currently, there’s no way to securely use an API key while controlling my web application. I’m developing an API to monitor the server's boot status and attempted to use the List Events feature. However, I can't keep the API key completely safe due to platform limitations. It would be beneficial to have the option to restrict the API key's access to specific actions, like only allowing it to use the List Events API.

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

Being able to fork a database for testing against current copies of production data to track any issues with particular dataset, and to to completely validate staging environments before pushing to production.

For compliance issues - servers need to be hosted in India. It would be really helpful

It would be great to have a way to host apps that are deployed in multiple regions, so the app is fast anywhere in the world. I guess this is quite a challenge, because you might also need a multi-region distributed database. But it would be great to have an easy way of building such an app without the dev-ops overhead.

When I run into an error while deploying, Gatsby (the static site generator I use) logs out all its current data in a misguided effort to be helpful. This generates extremely long logs which means using the web UI I would have to scroll up 40-50 times to get back to the actual error. Being able to download the entire logs at once and inspect them in a normal text editor would solve that problem for me.