AWS IoT Core is a managed cloud service that lets connected devices interact with cloud applications and other devices. It includes the Device Gateway and the Message Broker, which connect and process messages between IoT devices and the cloud. AWS IoT Core connects AWS and Amazon services like AWS Lambda, Amazon Kinesis, Amazon S3, Amazon SageMaker, Amazon DynamoDB, Amazon CloudWatch, AWS CloudTrail, Amazon QuickSight, and Alexa Voice Service to build IoT applications that gather, process,…
$0.08
Per Million Minutes
Firebase
Score 8.4 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
Pricing
AWS IoT Core
Firebase
Editions & Modules
Connectivity
$0.08
Per Million Minutes
Rules Engine
$0.15
Per Million Actions
Messaging
$1.00
Per Million Messages
Phone Authentication
$0.01
Per Verification
Stored Data
$0.18
Per GiB
Offerings
Pricing Offerings
AWS IoT Core
Firebase
Free Trial
No
No
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
AWS IoT Core
Firebase
Considered Both Products
AWS IoT Core
Verified User
Anonymous
Chose AWS IoT Core
Azure IoT is a good product but since our whole suite of tech is now set up in AWS (ec2, s3, sagemaker, cloud formation, etc.), we wanted something that could quickly adapt to our environments. Learning a new tech for IoT was simply a bottleneck that we wanted to avoid at this …
AWS iot core is a good starting point which can be utilized for a variety of enterprise solutions. Barrier to entry to experiment and try AWS iot core is less and AWS eco-system providers ensure that even startups can try a variety of solutions and build key skills and …
Azure IoT service provides more or less the same services as compared to AWS IoT core, however the costing of AWS lead us to continued usage of IoT core over Azure IoT services. Also, considering our existing technology stack is on AWS, it was a natural selection for better …
It turns out that AWS IoT Core is the most mature solution on the market with the best variety of integration tools available. On the downside, it is not the cheapest platform existing out there. Amazon IoT Core is easy to start and set up, and our prior engagement with Amazon …
For our use case, we ended up with AWS because the human resources that were planning to be resourced on this particular project happened to have prior familiarity with the AWS ecosystem. The conversation became can we justify continuing with this ecosystem rather than pivoting …
We have checked other IoT platforms such as IBM Watson IoT and Microsoft Azure IoT, but Amazon IoT Core seems reasonable in terms of pricing and overall functionalities. Amazon IoT Core is easy to start and set up and our prior engagement with Amazon for AWS was a factor to go …
AWS IoT Core is faster, easier, cheaper, and enjoyed by our employees more than Microsoft Azure. We selected AWS IoT because we saw an advertisement for it and have used it ever since. We will continue to use it as long as it is around or until we find one that is better.
We prefer Amazon storage and content delivery S3 services rather than Microsoft Blob Storage. Also, AWS IoT Core seems to be the cheaper alternative compared to Azure IoT.
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.
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 …
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 …
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.
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.
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.
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.
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 …
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 …
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 …
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 …
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 …
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 …
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 …
AWS iot core is very useful if you need to scale very quickly for managing lots of devices without handling the underlying infrastructure cost. It can enable real time publishing and subscription of devices, monitoring and early stage intervention in case of unexpected issues while developing a full stack solution. However, healthcare scenarios where government intervention is needed should be developed and scaled by following the set of compliance policies of the government and the SLA requirements of the customer. Finally, it is great where you need to do data science research after anonymizing data
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.
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.
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.
I give AWS IoT Core's overall usability this rating because it is very easy to use and is enjoyed by all of our staff. The only problem is that it sometimes glitches and it freezes a lot. So overall, the usability of AWS IoT Core is very good, and we will continue to use it.
Firebase functions are more difficult to use, there are no concepts of triggers or cascading deletes without the use of Firebase functions. Firebase functions can run forever if not written correctly and cause billing nightmares. While this hasn't happened to us specifically it is a thing that happens more than one realizes.
It covers all the aspects of IoT services required for an IoT company. It supports all the industry-wide protocols for secure data transmission and integrates powerful AL and ML technology for data analytics. For data storage, Amazon S3 is a great solution. Strong tech support and user community. Since it is widely used as compared to other products, there is an abundance of training and learning material on the web.
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.
Azure IoT is a good product but since our whole suite of tech is now set up in AWS (ec2, s3, sagemaker, cloud formation, etc.), we wanted something that could quickly adapt to our environments. Learning a new tech for IoT was simply a bottleneck that we wanted to avoid at this point.
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.
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.