Web push notification infrastructure for every site with visitors — e-commerce, news, corporate, blog, forum. Send your campaign from one panel, set up the automations, keep your subscribers on your own infrastructure. Billed in Turkish lira.
An illustrative panel view built with sample data.
Every stop is a tool that exists in the panel today. None of it is roadmap; none of it is locked to a plan.
The values at each stop are sample data.
A new post, a new product, a basket left behind, or a campaign you open by hand.
The template you set up fills in the headline and image.
A segment by tag, language, country, browser and last seen.
A notification landing in the night window is held until morning.
A second person approves anything above the threshold.
An end-to-end encrypted payload, from the queue to browsers.
Stop it with one click in the first 45 seconds; whatever is queued is cancelled.
That is why the panel has three brakes. All three sit around the send button; none of them is there to slow you down, but to keep the way back open.
In the first 45 seconds after sending, stop the campaign with one click; anything still queued is cancelled. The counter appears in the panel where the send button was and counts down every second.
Campaigns above the audience threshold you set are not sent without approval. If your team has an approver, the approval is asked of them; if the content changes, the approval is dropped and asked again.
If your click rate or subscriber loss is unusual against your own history, you are told in the panel and by email. The threshold is not fixed; it is computed from your own last thirty days.
On the visitor’s side, three things decide which notification lands when: their local time, the quiet-hours window and the topics they picked.
One campaign, three cities. It reaches each visitor at their own local time; anything landing in the night window waits for morning.
Visitor groups by tag, language, country, browser and last seen.
Two or more headlines; the winning variant goes to the rest of the audience.
The same campaign reaches every visitor at their own local time; quiet hours are defined in the project’s time zone.
Visitors pick the topics they want notifications about from a card on your site; the choice becomes a tag.
Link your own user id to the subscriber; send notifications like “your order has shipped” or “someone replied to your thread” from your server to that one person.
You do not need a separate Firebase project. Paste the script tag, upload the service worker file to your site, then run the install check from the panel.
One line of script into your site’s <head>. Copy it from the panel.
As readers and users give permission, the system turns them into subscribers automatically.
Send a campaign, then follow deliveries and clicks in the panel.
On WordPress you do not need to paste code at all: the official plugin is published in the directory. Mobile apps are covered too — the Android and iOS SDKs are on Maven Central and Swift Package Manager.
01<!-- 1) Add to your site’s <head> -->02<script03 src="https://cdn.bildirim.io/sdk.js"04 data-key="pk_canli_anahtarin"05 data-api="https://api.bildirim.io"06 defer></script>0708<!-- 2) Upload BildirimSDK-sw.js to the -->09<!-- /bildirim/ folder on your site. Without -->10<!-- it, permission cannot be requested. -->Six site types, the same tools, used differently. All of it can be set up in the panel today; hover a row to open it.
An abandoned-basket reminder, discount and stock announcements, tagging by category. Report the purchase event to the SDK and the revenue a notification brought in appears per campaign in the panel.
Send breaking news from one screen; let your RSS feed announce the new story by itself. Readers pick their topics from a card on your site, an audience above your threshold needs a second pair of eyes, and the first 45 seconds are undoable.
Announcements, events, dealer and customer updates. Give your team members roles, put critical sends behind approval; every action is written to an audit log that cannot be altered. Those are the three things a corporate site asks for most.
Announce a new post automatically from your RSS feed, send your readers a daily or weekly digest, set up a welcome series for new subscribers. Set it up once and get back to writing.
Send per-person notifications like “someone replied to your thread” from your own server in a single request: you link your own user id to the subscriber and target by that id. Tags by interest, win-back for members who go quiet.
Trigger events, alerts and reminders through the API; turn on identity verification so nobody can send notifications in someone else’s name. Get the results back into your own system with webhooks.
All six use the same infrastructure; the difference is which tool you set up and why. You pick your site type when you create a project, and the panel follows it.
Every line here describes behaviour that works today; none of it is an absolute guarantee. The detail is on the legal pages, the current state on the status page.
Features are identical on every plan: segmentation, A/B testing, automations, webhooks and mobile push are not locked to any plan. Plans differ only in active subscriber and monthly send capacity; on the free Starter plan notifications additionally carry a small badge.
| STARTER | PRO | PUBLISHER · MOST POPULAR | BUSINESS | ENTERPRISE | |
|---|---|---|---|---|---|
| MONTHLY PRICE | ₺0Free forever | ₺1,499/mo · excl. VAT | ₺4,990/mo · excl. VAT | ₺9,990/mo · excl. VAT | QuotePriced to your usage |
| ACTIVE SUBSCRIBERS | 10,000 | 50,000 | 120,000 | 250,000 | Özel |
| MONTHLY SENDS | 3,000,000 | 15,000,000 | 36,000,000 | 75,000,000 | Özel |
| FEATURES | All included | All included | All included | All included | All included |
| BADGE | “Sent with Bildirim” badge | None | None | None | None |
| SUPPORT | Docs and the help box | Priority email support | Priority email support | Priority email support, onboarding help | Priority support, onboarding help, bespoke contract and SLA |
| Start free | Choose plan | Choose plan | Choose plan | Get a quote |
120,000 active subscriber · 36,000,000 sends/month · Priority email support
Choose plan250,000 active subscriber · 75,000,000 sends/month · Priority email support, onboarding help
Choose planÖzel active subscriber · Özel sends/month · Priority support, onboarding help, bespoke contract and SLA
Get a quotePrices exclude VAT. When a limit is reached sending stops; no overage fee is charged. Plans are per project (site).
For anything you cannot find an answer to, use the help box at the bottom right or the contact form. What you write lands in the support inbox.
No. E-commerce shops, news sites, corporate sites, blogs, forums and community sites and web apps all use the same infrastructure; what differs is which tool you set up and why. E-commerce leans on the abandoned-cart reminder and post-purchase revenue tracking, news on RSS and breaking alerts, blogs on new-post announcements and digests, forums on per-user notifications. You pick your site type when you create the project; the panel shows the e-commerce surfaces (revenue card, cart automation) only for types that sell.
Safari 16.1+ works with standard Web Push. On iOS 16.4+, notifications can only be delivered to people who have added your site to their home screen; that requires a web manifest on your site, and the install screen in the panel walks you through it. When the manifest is live, the SDK also shows iOS Safari visitors a card with the “Add to Home Screen” steps.
Yes. Device records from your Android (Firebase Cloud Messaging) and iOS (APNs) apps live in the same list as your web subscribers; the same campaigns, segments, automations and click tracking work on mobile, and mobile push is not locked to any plan. Ready-made SDKs are published: Maven Central for Android (`io.bildirim:bildirim-android`), Swift Package Manager and CocoaPods for iOS. An app that already has Firebase/APNs set up can also be connected without the SDK, with a few HTTP calls — both routes use the same endpoints. Step-by-step instructions are under Docs → Mobile integration.
No. The Starter plan is free forever and we do not ask for a card. It covers up to 10,000 active subscribers and 3,000,000 sends per month; notifications carry a small "Sent with Bildirim" badge.
The application database and its backups are hosted in Türkiye. Delivering a notification to the browser goes through Google’s, Mozilla’s and Apple’s push services; payments go through a payment provider established abroad. You can request the list of sub-processors at [email protected].
The push endpoint address and encryption keys issued by the browser, the tags you add, the browser, operating system, language and country, and the time last seen. IP addresses are not stored on the subscriber record.
Once the Bildirim snippet is on your site, visitors are registered with Bildirim as they come back; you can import your subscriber list as CSV. Browser security rules mean push subscriptions created at another provider cannot be taken over directly — they transfer as people grant permission again. Migration is therefore gradual, and how long it takes depends on how often your site is visited.
Per project. You can open several projects (sites) under one account; each project has its own plan, active-subscriber count and monthly send quota. The free Starter plan is per project as well.
When the active-subscriber limit is reached no new subscribers are recorded, while sending to existing ones continues. When the monthly send limit is reached, new campaign sends stop. Neither case produces a surprise overage charge; you can upgrade from the panel. Your usage is visible live in the panel’s top bar.
Yes. You can cancel from the billing portal; your plan stays active until the end of the period and then reverts to the free Starter plan.
Yes, entirely in Turkish lira. Annual billing is 20% cheaper. Prices exclude VAT.
Send the first notification to yourself: press the button, allow permission, and two seconds later it lands in this browser. If you like it, take it to your site. No card required; free up to 10,000 subscribers.
On an unsupported browser the button says so; nothing fails silently.