Firebase vs. IBM Cloud Foundry

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Firebase
Score 8.2 out of 10
N/A
Google offers the Firebase suite of application development tools, available free or at cost for higher degree of usages, priced flexibly accorded to features needed. The suite includes A/B testing and Crashlytics, Cloud Messaging (FCM) and in-app messaging, cloud storage and NoSQL storage (Cloud Firestore and Firestore Realtime Database), and other features supporting developers with flexible mobile application development.
$0.01
Per Verification
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
FirebaseIBM Cloud Foundry
Editions & Modules
Phone Authentication
$0.01
Per Verification
Stored Data
$0.18
Per GiB
Community Runtimes
$0.07
Per GBH
Offerings
Pricing Offerings
FirebaseIBM 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
FirebaseIBM Cloud Foundry
Considered Both Products
Firebase
Chose Firebase
I actually only have experience with Firebase. It's for a good reason. It's the first database I worked with and just stuck with it. It's beginner friendly while offering advanced tool.
Chose Firebase
Firebase provides an event based data model with well defined pre-determined dimensions. Where I've seen the strength of other platforms is the user interface where data is analyzed. However, other platforms such as AEP also have advanced data cleansing and standardization …
Chose Firebase
Supabase is more user-friendly especially since it is directly integrated with Lovable, one of the most popular AI coder for non-technical users.
Chose Firebase
Supabase seems to have the best of all worlds right now. Followed by MongoDB/Firebase for smaller projects requiring less manpower and resources. Azure and Microsoft are reserved for existing projects and larger corporate clients.
Chose Firebase
Although there are other backend platforms that could have provided us with a solution to our project. The way of grouping the solution in FIREBASE, atomizing in the same project the database, cloud functions, authentication, push notifications, etc., has given us a clearer …
Chose Firebase
Unlike other tools in the GCP suite that have an equivalent in other clouds such as Bigquery (Athenas on AWS), AI Platform (Sagemaker), Storage (S3), we do not find an equivalent as complete as Firebase in any other provider. This is the main reason why we chose this provider …
Chose Firebase
Firebase came to a multiuse case for our product for authenticating backend services, users on the app & get data on the user base using the dashboard.
Chose Firebase
Firebase has a single NoSQL database, it is a simple, powerful and uniform application development platform in connectors, it has multiple programming languages ​​such as JavaScript and necessary tools that will simplify the creation of applications.
Chose Firebase
Firebase poses great documentation and integration with Android devices. And it's very good as well for iOS ones. So, for these scenarios, Firebase becomes the ideal ally.
Chose Firebase
It eases the app development process, has an extensive database that allows you to store media files in the cloud, supports robust uploads and downloads, and login authentication on any platform.
Chose Firebase
PostgreSQL is a relational database and is well suited for complex applications, however, Firebase is well suited for light and faster applications.
Chose Firebase
Firebase is easy to manage and scale really well for web application services. It offers better authentication and is easy to implement. For real-time analytics on web applications, it works very well. Firebase offers more features compared to other services especially it can …
Chose Firebase
  • User interface and console are very easy to understand
  • There is no pain in Integration with IOS, Android, and unity platforms
  • Cost-effective
Chose Firebase
We choose Firebase for various reasons:
  • A large set of resources and world-class Google support.
  • Pricing was a larger role in this decision.
Chose Firebase
If I get a suitable budget next year, I'll be switching us to Adobe Analytics. Their app/web tracking and the interface are streets ahead of Firebase.
Chose Firebase
Firebase is a much more comprehensive tool. While Fabric only had user traffic and trends data, it did not have the user communication set of tools. While CleverTap has CRM tools, it does not have tools for developers and product teams. While Adobe Analytics is good with …
Chose Firebase
I haven't played much with Heroku beyond deploying projects from Github. It looks to be very similar in providing a cloud-based platform for developing and deploying web apps as quickly as possible. I would look at comparing both of these before choosing a solution. I am just …
Chose Firebase
We chose Firebase for the following reasons.
  • Online resources.
  • Comes with better support.
