anurag

Without knowing more about why Railway was banned, it's hard to say how we would prevent it. Render uses GCP, AWS, and now, our own hardware [1]; GCP is mostly a historical artifact; we started using AWS for most things after dealing with poor customer and sales support from GCP a few years ago.

[1] https://x.com/anuraggoel/status/2057245946652901809

also, I can't help but imagine if instead of render, it was Apple's account which could've been auto-banned (Render is almost a billion dollar company or series-B, I am not sure)

I believe you mean Railway.

Render (a $1.5B company) has been hosting customers on GCP since 2018, and has never been banned.

Under our new plans, 75% of paying Render customers will see their Render costs decrease or remain the same.

Render offers free static sites that are served via a CDN and load instantly: https://render.com/docs/static-sites

Render lets you attach a disk to your app: https://render.com/docs/disks

Render has Object Storage in alpha: https://render.com/object-storage

Render does not require a Dockerfile or understanding containers. It can also detect your runtime and deploy your app without ever generating a Dockerfile.

The one redeeming feature of this failure is staged rollouts. As someone advertising routes through CF, we were quite happy to be spared from the initial 25%.

This is a big deal because you can now run Firecracker/other microVMs in an AWS VM instead of expensive AWS bare-metal instances.

GCP has had nested virtualization for a while.

Render's built its own Postgres (we don't use RDS). Glad to hear it's working well for you!

Nuance has a unique offering: prescription hearing glasses built for noisy environments: https://www.nuanceaudio.com/en-us/c/hearing-glasses

Appreciate the extra transparency on the process.

Great to hear Render worked for you!

(Render CEO) We're prioritizing Object Storage independent of this move.

I work at Render (render.com); we have over 4 million developers on the platform, and we've migrated many large (and small) Heroku customers over because of our more modern capabilities and scalable pricing.

https://render.com/docs/migrate-from-heroku

Much-needed innovation in scaling Postgres. Congratulations on the launch!

I work at Render. We've removed the phishing website from the platform.

I'm a very happy paying customer of NextDNS (https://nextdns.io) which blocks known adware and tracking hosts across all mobile and desktop platforms.

Not any more. We replaced it with our own code that did exactly what we needed it to do.

Thanks!

Preview environments need some polish. We'll get there.

No. It's a sad name clash.

We can choose to be profitable now, but we're choosing to reinvest profits into building for the long term. Either way, not going anywhere!

We're working towards HIPAA compliance this year, but I don't have an ETA.

- Completely agree on more instance sizes similar out our Postgres

- More granular secret access (and, in general, more granular RBAC) are on the list for 2025

- Render is now ISO 27001 certified [1], and we help you pass SOC 2/ISO 27001 audits.

Thanks for the support team shoutout!

[1] https://render.com/blog/render-iso-27001-and-document-center

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 support@render.com.

Cheers!

Fully managed Postgres with high availability and point-in-time recovery is a big reason developers choose Render.

Thanks!

Object storage is a major missing piece. Stay tuned.