IBM Cloud Private is a Kubernetes-based container platform allowing users to build cloud-native applications on their own infrastructure. In addition, it offers common services for self-service deployment, monitoring, logging and security, as well as middleware, data and analytics.
N/A
Platform.sh
Score 9.7 out of 10
N/A
Platform.sh helps companies of all sizes, from SaaS entrepreneurs looking to build, run, and scale their websites and web applications.
N/A
Pricing
IBM Cloud Private
Platform.sh
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM Cloud Private
Platform.sh
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM Cloud Private
Platform.sh
Features
IBM Cloud Private
Platform.sh
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
IBM Cloud Private is an ideal platform for companies to accelerate their business growth. It helps in reducing the cost of IT and operations while delivering a great customer experience. With IBM Cloud Private, you can gain agility and security with a flexible hybrid model that fits your needs. It's highly recommended to my colleagues from me.
In our organisation we are the only team that uses Platform.sh to host any site. This was a cost effective way for us as we were using Acquia Cloud earlier for these websites. We mostly use Platform.sh for those sites which are always in development as it is simpler and faster to handle these operations in Platform.sh. Then we do a lift and shift to Acquia as we move more towards the go live and post production maintenance side.
Capacity On Demand to scale up and down environments
SaaS model allows our team to have less involvement in managing or controlling the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities.
SaaS model allows our team to worry less about upgrades, fix packs, environment support etc.
Platform.sh is not for beginners in my opinion. It has a good amount of learning curve in my opinion.
As this is a PaaS, teams habituated with cloud infrastructure may miss the server side support from their cloud teams. I believe you will have to work on server bugs more on your own.
During normal maintenance periods, integrations may fail if you are working on your sites in that time, in my experience.
With VMware cloud, each VMware Cloud customer must have an SDDC account(VMC) as well as a general AWS account. The two accounts must be linked for the service to work which is a tiresome thing to do for some clients but with IBM Cloud Private all these issues are solved.
In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. After said development is done, we generally lift and shift to Acquia for more content heavy sites and to AWS for more transaction oriented sites.