Heroku Platform vs. IBM Cloud Foundry

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Heroku Platform
Score 7.6 out of 10
N/A
The Heroku Platform, now from Salesforce, is a platform-as-a-service based on a managed container system, with integrated data services and ecosystem for deploying modern apps. It takes an app-centric approach for software delivery, integrated with developer tools and workflows. It’s three main tool are: Heroku Developer Experience (DX), Heroku Operational Experience (OpEx), and Heroku Runtime. Heroku Developer Experience (DX) Developers deploy directly from tools like…
$25
per month
IBM Cloud Foundry
Score 8.3 out of 10
N/A
IBM Cloud Foundry is an IBM version of the open-source platform designed for building, testing, deploying, and scaling applications. Enterprises can run Cloud Foundry in a public isolated environment, while natively integrating with other IBM Cloud services, such as AI, Blockchain, and IoT.
$0.07
Per GBH
Pricing
Heroku PlatformIBM Cloud Foundry
Editions & Modules
Production
$25.00
per month
Advanced
$250.00
per month
Community Runtimes
$0.07
Per GBH
Offerings
Pricing Offerings
Heroku PlatformIBM Cloud Foundry
Free Trial
NoYes
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Heroku PlatformIBM Cloud Foundry
Considered Both Products
Heroku Platform
Chose Heroku Platform
Much easier to use:
AWS and GCP have many complex services and settings.
Heroku Platform is simple:
Chose Heroku Platform
Heroku was more extensive in terms of its operating and scaling from what we witnessed by looking into other options and trying to find the best operating system for a new platform.
Chose Heroku Platform
Heroku Platform is much faster to setup, easy to maintain and in terms of ROI makes more sense.
Chose Heroku Platform
Heroku Platform is cheaper to begin with compared to DigitalOcean or Amazon Fargate. The configuration user interface is also arguably easier to understand. With its user friendliness and cheaper tiers, Heroku Platform was our pick to host some of our applications that were …
Chose Heroku Platform
I believe Azure App Service is pretty similar to Heroku as you can in both deploy your backend applications.
However, the dyno concept and it's drastically simple web dashboard makes Heroku a much better and sane alternative to Azure app service. In Heroku, you get abstracted of …
Chose Heroku Platform
Kuberbetes is an easily scalable docker based option which should need minimal DevOps, however, it has a pretty high learning curve with many decisions that need to be addressed as well as monitoring, logging and security concerns.
Chose Heroku Platform
Heroku has the advantage of simplifying the development and integration with some services (which in Heroku they call addon) wherein other platforms, certainly for those who don't have much experience, it will take much more development time.
Chose Heroku Platform
Heroku, in my opinion, is the easiest platform to deploy and host web applications on. From collaboration to deployment, everything is well thought out and bulletproof. If you need advanced server functionality, like a VPC, machine-to-machine communication, etc., you will …
Chose Heroku Platform
We chose Heroku solely because we had an end goal of putting our data into Salesforce. The platform allowed us to simplify this.
Chose Heroku Platform
We also use Cloud 66 which provides some of Heroku's features, at a lower price. It still cannot compare to Heroku's ease of use and ability to easily deploy new staging environments though, so we will always use Heroku for at least some of our projects.
Chose Heroku Platform
Heroku is an all in 1 package for deploying and running your services. It provides an easy to use setup and run for 90% of cases. If you have a more complicated infrastructure, you'd definitely need to move to another hosting provider. But if as long as you can operate within …
Chose Heroku Platform
Heroku has advantages over Docker, Google App Engine and AWS products, but it depends largely on your use case. If you are already in AWS, it's probably in your best interest to stay with AWS products. However, other "Cloud Formation/Orchestration" products like Docker are …
Chose Heroku Platform
We kicked the tires on OpenShift before deciding on Heroku, and found the platform to be much less intuitive and well-documented than Heroku. It felt like we were constantly trying to implement workarounds for esoteric platform problems, and eventually the work became too …
Chose Heroku Platform
For a different project, Aptible surpassed Heroku when it came to meeting HIPAA-related requirements, though it offers much less flexibility with add-on services (for obvious reasons). Google App Engine had a much more complicated deployment model and seemed unnecessarily …
Chose Heroku Platform
Heroku is much easier to get setup in and doesn't require strong DevOps knowledge. It's also a lot harder to mess up in.
Chose Heroku Platform
To this day no other PaaS matches Heroku in ease of use and maturity. If you want to stay 100% focused on your unique product/service rather than wasting time on boilerplate hosting issues, I can highly recommend Heroku. I personally use it for all of my own websites …
Chose Heroku Platform
Heroku is the more expensive option for hosting compared to some of the cloud platforms we investigated, but it's worth it for us because of the plug-and-play nature of Heroku deployment. We can be up and running in a few minutes and know with precision how much it will cost us …
Chose Heroku Platform
Heroku has the easy facility to deploy and host applications while others have to configure a lot. The price of the services is high for others. But within Heroku pricing and easy to maintain under the same roof.
Chose Heroku Platform
Some APIs are specifically developed to be deployed to certain platforms and usually decision which platform to use is not developer's. Another question is deployment cost and pricing model; in specific cases after price comparison Heroku is often selected among other cloud …
Chose Heroku Platform
AWS Elastic Beanstalk and AWS Lambda
Chose Heroku Platform
Heroku is a really great platform to get up and running QUICKLY and efficiently. What Heroku is really great at that other services are lacking is ease of use, documentation. It is really great for beginning developers and awesome to get up and running to take care of lots of …
Chose Heroku Platform
Heroku is a much better choice for small prototyping and small to medium size sites. It is easier to use than most other services/platforms.
Chose Heroku Platform
Slicker UX. More tightly integrated with Salesforce. Process oriented DX.
Chose Heroku Platform
I feel Heroku is lightyears ahead of all other PaaS offerings. To me the competition is between PaaS and self-hosted cloud, not between Heroku and other PaaS providers.
IBM Cloud Foundry
Chose IBM Cloud Foundry
IBM Cloud Foundry is our first choice industry-standard platform as a service (PaaS) which has always provided us with quicker, simpler, and more consistent ways for the deployment of the cloud-native applications which in result saved us lots of time and money.
Chose IBM Cloud Foundry
IBM Cloud Foundry is easier and faster to get going and offers the same benefits we needed.
Chose IBM Cloud Foundry
Dynatrace Network Application Monitoring (NAM), formerly DCRUM, Azure Application Gateway and Azure App Service
Chose IBM Cloud Foundry
When I started with prototyping five months ago, I tried IBM Cloud Foundry and AWS, but finally I preferred IBM Cloud Foundry.

