QueueFly

About QueueFly

Simple shouldn’t mean basic.

QueueFly exists because of one repeated experience: every company that needs push notifications ends up rebuilding the same plumbing — queues, retries, token cleanup, scheduling — and every vendor either sells it as an enterprise platform or meters every message you send. I built QueueFly to be the opposite of both: something simple, with all the features, for companies and developers who just want notifications that arrive.

How QueueFly works

You keep your Firebase. QueueFly doesn’t replace FCM or lock your data into a platform. You bring your Firebase credentials; QueueFly runs the production layer around it — auto-scaling queues, retries with backoff, dead-letter queues, scheduled and timezone-aware sends, automatic token rotation, and webhooks.

Every plan gets everything. Unlimited notification sends on every plan, including the free trial. Multi-tenancy, scheduling, DLQs — no feature paywalls. You pay for registered devices, not per message, so a traffic spike never becomes an invoice surprise. Pricing in EUR, from €44/month.

Built small, on purpose. I build and maintain QueueFly myself, which means short lines of communication, changes that ship in days, and support answered by someone who actually knows the codebase. sales@queuefly.com reaches me directly.

When QueueFly is the wrong choice

I’ll save you a sales call: if you need direct APNs connections, SMS or voice channels, or marketing automation (segmentation, journeys, A/B campaigns), use a platform built for that. QueueFly is deliberately one thing, done properly — transactional-grade push notification infrastructure on top of FCM.

Who I am

Alexandre Paula

Founder & sole developer of QueueFly · Tech Lead at SoftFinança, S.A. · Lisbon, Portugal

I’ve spent 15+ years designing and building software — mostly .NET backends with React and Angular frontends — in Portugal’s payments and banking world: Universo, Payshop, Fidelidade. In that world, “the message didn’t arrive” is an incident, not a metric. QueueFly is built with that bias: nothing is silently dropped. Sends return a journal id you can check for per-device delivery status any time, invalid tokens come back through webhooks, and messages that keep failing are parked in a dead-letter queue. And because a failed record doesn’t need its payload to be useful: once a message is processed, sent or failed, its body and subject are nulled. The receipt survives; the content doesn’t. Privacy first — even from myself.

It started from wiring Firebase push plumbing project after project — and deciding to wire it once, properly.

Try it with your own Firebase project

30 days, all features, unlimited sends, no card.

Start free