Question 1

What is QueueFly?

Accepted Answer

QueueFly is a notification delivery infrastructure platform that wraps Firebase Cloud Messaging (FCM) with enterprise-grade reliability, auto-scaling queues, scheduled notifications, and automatic token management — letting developers ship push notifications in minutes instead of weeks.

Question 2

How much does QueueFly cost?

Accepted Answer

QueueFly offers a 30-day free trial with all features and no credit card required. Paid plans start at €44/month (Premium, up to 50k devices) and €134/month (Pro, up to 250k devices). Enterprise plans with dedicated infrastructure are available with custom pricing. Every plan — including the free trial — includes unlimited notification sends; pricing scales with device count, not message volume.

Question 3

Does QueueFly work with Firebase Cloud Messaging?

Accepted Answer

Yes. QueueFly is built on top of Firebase Cloud Messaging (FCM). You bring your own Firebase project credentials and QueueFly handles the queue, scaling, retries, token rotation, and scheduling on top of FCM.

Question 4

Does QueueFly support scheduled notifications?

Accepted Answer

Yes. QueueFly supports both one-time and cron-style scheduled notifications with full timezone-aware delivery. Scheduled pushes can be sent to a specific device token, a user ID (all their devices), or an entire topic.

Question 5

How quickly can I integrate QueueFly?

Accepted Answer

You can send your first push notification in minutes. Sign up, create a tenant, paste your Firebase credentials, and call the REST API. Device tokens are auto-registered on first push — no pre-registration needed.

Question 6

What happens if a notification fails to deliver?

Accepted Answer

QueueFly automatically retries failed deliveries with exponential backoff. Messages that keep failing are parked in a dead-letter queue (DLQ) instead of being silently dropped — sends return a journal id you can check at any time with POST /api/v1/push/sent for per-device delivery status, and invalid device tokens are pushed to your webhook. In keeping with our zero-retention design, delivery records never contain the message itself: body and subject are nulled once a message is processed.

Notes on notification infrastructure

Best Push Notification APIs for Developers in 2026 (Compared)