Hello, what a pleasure to have you both reply to this topic. I’ve been part of the Django ecosystem since 2020, so I’ve seen your names around here and there.
It’s been a bit of a journey over the past couple of years. In the end, I did migrate some of my personal projects away from Heroku, while others had been dormant for a while as I evaluated the next steps.
Personal projects
I managed to get Django running on Railway.app, and their Discord community was very helpful. After a while, however, they also retired their free tier. To my knowledge, this has since been brought back, although the last I heard about it was around three or four months ago.
Then there was Fly.io. I had things running there, but while hosting my database on the platform, Fly.io experienced a hardware failure. I didn’t have a replica, unfortunately, which resulted in data loss. While this was partly my own fault, and I acknowledge that, I was fortunate that it was a personal project rather than something with users depending on it.
Some of my projects could also be moved away from Django altogether. These were typically single-page sites where I could get away without a database, for example. I moved those to Cloudflare Pages, usually using Nuxt or Hugo, depending on the requirements.
Work-wise
I work with my brother-in-law, who at the time was starting to get more involved in DevOps. We tended to stick with Heroku for work in the meantime, largely because we were familiar with it. However, we also looked at AWS, particularly CloudFormation, as we liked the idea of infrastructure as code.
With a bit of Elastic Beanstalk and RDS, we could get our Django projects running quite nicely.
With further research, we came across Terraform around three to six months ago. This was great, essentially CloudFormation on steroids. Being able to integrate with external providers such as Cloudflare was particularly useful, as it meant we could describe an entire project, from DNS through to the database, in code.
During this time, we’ve been (and are still) migrating our Django projects from Elastic Beanstalk to Fargate. This allows us to put environments to sleep when they’re not in use.
We still have a few things left running on Heroku, but certainly fewer than before as we work through the list and migrate them over to AWS.
So, to answer your question: Fargate, RDS and the wider AWS ecosystem, using Terraform.
This is how my brother-in-law and I are currently deploying Django.
We’ve also had a look at Cloudflare’s recently announced approach to deploying Django, but it’s not quite ready for our production environments just yet. I look forward to seeing how it develops.