I selected IBM Cloud Foundry because IBM service CLI is quite simple to use in devops. It works with the recent versions of Python and it's not …
Chose IBM Cloud Foundry
Why I prefer IBM Cloud Foundry platform over AWS Elastic Beanstalk or Heroku Platform is the automation of development process and pushing of projects to cloud with clear step by step instructions - which is available on the documentation. I can say categorically, the terminal …
Chose IBM Cloud Foundry
IBM Cloud Foundry is easy to use and allows for fast and easy deployment of web apps.
Chose IBM Cloud Foundry
IBM Cloud Foundry provides many programming languages. It is a managed service and it allows us to use only the resouces without the managed overhead.
Chose IBM Cloud Foundry
Ease of use and all the capabilities we need are well built-in. Though we had to work around for p2p security and log draining which is not bad.
Chose IBM Cloud Foundry
Cloud Foundry has lot of benefits because platform as a service provided for the developers to implement applications based on the use cases. Different use cases required different buildpacks to run on. It has flexibility to code, push, and run flexibility. Provided ease of use …
Chose IBM Cloud Foundry
We have had to move our deployments to Kubernetes because we needed more reliability. We moved to Google because IBM rates and billing was so backward and expensive. Our client was also very angry at all the outages, lost revenue, production down time and inordinately expensive …
Chose IBM Cloud Foundry
IBM Cloud Foundry is among the services provided by our cloud provider. This is why we choose to go with Cloud Foundry.
Chose IBM Cloud Foundry
While we are still looking at kubernetes and other services, we will continue to use Cloud Foundry because of the advantages it provides. The support from IBM is good and take a lot of work that our developers and ops had to do away.
Chose IBM Cloud Foundry
AWS and Digital Ocean; Access to a larger pool of services; whatever your business needs, IBM provides it.
Chose IBM Cloud Foundry
It is a cloud-based solution and for all my customers that want to migrate to cloud, this is the solution that we are proposing to customers, as it provides a lot of benefits over private cloud. Scalability and resiliency are not a major challenge and it can be used with other …
Chose IBM Cloud Foundry
CF is what we initially went with to establish a development pipeline and start our cloud journey, now we are expanding this and although we are now pulling in many other tools and functions around CF, it is not being replaced. It stands out as having a key place working ‘with’ …
Chose IBM Cloud Foundry
IBM Cloud Foundry (CF) is simpler and there is a service model that fits most of our internal services. We are going to Loopback for API and Node.js and we have an easy path to go with Bluemix. It's a very easy way to start if you are moving to the cloud and mainly if you are …
Chose IBM Cloud Foundry
We chose to go with more bare metal options since Bluemix didn't really offer these at the time. It was simpler to get up and running with the bare metal service, and we felt that any problems we ran into would be a result of our own incompetence rather than problems with the …
Chose IBM Cloud Foundry
I have use EC2 and Microsoft's Azure. To me, both Azure and Bluemix were fantastic, but they each had some pros and cons. Azure had more services to offer, but their biggest flaw was in their inability to integrate and work with external platforms, APIs, Programs, etc.. Like …
Chose IBM Cloud Foundry
While IBM works well is when being used by large organizations, these other vendors work well with smaller organizations. We ended up being willing to pay more for Heroku, as they have such an easy-to-use service, and our deployments worked as expected every time.
Chose IBM Cloud Foundry
Used AWS and Azure.
AWS has more features and a far superior interface responsivesness. It's actually usable! That being said default configurations and menus in AWS are more cryptic then necessary.
Azure seems to be the gold standard for pre-configuration and ease of use. …
Chose IBM Cloud Foundry
Bluemix had a much easier route to get into the artificial intelligence side of things with Watson skills. It also seemed a lot more straightforward to use things like the Weather Channel data, sentiment analysis... etc., than the others. I'd also had a bad experience with AWS …
Chose IBM Cloud Foundry
Not even close--as noted in previous answers, we will likely use the competition before even considering IBM Bluemix.
Chose IBM Cloud Foundry
We have used Red Hat which does not do business in Australia with people like us. They were a promising service (PaaS) while we were able to use the free version but as soon as we needed access to serious mobile-first services we had to pay and their policy meant we had to …
Chose IBM Cloud Foundry
I like when the provider offers cloud deployment via standard orchestration mechanisms (like Docker, Kubernetes, DCOS) This is currently well covered by Azure. Amazon also has good flexibility (supports Kubernetes, DCOS). It's good that Bluemix added support for Docker and …
Features
Heroku PlatformIBM Cloud Foundry
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Heroku Platform
7.2
Ratings
7% below category average
IBM Cloud Foundry
7.6
Ratings
2% below category average
Ease of building user interfaces6.00 Ratings7.00 Ratings
Scalability7.00 Ratings8.50 Ratings
Platform management overhead7.00 Ratings8.50 Ratings
Workflow engine capability6.00 Ratings8.00 Ratings
Platform access control7.00 Ratings10.00 Ratings
Services-enabled integration6.00 Ratings7.50 Ratings
Development environment creation9.00 Ratings7.70 Ratings
Development environment replication9.00 Ratings6.40 Ratings
Issue monitoring and notification8.00 Ratings4.70 Ratings
Issue recovery7.00 Ratings7.50 Ratings
Upgrades and platform fixes7.00 Ratings7.50 Ratings
Best Alternatives
Heroku PlatformIBM Cloud Foundry
Small Businesses
AWS Lambda
AWS Lambda
Score 8.2 out of 10
AWS Lambda
AWS Lambda
Score 8.2 out of 10
Medium-sized Companies
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
Enterprises
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Heroku PlatformIBM Cloud Foundry
Likelihood to Recommend
7.0
(0 ratings)
8.5
(0 ratings)
Likelihood to Renew
9.5
(0 ratings)
7.0
(0 ratings)
Usability
9.2
(0 ratings)
-
(0 ratings)
Availability
8.0
(0 ratings)
-
(0 ratings)
Performance
9.0
(0 ratings)
-
(0 ratings)
Support Rating
8.7
(0 ratings)
-
(0 ratings)
Online Training
6.0
(0 ratings)
-
(0 ratings)
Implementation Rating
9.0
(0 ratings)
-
(0 ratings)
User Testimonials
Heroku PlatformIBM Cloud Foundry
Likelihood to Recommend
Heroku is very well-suited to early stage and/or rapidly changing projects. It is great for getting moving quickly or changing direction quickly. In scenarios where there is already scale or well-defined requirements, it may be preferable to set things up directly on AWS or another cloud provider to avoid the additional costs of Heroku as the middleman.
Read full review
IBM Cloud Foundry is a solid service from the IBM Cloud platform. It is easy to learn, and does not usually require you to make drastic changes to your existing applications. It is especially good for new applications that are cloud native, or micro-services, that can be easily updated and deployed. With its blue/green deployment, you can achieve 0 downtime for your customers.
Read full review
Pros
  • Amazingly clear and straightforward documentation (versus the quagmire of AWS docs).
  • Deploy your entire site in one command.
  • Setting up asynchronous job processing for long running operations (e.g. sending emails, making external API calls).
  • A wonderful portfolio of tightly-integrated add-ons in their marketplace.
