LitePush came out of a simple frustration: we wanted to add browser push notifications to a project, and every existing option felt heavier than the job. Firebase meant wrestling with FCM configuration. OneSignal and Pusher Beams forced a proprietary SDK between us and the browser, metering us per subscriber so that our bill grew with every single visitor who opted in. But Web Push is an open browser standard (VAPID + the native PushSubscription API). There was no reason it had to be that complicated or that expensive. So we built the version we actually wanted: drop in one script tag, host one service-worker file, and call subscribe(). It takes about five minutes from signup to your first delivered notification—with no build steps and zero SDK lock-in. Around that core API, we built a streamlined dashboard equipped with a broadcast queue, subscriber groups, delivery analytics, webhooks, and full PWA/iOS support. Our pricing is flat—we offer a free tier, followed by flat monthly plans with no variable per-subscriber fees (starting at $9/mo for up to 10,000 subscribers), ensuring a bigger audience doesn't mean an unpredictable bill. The biggest shift while building this was choosing to lean into the standard instead of hiding it. Because there is no proprietary layer, you can export your raw subscribers and leave anytime. We just focus on making the simple path absolutely delightful. Would love your feedback! I'm happy to answer anything

LitePush

drop-in Web Push for developers with flat pricing

drop-in Web Push for developers with flat pricing