71–80 of 97 posts
I don't understand the developer's pricing (new offering) which is as below: $10 per month GB RAM $20 per month vCPU As compared to standard pricing which is: $6 per month GB RAM $13 per month vCPU Isn't the developer pricing for small project expected to be less than standard? If its costly than standard pricing then what is the benefit of developers pricing?
I have never quite understood this value proposition (maybe I am not the target audience?) The point of PaaS is to avoid DevOps... making a PasS with an eject just feels orthogonal to the value prop of the main business. Ejecting seems like a low probability event as they CHOSE PaaS in the first place. (unless the money got really high) We included Porter in our post-Heroku research and chose Render. We have loved Re…
> maybe I am not the target audience There’s a point in which the hosted PaaS is too expensive. And what will you do when there are millions to be saved?
I think your natural competition here is: 1. Things like Digital Ocean that make it easy and can scale up 2. The PaaS offerings of the major clouds for example Microft Azure Appspaces. I think your advantage might be that you could eject into something more enterprise ready perhaps with Terraform/k8s etc. You could also sell consulting time to help the ejector transition to cloud. Because rearchitecting is part of th…
Earlier quoted context omitted.
They charge for managing the kubernetes instance that’s running on your infrastructure. What’s cool is that you can stop using Porter once everything on AWS/Azure/GCP is set-up and you’re not locked in. You just have to manage the cluster yourself.
I meant: what's the business model for Eject specifically? Why make it easy for customers to leave (aside from pre-empting buying-decision concerns)
I personally don't get it. You can start on GCP today, without being tied to GCP much at all. It isn't even expensive to do so. Is there something I'm missing here? 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…
Your statement on the ease of migration really depends on your skill set. An increasing number of software engineers do not have to deal with real infrastructure whatsoever. Most of the "big" companies I've been at have pretty ready made platform abstractions for their engineers.
I would put the following services in that category:
- Porter - Cloud66 https://www.cloud66.com - Hatchbox https://hatchbox.io
They all manage infrastructure on your behalf within a larger Cloud Service Provider.
Terms I could think of are "DevOps as a Service" or "Platform Engineering as a Service".
How would you call this?
And what alternatives do you see?
I don't understand the developer's pricing (new offering) which is as below: $10 per month GB RAM $20 per month vCPU As compared to standard pricing which is: $6 per month GB RAM $13 per month vCPU Isn't the developer pricing for small project expected to be less than standard? If its costly than standard pricing then what is the benefit of developers pricing?
The standard pricing doesn't include underlying cloud provider cost. The pricing page can be more clear.
Earlier quoted context omitted.
Cloud providers (particularly the hyperscalers) are ultimately bundles of multiple services. Given that the hyperscalers do almost everything, you could extend this point in a variety of ways: why do companies already on AWS bother to use MongoDB, Snowflake, or even GitHub when DynamoDB, Redshift, and CodeCommit exist? The answer tends to boil down to a combination of developer experience, performance, and pricing. F…
Totally; the ability to migrate seamlessly between cloud providers is compelling to many
We migrated microservices from Heroku to Porter, and also from standalone VMs and K8s running on AWS to Porter. As a coder trying to do both dev and devops on a tiny team, it was life changing for me. The key benefits for a small startup team are: 1. Effortless CI/CD: Deploying services on K8s clusters across different clouds becomes trivial. Setup a dockerfile in your repo, point Porter at it, deploy. We mostly run…
How long until they’re victims of their own success and can’t give every customer bespoke support…