Google's free, unlimited cross-platform push notification service — part of the Firebase Backend-as-a-Service stack Google acquired on 21 October 2014 (from co-founders Andrew Lee, James Tamplin, Vikrant Tomar). Free on both the Spark (no-cost) and Blaze (pay-as-you-go) Firebase plans in 2026 with no per-message charges, no message-count limit, and no overage fees. Used by an overwhelming majority of Indian Android, iOS and web apps as the default delivery rail for transactional and engagement push.
Firebase Cloud Messaging (FCM) is the rare engagement-stack component that is genuinely a no-brainer call for Indian product teams: free, unlimited, cross-platform, operated by Google, used by an overwhelming majority of the Indian mobile app ecosystem, and increasingly the only practical way to deliver push to Android devices because of the way Google Play and the Android push topology have evolved. FCM is part of the Firebase Backend-as-a-Service platform Google acquired on 21 October 2014 from co-founders Andrew Lee, James Tamplin and Vikrant Tomar; Firebase itself was originally founded in 2011 in San Francisco. FCM (formerly Google Cloud Messaging / GCM) is the successor to GCM and the canonical push rail for Android (replacing the deprecated GCM in 2018), with Apple Push Notification service (APNs) integration for iOS and Web Push protocol support for web apps. In 2026 the pricing position is unambiguous: FCM is free on both the Spark (no-cost) and Blaze (pay-as-you-go) Firebase plans with no per-message charges, no message-count limit, and no overage fees — regardless of whether you are sending 10 pushes a day or 10 million. The right framing for Indian buyers in 2026 is: FCM is the delivery rail you should always use; the question that actually matters is which engagement platform (WebEngage, MoEngage, Clevertap, OneSignal, Braze) sits on top of FCM to handle segmentation, journeys, A/B testing and analytics. FCM by itself is excellent at sending notifications and weak at orchestrating them — there's no meaningful campaign automation, segmentation is shallow (basic topic / token / device targeting), and analytics requires the Firebase Analytics + BigQuery export pipeline which is on the Blaze plan. This is the wrong call only if you somehow need a managed engagement platform with no separate orchestration tier — almost no production team is in that bucket.
Firebase Cloud Messaging (FCM) is Google's cross-platform push notification delivery service — the actual rail that gets a push from your server to a user's Android, iOS or web browser. On Android, FCM is the only first-party push pipeline (it replaced GCM in 2018 and is the system service that the OS routes background notifications through); on iOS, FCM acts as an abstraction layer in front of Apple's APNs (Apple Push Notification service); on web, FCM speaks the W3C Web Push protocol and integrates with browsers that support it (Chrome, Firefox, Edge, Opera, and Safari via APNs-for-Web).
FCM is part of Firebase, the Backend-as-a-Service (BaaS) platform that Google acquired on 21 October 2014. The original Firebase company was founded in 2011 in San Francisco by Andrew Lee, James Tamplin (CEO), and was initially a real-time chat-API company called Envolve before pivoting to a generic real-time backend. The co-founding team (which expanded to include Vikrant Tomar among others) was retained post-acquisition and continued building out the Firebase platform under Google. Today Firebase covers Realtime Database, Cloud Firestore, Authentication, Cloud Functions, Cloud Storage, Hosting, FCM (Messaging), Crashlytics, Performance Monitoring, Remote Config, A/B Testing, App Check, Test Lab, and Analytics — with FCM being arguably the most universally adopted single Firebase product.
The 2026 pricing position is unusually clean: FCM is free on both the Spark and Blaze plans with no message-count limit and no per-message fees. The Spark plan is the no-cost tier of Firebase; the Blaze plan is pay-as-you-go for the products that do charge (Cloud Functions invocations beyond the free quota, Firestore reads / writes / storage beyond the free quota, Hosting beyond the free quota, etc.) — but FCM specifically remains free on both. This is genuinely unusual in the messaging-infrastructure category: every comparable platform (OneSignal, Twilio, MSG91) either caps the free tier at a small number of monthly active users / monthly notifications or charges per-message at scale.
The practical consequence: FCM is the universal push delivery rail in the Indian mobile ecosystem. An overwhelming majority of Indian Android, iOS and web apps either integrate FCM directly, or integrate an engagement platform (WebEngage, MoEngage, Clevertap, OneSignal, Braze) which itself sends to FCM under the hood. Even the Indian-built engagement platforms — WebEngage (Mumbai), MoEngage (Bengaluru), Clevertap (Mumbai) — all rely on FCM as the actual Android push transport. You cannot meaningfully reach Android devices without going through FCM in 2026.
Native Android (FCM SDK / FCM HTTP v1 API), iOS via APNs handoff, and web via W3C Web Push. One unified server-side API surface for Android + iOS + web; SDK handles registration, token refresh, notification rendering, and tap-handling.
Send to a specific device token, to a topic (publish-subscribe model — any device subscribed receives), or to a Boolean condition combining topics. Useful for transactional sends (token) and basic broadcast (topic); not sufficient for behavioural segmentation.
Notification messages (auto-rendered by the OS even when the app is killed) and data messages (your app code decides what to do — useful for silent payload updates, background sync, large-payload triggers). Critical distinction for Indian apps that need silent updates without OS-rendered notifications.
Web dashboard for composing and sending one-off campaigns to topics or user segments. Lightweight enough that small Indian teams can use it as their entire push interface in early stages; thin on segmentation and A/B testing for larger teams.
FCM integrates natively with Firebase Analytics (free) for basic send / open / conversion tracking, and with BigQuery export on the Blaze plan for SQL-level event analysis. The export is the cleanest way to build custom engagement dashboards.
Server-side APIs to subscribe / unsubscribe tokens to topics, batch send to thousands of tokens at once, schedule sends with the Notifications composer, and handle delivery receipts via the Reports API. Most production Indian teams build their orchestration layer on top of these.
FCM is free. There is no fine print to navigate. Specifically in 2026:
Indirect costs to plan for: (1) you usually pair FCM with the Blaze plan anyway because you want BigQuery export of Firebase Analytics events for engagement analytics — that's a Blaze-only feature, and BigQuery query costs are pay-as-you-go (typical Indian app spends ₹2,000–₹50,000/month on BigQuery export at production scale). (2) Your engagement platform on top (WebEngage / MoEngage / Clevertap / OneSignal / Braze) is the actual cost line: typical Indian B2C app spends ₹15,000 – ₹15 lakh/month on the engagement platform (priced by MAU + channels enabled), with FCM as the underlying delivery rail at no extra cost. (3) If you also send SMS / WhatsApp / email, those have their own costs (DLT-registered SMS in India is typically ₹0.15–₹0.40 per SMS; WhatsApp utility messages ~₹0.40–₹0.60 per message at India rates per the July 2025 Meta per-message pricing).
FCM is the wrong call (as a standalone solution) when: you need multi-channel engagement (push + email + SMS + WhatsApp + in-app messaging) with shared user profiles and journey orchestration — use WebEngage / MoEngage / Clevertap on top of FCM; you need sophisticated behavioural segmentation and A/B testing of push content — FCM Console is too thin; you need RFM / cohort / funnel analytics — pair with a real product-analytics tool (Mixpanel, Amplitude, Posthog, Clevertap) and use FCM only as the delivery rail; you need WhatsApp Business API delivery as the primary channel in India — that's a fundamentally different product (use Haptik / Wati / Interakt / Gupshup); or you specifically want a managed engagement platform without separate orchestration tooling.