Read full review
  • Intuitive user interface makes it easy for anyone to use, regardless of their professional background.
  • A lot of the services integrate well with external platforms, APIs, and programs, not just IBM services. A lot of the competitors in this space lack this ability.
  • Maybe it is just our contract in particular, but support and help is always made available.
Read full review
Cons
  • Could be less expensive, although you get what you pay for
  • Sleeping apps can be an annoyance: Heroku automatically puts your apps in sleep mode and they have to spin back up after periods of inactivity. Much of this can be solved but it requires working around the built-in functionality. I understand why they do it but it's an area that could be improved.
  • Restrictions to server access means you can't customize as much as you could if you owned the server. But again, this is also a benefit because it's about convention over configuration. So you can't configure as much, but then, you typically don't have to.
Read full review
  • Sometimes the API Connect GUIs don't cleanly disengage after attaching models or updating schema and it is hard to know what has been written successfully and which (if any) models or tables were missed. I shouldn't have to manually check through a list of 377 models to find the ones in and out of a list on either models, folder or database tables. Printing a summary even in logs which did a "diff" sort of thing between 'task-set' and 'task-completed' (referring to attaching models or updating schema as tasks here as 'tasks').
  • Provide access to Postgres Database in Sydney datacentre for Australia.
  • Clearer documentation around setting up a secure (referring to SSL and certificate setup here) server on eg, chubby1.au-sydney.mybluemix.net.
  • Allow a ramp in pricing onto the Blockchains. We will not be able to afford it until quite a few years into production, even if we launch successfully.
