Tiny SDK · No build step

Browser notifications, one drop-in script.

$9/mo for 10,000 subscribers. No FCM account, no SDK to learn, no enterprise sales call — a dashboard, broadcast queue, and PWA support, all behind a single <script> tag.

Get started free See pricing

No credit card required · Free tier never expires

Three steps. Five minutes.

From signup to your first delivered notification. No SDK to learn, no configuration files, no enterprise sales call.

Drop in the SDK

One script tag on the page where you want notifications.

<script
  src="https://litepush.dev/sdk.js"
  data-project="prj_xxxx"
  data-vapid-key="xxxx"
  async
></script>

Ask for permission

Trigger when the user is in the mood — not on page load.

await litepush.subscribe({
  userId: 'user_42',  // your own user ID, optional
});

Send from your server

REST API. Bearer auth. JSON in, broadcast ID out.

await fetch('https://api.litepush.dev/v1/send', {
  method: 'POST',
  headers: { Authorization: 'Bearer lpk_live_xxxx' },
  body: JSON.stringify({
    target: { type: 'user', external_id: 'user_42' },
    notification: { title: 'Hi!', body: 'It worked.' }
  }),
});

Built to be cheaper, not bigger.

Identical workload across services. We compete on price + simplicity.

	LitePush	OneSignal	Pusher Beams	web-push (DIY)
10k subs / 200k pushes / mo	$9	$59	$29	$0 + your infra
100k subs / 2M pushes / mo	$30	$419	$199	$0 + your infra
500k subs / 10M pushes / mo	$79	$2,019	$399+	$0 + your infra
Time to first push	< 5 min	30+ min	10–15 min	hours
Per-subscriber metering	✗	$0.004/sub	✗	✗
Standard PushSubscription	✓	✗	✗	✓

Web-push-only workload — competitor prices are each provider's cheapest plan that supports browser push at the stated volume. Prices verified June 2026.

Pricing

Pay for what you use. Upgrade or cancel any time, directly from your dashboard.

Free

$0/ mo

No card required

2,000 subscribers
40,000 pushes / mo
1 project
3 subscriber groups
Custom notification icon
"Powered by LitePush" on every notification

Start free

Hobby

$9/ mo

or $90/yr · 2 months free

10,000 subscribers
200,000 pushes / mo
3 projects
9 subscriber groups
No branding
Banner images
Analytics — 30-day history

Start with Hobby

Plus

$16/ mo

or $160/yr · 2 months free

25,000 subscribers
500,000 pushes / mo
5 projects
27 subscriber groups
No branding
Banner images
Scheduled broadcasts
Webhook delivery confirmations
Analytics — 30-day history

Start with Plus

Pro

Max

$79/ mo

or $790/yr · 2 months free

500,000 subscribers
10,000,000 pushes / mo
Unlimited projects
1,000 subscriber groups
No branding
Banner images
Scheduled broadcasts
Webhook delivery confirmations
Analytics — 1-year history + CSV export

Start with Max

Frequently asked

You can — and for a single project, you probably should. LitePush is what you reach for once the boilerplate adds up: a subscriber store with dedup, a broadcast queue that fans out to hundreds of thousands of subscribers with retries and delivery tracking, click/dismiss analytics, webhook events, GDPR erasure + export endpoints, VAPID key management, and a dashboard to send from. If you'd rather not build and host all of that, $9/mo is cheaper than the afternoon you'd spend on the fan-out queue alone.

No. Web Push uses the VAPID protocol — any server can push to any browser using only public-key crypto. FCM, Apple Push, and Mozilla autopush are all free public infrastructure. You only need an Apple Developer account ($99/yr) for NATIVE iOS apps, not for web push.

Yes, since iOS 16.4 (March 2023) — but only when the user has added your site to their Home Screen as a PWA. iOS does not deliver web push from a regular Safari tab. The SDK's canSubscribe() detects this case and returns false, so you can show an 'Add to Home Screen' hint instead of a broken subscribe button (the docs have a copy-paste snippet). Everywhere else just works: Chrome and Edge (desktop + Android), Firefox, and macOS Safari 16+ in any tab.

Add one script tag, host one service-worker file on your origin, and call litepush.subscribe(). Genuinely under 5 minutes for a first push. We've timed it.

The browser SDK and service worker are a tiny, unobfuscated script you can read end-to-end in DevTools — and you're welcome to vendor them into your repo. The backend, though, is a managed service: there's no self-host option today. If self-hosting is a hard requirement, the web-push npm library on your own infrastructure is the path (see the first question above).

Yes — export your entire subscriber list with group memberships as CSV any time, from the dashboard or GET /v1/subscribers/export. One honest caveat: Web Push subscriptions are cryptographically tied to the VAPID key they were created under, so they can't be handed to a different provider's keys — your users would re-opt-in on the new service. That's a property of the Web Push standard itself, not a LitePush lock-in; the same re-opt-in is required moving between any two push providers.

The relevant call returns a friendly 403 — new subscribes get blocked once you're at your subscriber cap, and broadcasts that would push you over the monthly delivery cap get rejected before they fan out. Existing subscribers keep receiving anything still within budget. No surprise charges, no silent rate-limiting; upgrade or wait for the monthly counter to reset on the 1st (UTC).

Yes — directly from the dashboard via the Stripe Customer Portal. You keep access through the end of your billing period. No retention dark patterns, no support contact required.

No — fees are non-refundable. Because you can cancel at any time and keep paid-tier access through the end of the billing period you've already paid for, a refund would just shorten that window. If we ever terminate your account for reasons outside your control, that's the one exception (see the Terms of Service). For data-protection-driven termination triggered by a sub-processor change, the DPA also covers a pro-rated refund.

Ship Web Push this weekend.

Free tier. No credit card. Five-minute setup. Cancel any time.

Get started free Sign in