Feature Requests

Just use the previously build container image. Even better would be to cache the git ref, so even if the same ref is being published to a new branch (perhaps staging => production) it will be a fast deploy.

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

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.

Notification Service and Event Streaming

I would like an easy way to deploy and connect to a MongoDB instance in Render.

Proposal It would be really nice to have the following syntax available in render.yaml : envVars: - fromGroup: my-production-env-group - fromGroupPreviewOverride: my-preview-env-group This problem has come up several times in the community and is one of the most important parts of a streamlined CI/CD workflow. I would love to see it on the roadmap :) Problem statement Currently, there are 3 options for overriding environment variables in preview environments: Solution 1 Define them in plaintext within render.yaml : envVars: - key: MY_ENV_VAR value: production-value previewValue: preview-value This works for values that can be shared, but is not suitable for private secrets (which is a pretty common use-case) Solution 2 Define them with sync: false and manually fill them in on each PR. This works, but is extremely time consuming, especially if your env file has 10+ variables to fill in. Solution 3 (workaround) Omit environment groups from render.yaml altogether, but still reference them in your services. For example: envVars: - fromGroup: my-production-env-group - fromGroup: my-preview-env-group From here, you must write additional logic into your application to choose the correct variable based on the environment. let myVariable; if (process.env.NODE_ENV === 'development') { myVariable = process.env.LOCAL_VALUE } if (process.env.NODE_ENV === 'production') { // https://render.com/docs/environment-variables#all-services if (process.env.IS_PULL_REQUEST) { myVariable = process.env.PREVIEW_VALUE } else { myVariable = process.env.PROD_VALUE } } In my opinion, this 3rd solution is the best, but still isn't great because it requires you to expose production variables in your preview environment.

I can use Docker to run PHP apps but it would be great to have native PHP support in Render.

Would love to be able to mark certain secret files as build-only. I don't want to risk a runtime security bug exposing secrets that can -- for example -- clone certain private Git repositories. I'm using the Docker builder.

I can search application and request logs using the built-in log explorer in the Dashboard. However, I would like the ability to export the logs without needing an external provider (e.g., log streams). I want to export a subset of filtered logs to a static file for offline analysis. There should be two export formats: Plain text file: pretty much what I see in the UI CSV file: structured data, where there are columns for log level, status code, HTTP method, request ID, etc.. Timestamps in exported logs should also be in UTC, not localized.