[woodhull]

We launched our company on Render. It was great for going from zero to one very quickly but we had many problems and ended up migrating to AWS as we scaled.

* Poor visibility into detailed metrics, especially when problems happened in the render load balancer / routing mesh. We had a specific issue where a small number of requests were failing somewhere in render's infrastructure before reaching our application, and at the time there was no visibility to allow customers to know about requests that timed out or failed within render's infrastructure rather than our application. We collaborated with your team to surface and replicate the issue, but it was frustrating. I had a very good set of conversations with a product manager on your team about what we needed and why it was important in early 2024.

* At the time, the hosted postgres implementation was immature. I think this is an area you've already improved dramatically.

* Maybe you could add support for something like AWS PrivateLink so customers can run parts of their workloads on AWS securely over a private network. This would be a neat way to allow customers to stay on Render longer as their needs grow.

[anurag]

We launched HTTP request logs early in 2024, which would have made things easier to debug. Similarly, we're launching full OpenTelemetry exports in a few weeks.

Deep observability is critical for more complex environments, and things are improving dramatically on this front just as they have on Postgres.

We already support AWS PrivateLink! Reach out to [e-mail].

[jboggan]

I'm currently building on Render and I concur with the third point. Render is great right now but I know I'm going to need a more sophisticated backend data environment and analytics workloads in the future.