About PushFlo
The missing piece of serverless, built by developers who got tired of it being missing.
The itch
We love serverless hosting. Genuinely. Push to a branch, get a preview URL, pay almost nothing until you have real traffic — Vercel, Netlify, and Cloudflare made shipping web apps feel effortless in a way that still hasn't worn off.
But serverless has a hard edge, and everyone building on it eventually walks into the same one: real-time communication. A serverless function answers a request and disappears. It cannot hold a WebSocket open, which means no live notifications, no dashboards that update themselves, no chat, no multiplayer — not without help.
The existing help felt like buying a container ship to cross a river: enterprise-priced plans, quota matrices you need a spreadsheet to compare, SDKs with more concepts than most apps have features. We were developers with a simple need and nothing simple to meet it.
So we built the piece we were missing
PushFlo was born from that itch — a passion project by dedicated developers who wanted to make life easier for fellow developers, not to build another platform you have to study. It holds the WebSocket connections on Cloudflare's edge so your serverless functions don't have to; you publish a message with one HTTP call, and your users see it instantly.
Being not overwhelming is a design goal we defend as seriously as uptime. One SDK. Channels you name with plain strings. A quickstart that fits on one screen. Four pricing tiers you can compare without a spreadsheet. If a feature would make the simple path harder to see, it doesn't ship.
What we promise
- Support from someone who built the platform. Email support@pushflo.dev and a developer who works on PushFlo answers — not a ticket bot, not a tier-one script. If you're kicking off an integration and something isn't clicking, that's exactly the email to send.
- Pricing you can predict. Flat monthly tiers, and monthly message quotas are soft — exceeding one gets you a notification, never a mid-launch outage. The whole grid fits on one screen.
- Honesty about limits. Our docs state exactly what PushFlo does and doesn't do — including where a competitor is the better fit today. We'd rather you pick us informed than disappointed.
How it runs
PushFlo is an independent, self-funded project. The infrastructure runs on Cloudflare's global edge network across 300+ cities, availability is public on the status page, and the SDK is open on GitHub. Because we run on usage-efficient edge infrastructure instead of fleets of idle servers, the free tier can be genuinely useful and the paid tiers stay affordable — that isn't a promotion, it's the cost structure.
Who's behind it
PushFlo is built and run by Marek, an indie developer who hit the serverless real-time wall one too many times and decided to fix it properly. Every feature ships because a real app needed it; PushFlo runs PushFlo's own real-time dashboards, so the first user to notice a rough edge is usually us.
Being small is part of the product: no growth team writing quota matrices, no sales funnel between you and an answer, and every customer matters — because there's no tier of customer that doesn't.
See if it fits your app
The free tier is a real tier — 500K messages a month, 100 connections, no credit card. Ten minutes from signup to your first live message.