Feature Requests

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

Please please please let us create API keys limited to specific projects/environments/services, with permission levels (read-only, deploy, full). This would be for agent controlled deployments. I run an autonomous AI agent that should be able to deploy, read logs, and manage env vars for our dev services, but have zero access to production. Today every API key has full account access, so the only workaround is a separate workspace plus a separate user account, which is clunky. This is becoming common as more teams let AI agents handle deployments. Scoped keys would make Render the safest place to do it.

Dublin, Ireland being in the EU but also closer proximity to the US than Frankfurt.

web development

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.

Render API keys / tokens are not per-workspace or per-org, and has access to all workspaces that I have. Vanta, one of the most common SOC 2 compliance vendor, requires Render API key for integration, and this limitation complicates as we don't want to provide a personal API key that can access to a lot more external organizations and workspaces.

Add the Apache AGE postgres plugin to enable using Postgres as a Graph DB and avoid an outside call to Neo4J/Memgraph/etc.

I would like to be able to change the onrender.com subdomain after I create the web-service in case I made a mistake in naming or if I want to change the naming for logical grouping, etc..

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