Chose Firebase
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted …
Chose Firebase
Firebase does a lot of things well, but Branch.io does a lot of things great. We originally chose Firebase because it was free, had great crash reporting, and full event tracking. As we began to scale, increase paid marketing spend, and implement features such as journey …
Chose Firebase
It's tough to pick out competitors against Firebase as I'm really unsure and doubt there's another product exactly like it. As mentioned before Firebase literally does everything you can imagine for a mobile application but doesn't get insanely deep in one feature or action. It …
Chose Firebase
Firebase is well suited for projects with simpler database workloads that require its real-time features. For data that is heavily read in real time, it's a great choice and gives developers a lot of features that would have been complicated and time-consuming to build up front …
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
FirebaseIBM Cloud Foundry
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Firebase
-
Ratings
IBM Cloud Foundry
7.6
Ratings
2% below category average
Ease of building user interfaces00 Ratings7.00 Ratings
Scalability00 Ratings8.50 Ratings
Platform management overhead00 Ratings8.50 Ratings
Workflow engine capability00 Ratings8.00 Ratings
Platform access control00 Ratings10.00 Ratings
Services-enabled integration00 Ratings7.50 Ratings
Development environment creation00 Ratings7.70 Ratings
Development environment replication00 Ratings6.40 Ratings
Issue monitoring and notification00 Ratings4.70 Ratings
Issue recovery00 Ratings7.50 Ratings
Upgrades and platform fixes00 Ratings7.50 Ratings
Best Alternatives
FirebaseIBM 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
FirebaseIBM Cloud Foundry
Likelihood to Recommend
7.3
(0 ratings)
8.5
(0 ratings)
Likelihood to Renew
-
(0 ratings)
7.0
(0 ratings)
Usability
7.0
(0 ratings)
-
(0 ratings)
Support Rating
7.3
(0 ratings)
-
(0 ratings)
User Testimonials
FirebaseIBM Cloud Foundry
Likelihood to Recommend
Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.
Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.
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
  • Extremely robust. Has about any tool you can think of under one roof making it extremely useful as a backup platform for data analytics or small teams that need something quickly.
  • Intuitive and easy UI/UX. Being made and owned by Google, you expect nothing less. Very easy to use for anyone that has any marketing or analytical experience especially in Google Analytics (which I just assume all marketers do).
  • Safe, secure, and sturdy. Never need to worry about downtimes or misinformation as it's as clean and safe as it is being run by Google.
  • FREE! What else is there to say. Unless you're an extremely large application handling hundreds of thousands to millions of users, this pay as you go plan will stay free.
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
  • Firebase/Firestore has very limited support for querying more complicated items; for example, performing a simple string search is not possible.
  • While upfront costs are low, costs can grow quickly if you're not careful about what you are being billed for.
  • Dashboards have at times shown different information to what is billed, and support from Google is less than stellar and not as effective as that from Amazon or Microsoft.
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
Usability
I don't use the Firebase UI much, but rather connect it to GA4. GA4 has a great event model but the GA4 UI and analysis capabilities are limited. It's harder to measure product usage type of engagement but if you have the time and resources to leverage the GA4 to BiqQuery export you'll have all the raw event data you'll need for deep analysis, segmentation, and audience activation.
Read full review
No answers on this topic
Support Rating
Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.
Read full review
No answers on this topic
Alternatives Considered
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.
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
  • Firebase has been able to help us understand reliably, the drop-off in our user flows with their funnel feature. This has made it easy for us to be able to pinpoint weaknesses in our funnel and test and optimize with data as the dependent variable.
  • From an economic standpoint, we don't pay for Firebase which is great, but as the saying goes "You get what you pay for" also holds true in this context. As we looked to grow and scale, we looked for a paid solution.
  • From a developer resource standpoint, Firebase has been extremely easy to integrate into our app. Whether it be the event tracking, dynamic links or crash reporting we have not had to waste too much developer time thanks to their well-organized developer docs.
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