Cool concept. In my experience, the biggest headache/expense is data migration, and not software migration. As long as the stack is vendor neutral, it's not the long-poll, though it is gruntwork. In the SaaS world, maybe this will be useful to run managed cloud services? (That is, customer A wants a private instance in AWS and customer B wants it in Azure)
Show HN: Porter Cloud – PaaS with an eject button
21–30 of 97 posts
Re: Show HN: Porter Cloud – PaaS with an eject button
#22It's a great idea, but the pricing seems high - $30/month minimum? I'm running 3 apps on Fly.io and I'm still so low in the pricing that they're invoicing me $0. I will pay for the convenience of a PaaS - but not that much.
not sure where you saw $30/month minimum! There's no minimum spend on Porter, and you just pay for what you use as low as a 0.1 CPU and 1MB RAM. We do not have a free tier however.
Re: Show HN: Porter Cloud – PaaS with an eject button
#23Earlier quoted context omitted.
not sure where you saw $30/month minimum! There's no minimum spend on Porter, and you just pay for what you use as low as a 0.1 CPU and 1MB RAM. We do not have a free tier however.
Pricing page (developers). How can you have less than 1 CPU?
Re: Show HN: Porter Cloud – PaaS with an eject button
#24Sounds like an interesting tradeoff. I noticed that the link to GitHub in the footer 404s however. I was hoping this was OSS.
https://github.com/porter-dev/porter-archive
They've probably forked the cloud product, and are leaving the old OSS version up?
Re: Show HN: Porter Cloud – PaaS with an eject button
#25Huge fans of Porter, we've been using them for a number of years at Woflow and they've helped us scale effortlessly.
Re: Show HN: Porter Cloud – PaaS with an eject button
#26Re: Show HN: Porter Cloud – PaaS with an eject button
#27Re: Show HN: Porter Cloud – PaaS with an eject button
#28Re: Show HN: Porter Cloud – PaaS with an eject button
#29Cool concept. In my experience, the biggest headache/expense is data migration, and not software migration. As long as the stack is vendor neutral, it's not the long-poll, though it is gruntwork. In the SaaS world, maybe this will be useful to run managed cloud services? (That is, customer A wants a private instance in AWS and customer B wants it in Azure)