QueueFly
Firebase-powered · Enterprise-grade reliability

Notification infrastructure that scales with you

QueueFly wraps Firebase Cloud Messaging with enterprise-grade reliability, auto-scaling, and smart token management. Ship push notifications in minutes, not weeks.

Why QueueFly?

Everything you need to deliver at scale

Built for engineers who demand reliability and simplicity.

Delivery Infrastructure

Battle-tested pipeline built on Firebase, optimised for throughput and minimal latency across all device types.

Reliability Layer

Automatic retries with exponential backoff recover transient failures, and dead-letter parking catches persistently failed sends — so a failure is never silent.

Token Management

Auto-refresh FCM tokens, deduplication, and cleanup. Never worry about stale or invalid device tokens again.

Auto-Scaling

Send unlimited notifications on every plan. The queue absorbs every traffic spike effortlessly, with zero configuration needed.

Scheduled Notifications

Schedule pushes in advance to the exact UTC instant you provide — per device, per user, or per topic, cancellable until they fire.

By User or Topic Notifications

Send notifications across all user devices or to all customers by a topic.

How It Works

Live in 3 steps

1

Sign Up

Sign up at queuefly.com
2

Configure

Create a tenant from the dashboard
Copy your ClientId, TenantId & ApiKey
3

Deliver

Send by user ID, device token, or topic. Schedule for later.

Send notifications

Use Cases

Built for every notification workflow

Transactional Alerts

Real-time order updates, payment confirmations, and shipping notifications.

  • Send by device token or user ID
  • Automatic retry on FCM failures
curl
curl -X POST https://api.queuefly.com/api/v1/push/by-user \
-H "Content-Type: application/json" \
-H "ClientId: $QUEUEFLY_CLIENT_ID" \
-H "TenantId: $QUEUEFLY_TENANT_ID" \
-H "ApiKey: $QUEUEFLY_API_KEY" \
-d '{
"externalUserId": "user-789",
"subject": "Your order has shipped! 📦",
"body": "Order #1234 · arrives tomorrow by 9 PM",
"jsonData": { "orderId": "1234", "screen": "order-detail" }
}'

Trust & Compliance

Privacy & data sovereignty, by design

Built for European enterprises who can't compromise on where their data lives or who can see it.

  • EU-hosted infrastructure

    Your data runs on Railway's EU West (Netherlands) region — not shipped across borders by default.

  • Encrypted everywhere

    TLS in transit and encryption at rest, with access restricted to authorised personnel only.

  • Zero cookies, zero tracking

    No cookies, no analytics, no ad pixels on this website — ever.

  • GDPR & CCPA/CPRA ready

    Full data subject rights built in: access, rectify, erase, restrict, and port your data on request.

  • We never sell your data

    No data brokers, no ad networks, no exceptions — your data funds nothing but your own notifications.

  • Zero message retention

    Notification payloads are purged from our systems the moment delivery is confirmed — we never retain or can reconstruct what was sent.

Built for European enterprises who can't compromise on where their data lives or who can see it.

EU Hosted
GDPR Ready
Encrypted
No Tracking

Roadmap

Built in the open, always improving

Privacy and reliability aren't a one-time checkbox — here's what we've already shipped and what's coming next.

Zero-retention notification payloads

Shipped

Notification payloads are now cleared from our systems the moment they are processed — we no longer retain a record of what was sent.

Firebase Installation ID (FID) support

Planned

Adopting Firebase's new Installation ID (FID) from the Firebase Installations Service for device identification.

Privacy-first statistics workers

Planned

Dedicated internal workers will compute delivery statistics independently of notification content, so records can be fully deleted — no stored trace of what was sent or exactly when.

MCP server for AI agents

Planned

An official Model Context Protocol (MCP) server so AI coding agents and assistants can send, schedule, and manage notifications directly through natural-language tool calls.

Redesign client area

Planned

A refreshed client area and usage analytics.

Pricing

Simple, transparent pricing

Start free. Scale as you grow. No surprises.

Developer Docs

Markdown

Quick Start

Get up and running in under 5 minutes — start sending push notifications immediately. No prior token registration required.

Base URL: https://api.queuefly.comREST / JSON3 auth headers required

Prefer Postman?

Import the collection and environment below to try every endpoint in this doc without writing any code. Just fill in your ClientId, TenantId, and ApiKey in the environment.

Step 1 — Send your first push notification

You only need a device FCM token — no prior user registration required.

bash
curl -X POST https://api.queuefly.com/api/v1/push \
-H "Content-Type: application/json" \
-H "ClientId: <your-client-id>" \
-H "TenantId: <your-tenant-id>" \
-H "ApiKey: <your-api-key>" \
-d '{
"deviceToken": "fcm-device-token-here",
"platform": "android",
"subject": "Order shipped!",
"body": "Your order #1234 is on its way.",
"jsonData": { "orderId": "1234" },
"imageUrl": "https://cdn.example.com/img.png"
}'

Step 2 — Optionally pre-register a device token

Pre-registering a token lets you associate it with an externalUserId, enabling the /by-user endpoints to fan out to all of a user's devices automatically.

bash
curl -X PUT https://api.queuefly.com/api/v1/device-tokens \
-H "Content-Type: application/json" \
-H "ClientId: <your-client-id>" \
-H "TenantId: <your-tenant-id>" \
-H "ApiKey: <your-api-key>" \
-d '{
"token": "fcm-device-token-here",
"platform": "android",
"externalUserId": "user-123"
}'
Zero friction. Send to any FCM device token directly — no user registration step needed. Optionally use PUT /api/v1/device-tokens to pre-register tokens and then POST /api/v1/push/by-user to fan out to all devices of a user. Retries and token rotation are handled automatically.