Firebase Cloud Messaging is free and powerful — but it is a delivery primitive, not a notification platform. Here is what you build yourself when you use FCM directly, and what Pushbrain handles for you.
FCM handles the last-mile delivery — the cryptographic hop from your server to the device. Everything else you build yourself: storing device tokens in a database, chunking sends into 500-token batches (the FCM multicast limit), pruning invalid tokens after each send, running a scheduler for recurring notifications, building a dashboard or API for non-engineering team members, and handling retries. Pushbrain provides all of that operational layer while still using your Firebase project for delivery, so delivery cost stays zero.
The FCM sendEachForMulticast API accepts at most 500 tokens per call. A broadcast to 10,000 devices requires 20 sequential or parallel FCM API calls. Implementing this correctly — handling partial failures, collecting error codes per token, retrying transient errors without duplicating successful deliveries — is non-trivial. Pushbrain chunks all sends automatically and surfaces the per-send invalid-token count in notification history.
FCM does not proactively notify you when a token goes stale. You find out only when you attempt a send and the response includes a messaging/registration-token-not-registered error for specific tokens. With direct FCM, you must write the pruning logic: parse the error codes, look up which token corresponds to which device record, and delete from your database. Pushbrain does this automatically on every send.
FCM delivery is free in both cases — Pushbrain uses your Firebase project, so delivery cost is identical. What you pay for with Pushbrain is the infrastructure you would otherwise build: token storage, a send API, a dashboard, scheduling, audience segmentation, A/B testing, and AI copy generation. The relevant comparison is Pushbrain monthly cost vs the engineering time to build and maintain those features in-house.
Yes. Because Pushbrain uses your existing Firebase project, your FCM tokens remain valid. You integrate the Pushbrain SDK (or use the HTTP API with existing tokens), and the same tokens you collected through your direct FCM integration work immediately. No user-facing re-permission prompt is required.