I'm definitely getting worried about that. Our CTO has always said we'd move off Heroku when we got big enough, which makes sense, but now I'm afraid we're goi

I'm definitely getting worried about that. Our CTO has always said we'd move off Heroku when we got big enough, which makes sense, but now I'm afraid we're going to be doing it in a hurry when Heroku stops caring about some aspect of their service we depend on. We're already sort of seeing that in a niche case - it used to be that credentials to access Heroku's PG databases were created with readonly permissions by default. That has been broken for some time, forcing you to connect to the PG instance and run the necessary SQL commands to provide access. Not a big deal but just another indication to me that the lights are on but no one is home.