Read full review
Likelihood to Renew
Heroku is a critical and core part of our infrastructure that is serving our customers well. We are very satisfied with the cost of our solution. While it would be difficult to move away from Heroku, we have no plans to do so. We have had no major issues with it and it is a pleasure to use. Other products on the market might offer comparable functionality, but until we expose a need that Heroku cannot satisfy, we'll stay the course.
Read full review
No answers on this topic
Usability
Deploying apps, scaling , managing environment is very simple. Clean interface for logs, metrics and app settings. Deployment is fast. Don't need deep knowledege of devops or cloud. Buildpacks, pipelines, and review apps makes work easier. Detailed guides help solve common problems fast.


Pricing is higher at scale. Autoscaling options are limited.
Read full review
No answers on this topic
Reliability and Availability
Heroku availability correlates pretty strongly to AWS US EAST availability. We had a couple of times where there was a Heroku-specific issue but not for the last 7-8 months.
Read full review
No answers on this topic
Performance
The only issue that I ever have is that about 1 out of 20 deployments (git push) will hang and need to be cancelled and done again.
Read full review
No answers on this topic
Support Rating
I've used it for many years without facing any major problem. It's not hard at all to get used to it, it's documentation is outstanding and simple. We are close to 2020 and I don't think most of the existing companies or startups should still face old problems such as wasting time deploying code and calculate computing resources.
Read full review
No answers on this topic
Implementation Rating
Be ready to pay a bit more than expected in the beginning if you're migrating from a big server. The application is probably not ready for the change and you have to keep improving it with time.
It's also important to consider that you can't save anything to the disc as it will be lost when your application restarts, so you have to think about using something like S3.
Read full review
No answers on this topic
Alternatives Considered
Heroku has advantages over Docker, Google App Engine and AWS products, but it depends largely on your use case. If you are already in AWS, it's probably in your best interest to stay with AWS products. However, other "Cloud Formation/Orchestration" products like Docker are typically lacking the ease-of-use factor that allows you to get up and running with Heroku quickly.
Read full review
IBM Cloud Foundry is our first choice industry-standard platform as a service (PaaS) which has always provided us with quicker, simpler, and more consistent ways for the deployment of the cloud-native applications which in result saved us lots of time and money.
Read full review
Return on Investment
  • It has been critical in seamlessly operating our platform with runs all of our programs.
  • It has been impressive with its ability to scale quickly which results in the growth of our work.
  • It allows for tracking of different features which allows for quick problem solving which saves us time.
Read full review
  • This was the founding solution used to allow us to move in to and test out a cloud pipeline. This is what paved the way for a full production cloud solution to be possible.
  • Having Cloud Foundry at the base of our development and sandpit environment, segregated away from our standard on premise solution has moved away red tape and ensured an agile way forward.
Read full review
ScreenShots