We also offer a feature called one-click SOC2 compliance that configures your AWS account to pass controls on platforms like Vanta/Drata in a single click, which many startups find useful.
We also offer a feature called one-click SOC2 compliance that configures your AWS account to pass controls on platforms like Vanta/Drata in a single click, which many startups find useful.
Cloud Functions are just a http handler with no hard dependencies on GCP.
Cloud Tasks are just a handler and the tasks just hit your Cloud Functions.
Cloud SQL is just postgres.
You connect your github with actions that CI/CD auto deploy to the above.
If you do it that way, you're pretty much dependency free and can move anywhere else if you need to.
Similarly, if you want to, you can move away even from a PaaS that is explicitly designed to lock you in to another cloud provider. And as I mentioned in the post, this is exactly what we've done for countless companies that wanted to move from a PaaS to the big 3 cloud providers.
The more important question is: what is the switching cost? Why do companies so rarely switch hosting providers and if they do, why does it take months and sometimes years for them to move?
We want the process of moving from Porter Cloud to one of the hyperscalers as arbitrary as a click of a button.
If Porter can host GPU’s, that’s a superpower render.com doesn’t have.
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)
There is definitely still some more devops overhead compared to Heroku, and I wish the product was a bit more mature. But even at ~$18k/mo on Heroku spend we’re now spending less than half with Porter. Other than myself and the other engineer who were responsible for the migration, the rest of the team really got to keep their work flows and there was little impact except for swapping some tools.
We had a messy, poorly documented web of micro services and shit too, the Porter team made the migration surprisingly easy all things considered. I’ll work with them again if I ever scale past a $10k/mo Heroku bill (post enterprise contract) with another team.
> I’ll work with them again if I ever scale past a $10k/mo Heroku bill (post enterprise contract) with another team.
We built Porter Cloud so you can just start on us from day 1 and migrate to the Porter you're used to when you're ready, without spending much effort on the migration :)
To my knowledge GCP doesn't have a git-push deployment. Cloud Run might be the closest thing if you do a Docker push, but that is just one part, then you need a database, still need CI/CD, etc.
It's close. And while I like the look of Porter, I probably wouldn't bother and would jump straight to GCP, but I do think there are usability differences.
> [1] By “big three clouds” we mean the lower-level primitives of each cloud provider. We don’t mean their higher level offerings like AWS App Runner, Google Cloud Run, or Azure App Service, since those run into the same PaaS problems described above.
Porter is explicitly designed to be a competitor to these services that is 1) more flexible 2) cloud-agnostic 3) more cost-effective. Many of our users come from Cloud Run because they need to customize networking settings (timeouts, websockets, etc.) or autoscaling behavior, not to mention the rather expensive cost (taking as an example a machine with 2 vCPU and 4GB RAM, Cloud Run is around 3~4x the cost of what equivalent compute would cost as a VM).