Get an audit

Head to head · Notify push · October 2026 research run

Amazon SNS vs Firebase Cloud Messaging

Amazon SNS scores 72.8 (BB) on agent readiness against Firebase Cloud Messaging's 69.8 (B), and leads in 3 of 7 scored categories. Firebase Cloud Messaging leads on agent ergonomics, payments & pricing and maintenance & community. Both do notify push.

Amazon SNSAmazon Web Services · HTTP API BB72.8/100#96 of 841 Firebase Cloud MessagingGoogle · HTTP API B69.8/100#162 of 841

Which one, for what

Amazon SNS BB

Good for Teams already on AWS that want cheap push, SMS and plain-text email alerts or fan-out to queues and functions under IAM and CloudTrail.

Ahead on

  • Reliability, 75 against 66
  • Security & auth, 89 against 68

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No idempotency token on Publish to a standard topic. Only FIFO topics deduplicate, over a five-minute window

Firebase Cloud Messaging B

Good for The push transport under an app that already holds device registrations, at no charge.

Ahead on

  • Agent ergonomics, 70 against 65
  • Payments & pricing, 40 against 35
  • Maintenance & community, 83 against 75

Watch for

Push transport only. No in-app feed, email, SMS, user preferences, digests or templates

Score by category

CategoryWeight this runAmazon SNSFirebase Cloud MessagingEdge
Reliability16%207566Amazon SNS +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28386Firebase Cloud Messaging +3
Agent ergonomics13%16.26570Firebase Cloud Messaging +5
Security & auth14%17.58968Amazon SNS +21
Payments & pricing10%12.53540Firebase Cloud Messaging +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87583Firebase Cloud Messaging +8
Transparency & trust7%8.88381Amazon SNS +2
Negative events≤1500
Total72.8 · BB69.8 · B

Facts side by side

FactAmazon SNSFirebase Cloud Messaging
KindHTTP APIHTTP API
VendorAmazon Web ServicesGoogle
Hosted endpointhttps://sns.us-east-1.amazonaws.comhttps://fcm.googleapis.com
TransportsHTTPHTTP
AuthOAuth or keyOAuth
PricingPay per useFree
Price for notify push$0. per messagefree
x402nono
LicenceProprietary service under the AWS Customer Agreement. The AWS SDKs and the AWS Labs MCP server are Apache-2.0Proprietary service under the Google APIs Terms of Service. The Firebase Admin SDKs are Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-062026-09-24
Terms last updated2026-08-142021-11-09
Privacy policy last updated2026-05-182026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity6.5M npm/wk11.5M npm/wk, 3.8M PyPI/wk

Verdicts

Amazon SNS

IAM and topic policies limit a credential to single actions and topics, a read-only managed policy exists, and CloudTrail can log each publish. Standard topics take no idempotency token, so a retried Publish can send twice. SNS has no user preferences, digests or in-app channel, email is plain text to confirmed subscribers, and SMS starts in a sandbox.

Firebase Cloud Messaging

Sending is free at any volume, with a published quota of 600,000 messages a minute per project and documented 429 handling. FCM is push transport only. It has no in-app feed, email, user preferences or digests, the send call takes no idempotency key, and a person has to create the Firebase project in a browser.

Before you call either

Amazon SNS

  1. Sign requests with SigV4 for service sns at sns.<region>.amazonaws.com, or call aws sns publish --topic-arn <arn> --message <text> from the AWS CLI
  2. Track MessageId yourself on standard topics, because a retried Publish sends again. Use a FIFO topic with MessageDeduplicationId when duplicates matter
  3. Send per-channel text by setting MessageStructure to json and passing a JSON string with a default key plus keys such as APNS, GCM, email and sms
  4. Check GetSMSSandboxAccountStatus and the monthly spend quota before texting. Sandbox sends reach only verified numbers
  5. Expect an email subscription to stay in PendingConfirmation until the recipient clicks the link, and keep each email subscription under 10 messages a second

Firebase Cloud Messaging

  1. Mint an access token from a service account with the scope https://www.googleapis.com/auth/firebase.messaging, then POST to https://fcm.googleapis.com/v1/projects/<project-id>/messages:send
  2. Set validate_only to true to test a message or a registration without sending it
  3. On 429 wait for the retry-after header, or 60 seconds if it is absent. Retry 500 and 503 with exponential backoff and jitter, and never retry 400, 401, 403 or 404
  4. Drop a registration when the error is UNREGISTERED (404). Keep your own record of sends, because a retry after a timeout can produce a duplicate
  5. Target fid in new code. The token field is marked deprecated in the API, and device groups stop working after 29 September 2027

Questions

Which is better for AI agents, Amazon SNS or Firebase Cloud Messaging?

Amazon SNS scores 72.8 (BB) on agent readiness against Firebase Cloud Messaging's 69.8 (B), and leads in 3 of 7 scored categories. Firebase Cloud Messaging leads on agent ergonomics, payments & pricing and maintenance & community.

Which is cheaper for notify push, Amazon SNS or Firebase Cloud Messaging?

Firebase Cloud Messaging, at free against $0. per message for Amazon SNS. These are the vendors' published prices for the job.

Do Amazon SNS and Firebase Cloud Messaging need an API key?

Amazon SNS takes an API key or an OAuth sign-in. Firebase Cloud Messaging uses an OAuth sign-in.

Can an agent call Amazon SNS and Firebase Cloud Messaging without installing anything?

Yes. Amazon SNS has a hosted endpoint at https://sns.us-east-1.amazonaws.com and Firebase Cloud Messaging at https://fcm.googleapis.com.

Other comparisons with Amazon SNS or Firebase Cloud Messaging

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report