"We were 6 years in with Heroku using every feature they had. As our Data Science teams grew, we started to use more and more AWS features within our org. We wanted to merge both worlds together for cohesion and to best align with our engineers skillsets. We decided to go with Porter to help leverage our developers' familiarity with a PaaS and our Cloud Engineers' deep understanding of AWS.

"We recently moved off of Heroku and opted to use Porter. Our main goals when moving away from Heroku were to reduce cost, increase reliability, have good scalability... and migrate fully over in under a week. I can reliably say that we have met and exceeded all of our criteria."

We started on Heroku but soon saw our costs balloon as we added more services and environments. We migrated to AWS ECS but ended up scratching it as ECS introduced unnecessary DevOps overhead for our engineers. Porter really hit the sweet spot for us, letting us keep the Heroku experience while taking advantage of AWS’s cost and flexibility.

"We tried Render and Heroku but ran into networking limitations early on. Porter we get the same automation along with all the benefits of hosting in our own AWS."