Disclaimer: Founder of northflank.com here so very clearly biased. But if you’re looking for an alternative, reach out. If not, all good.
Heroku pioneered what a PaaS could be, alongside Cloud Foundry and others, so I’m genuinely sad to see it go down like this.
We built Northflank because we saw enterprises wanting to deploy workloads in their own VPC with Heroku-level simplicity. Over the past 5 years, our mission has been solving the graduation problem where companies outgrow their PaaS and have to eventually migrate.
Northflank runs in your VPC (AWS/GCP/Azure/OCI) with the same git-push experience. We have customers ranging from small startups to governments and public companies who would've otherwise built their own internal developer platform. They either use Northflank as-is in their own cloud or use our API to build their IDP on top of it.
Most common use cases are preview environments and production workloads. Happy to answer questions and throw in some credits if you're evaluating alternatives.
We've been very happy with Northflank's blend of ease-of-use with configurability when you want it. (We're running BYOC AWS.) Running several workloads and it's the best preview-environment-per-PR setup I've encountered across PaaS options.
I've been incredibly happy with Northflank since moving over a few years ago after Heroku got unreliable. Felt like an upgrade from Heroku and the support and reliability have been great.
Looks like that still has downtime for a Postgres migration- you're suggesting going into maintenance mode and just doing a dump/restore. I've seen that take hours once you hit the terabyte scale, depending on hardware.
I've had pretty good luck setting up logical replication from Heroku to the new provider and having a 10-15 minute maintenance window to catch up once it's in sync. Might be worth considering.
You might also want to add a warning about Postgres versions. There's some old bugs around primary key hash functions that can cause corruption on a migration. I've seen it twice when migrating from Heroku to other vendors.
Sorry, but telling people to take a logical backup of their database, and then download it onto their local work station is insane for a production application. First, a logical backup at any decent scale will fail, and second, I don't even have enough local storage to do that -- even ignoring the compliance issues with downloading a full copy of production data onto a work station.
For a company like Northflank, I'd expect actual production-grade documentation for migrating, not instructions that are only applicable to a toy app.
Some folks want to do that, others want to import a backup directly, some want to spawn a read replica and sync their DB. Different strokes for different folks, all supported on Northflank.
Crunchy Bridge will help you migrate. They did a great job for us. We had a minute or so of downtime to let the read replica catch up and cut across. The team knows Heroku well, and some of them built it. (No affiliation, just a happy customer.)
Heroku pioneered what a PaaS could be, alongside Cloud Foundry and others, so I’m genuinely sad to see it go down like this.
We built Northflank because we saw enterprises wanting to deploy workloads in their own VPC with Heroku-level simplicity. Over the past 5 years, our mission has been solving the graduation problem where companies outgrow their PaaS and have to eventually migrate.
Northflank runs in your VPC (AWS/GCP/Azure/OCI) with the same git-push experience. We have customers ranging from small startups to governments and public companies who would've otherwise built their own internal developer platform. They either use Northflank as-is in their own cloud or use our API to build their IDP on top of it.
Most common use cases are preview environments and production workloads. Happy to answer questions and throw in some credits if you're evaluating alternatives.