DEV3 Technologies home

DEV3 Nudgeflare – Web Push Notifications with Segments, A/B Tests & RSS-to-Push (Next.js) with Gemini AI Admin Tools

Web push notification SaaS on Next.js 16 and MongoDB: per-site VAPID keys, opt-in prompts, segments, A/B and local-time sends, RSS-to-push, REST API, Gemini AI admin tools and a language switcher. Setup wizard and demo data included. No mobile apps.
by DEV3 TechnologiesVerified Author(0) 0 sales 3 viewsUpdated 15 Nov 2026

Video tour. Pick a section below to browse 38 screenshots in 8 sections.

App & phone tours

Tap play to watch each app. Nothing downloads until you do.

  • Mobile web0:18

Nudgeflare is a web push notification platform built by DEV3 Technologies on Next.js 16, React 19, TypeScript, Tailwind 4 and MongoDB. You host it on your own server, add your sites and send browser push notifications to your own subscribers, with no per-message fees from a third-party push service. It runs as a multi-tenant SaaS: each customer is an organisation with its own sites, subscribers, plans and API keys. The demo data is fictional: a regional news site, an outdoor shop, an online-course business and a few smaller organisations.

No live demo: about 40 grouped screenshots and two video tours show the marketing site, the workspace, the campaign tools, automations, analytics, the developer pages and the operator console. Install it with the demo data to try every role on your own server. This product is a web application: there are no mobile apps.

Sites, prompts and subscribers

  • Per-site VAPID keys generated on your server. The private key is encrypted at rest and never shown again.
  • JavaScript snippet and service worker: one script tag and one small hosted file. The service worker uses its own narrow scope, so it never replaces a customer's own root service worker.
  • Opt-in prompt designer: bell, slide-in or native prompt, delay and scroll rules, pages to skip, and live desktop and Android previews.
  • Subscribers with browser, system, country, timezone, tags and attributes. Push endpoints and keys are never displayed, only a masked hash.

Campaigns, segments and automations

  • Segments from allow-listed rules with a live audience estimate.
  • Campaigns with title, body, icon, image, buttons and UTM tags, scheduling, per-timezone local-time sends, throttling, expiry and A/B tests with an automatic winner.
  • Automations: welcome series, RSS-to-push (each item is pushed once) and API-triggered notifications from your own backend.
  • Analytics: delivered, clicked and unsubscribed counts, timezone waves, a campaign comparison and a "Flare Ladder" chart of recent campaigns.
  • Click links are signed and frozen when the push is queued, so a link cannot be changed afterwards.

Plans, billing and the developer tools

  • Plans by sites, subscribers and sends, with trials, a plan-change preview, invoices, usage meters and caps. The payment gateway is simulated in the demo.
  • REST API with scoped Bearer keys, an OpenAPI 3.1 document and a try-it page. Signed webhooks with a delivery log and retries.
  • Operator console: organisations, plans, platform throughput, worker lag, push-service response codes, an allow-list of push hosts, impersonation that is audited, and platform settings.
  • Worker process (npm run worker) for fan-out, schedules, RSS polling and automations. Private files, audit log, notifications, English and other languages in the UI, dark mode and a setup wizard.

Gemini AI admin tools and Translate

  • AI panels on the main pages: title and body variants for A/B tests, tone check, opt-in copy rewrite, plain-English segment filters, results explanations, anomaly flags, install steps for your platform, usage advice, support-reply drafts and a spam-risk flag for operators. Suggestions are previews: nothing is sent, scheduled or saved until you accept it.
  • What Gemini sees: only campaign and prompt copy and aggregate numbers are sent to Gemini. Push endpoints, keys, VAPID keys, API keys, webhook secrets and individual subscriber data are never sent.
  • Bring your own key: the product ships with GEMINI_API_KEY blank. You add your own key after purchase and Google bills it.
  • Google Translate switcher in the public header and the workspace, with seven languages. Subscriber tables, keys, endpoints, install snippets and customer notification copy are marked so they are not translated.

Safe by design

  • Every query is scoped to the organisation by a plugin that fails closed. Fan-out sends each notification exactly once, and the monthly quota stops a send at the boundary. Race tests run against a real MongoDB.
  • Subscribe requests are checked against the registered site origin, endpoints are checked against an allow-list of push services, and outbound requests use DNS-pinned connections.
  • 750 app tests and 59 core tests pass. The first-load JavaScript on the login page is about 188 KB gzipped and the SDK is about 2.4 KB gzipped.

Good to know

  • Built-in sender: push delivery uses a native VAPID (RFC 8292) and RFC 8291 payload-encryption implementation on Node's own crypto. No third-party push SDK or push package is installed, and it is tested against the RFC test vectors.
  • Service worker scope: the customer-site service worker registers under its own scope (/nudgeflare-push/), so it does not take over the site's own service worker. You can also add its one-line importScripts to an existing worker.
  • Use your own click domain: click links are signed and cannot be turned into an open redirect, but all organisations on one install share the domain that serves them. Use a dedicated click domain of your own, not your main brand domain.
  • Production mail needs a real driver: by default email is written to the admin outbox. Set MAIL_DRIVER=smtp and your SMTP settings (and install nodemailer) before you go live.
  • Push is simulated in the demo: the demo shows deterministic delivery results and sends nothing to a browser. In production the real sender runs. Payment, SMS and other third-party connections run in demo mode until you configure your own provider; demo drivers refuse to run in production.
  • Gemini AI admin tools need your own Google Gemini API key (Settings > AI); no key or AI usage is included. Without a key the AI buttons stay disabled. Without a key the demo uses a simulated driver labelled as a sample.
  • A Google Translate language switcher is on the public site and admin; it needs Google's widget to load in the visitor's browser, and private areas are excluded from translation.
  • Uses the open Web Push standard with your own VAPID keys, so no third-party push service fees apply. Browser support follows each browser's Web Push support; iOS Safari needs the site added to the Home Screen.
  • No native mobile app push or in-app messages are included in v1.
  • You need Node.js 20.9+, MongoDB 6+ (a single-node replica set works) and cron or systemd timers for the scheduled jobs, plus one long-running worker process.

What you get

The application source with the core in your repository under packages/next-core, the JavaScript SDK source, a setup wizard, demo data, .env.example, scheduled-job scripts, tests, the buyer documentation, START-HERE.txt and the licence. Setup wizard and demo data included. No mobile apps.

How it's built

Architecture, stack, key decisions and the quality gates DEV3 Nudgeflare passed before release.

The engineering behind Nudgeflare: a native VAPID and RFC 8291 sender with no third-party push SDK, fan-out that sends each notification once, quota that stops at the boundary, signed click links and push endpoints checked against an allow-list, with the known limits written down.

The problem it solves

Web push looks simple until you run it for other people. A push endpoint is a URL chosen by a visitor's browser, so a server that posts to it can be pointed at an internal address. Two workers pick up the same campaign and every subscriber gets two notifications. A plan limit is checked before a send and then exceeded by the send itself. A tracking link is edited after it was sent. And the private key that proves the sender's identity must be stored by a product that many customers share, without ever being shown or returned.

Architecture and approach

Nudgeflare is a Next.js 16 application on MongoDB with a separate worker process (npm run worker) and the shared core in your repository under packages/next-core. Every organisation-owned model passes through a tenant plugin that scopes each query by organisation and throws when a filter has none.

A native sender

Each site gets its own VAPID key pair. The private key is encrypted at rest and never returned by any API. Payloads are encrypted (RFC 8291, aes128gcm) and signed (RFC 8292) with Node's own crypto, so no third-party push package is installed. The implementation is tested against the RFC test vectors.

Endpoints are untrusted

Push endpoints come from browsers. Subscribing checks the endpoint host against an allow-list of push services, and sending uses DNS-pinned connections that refuse private addresses and redirects.

Exactly once

Fan-out writes one delivery row per subscriber under a unique key and claims work with leases, so two workers or a retry cannot create a second notification. Quota is reserved before sending and a send stops exactly at the monthly limit.

Signed click links

A click link carries a signature over the delivery, its targets and its expiry. Targets are frozen when the push is queued, so editing a campaign later cannot redirect a sent link, and links expire after 30 days. They are not an open redirect; because all organisations on an install share the click domain, the docs recommend a dedicated domain of your own.

AI admin tools

The AI panels are configured from one map file. Only campaign and prompt copy and aggregate numbers are sent; endpoints, keys and individual subscriber data are removed. Suggestions are previews and never send or schedule anything. The product ships with the Gemini key blank: you add your own.

Quality gates and results

The app has 750 tests and the core 59, including race groups run against a real MongoDB for subscription caps, fan-out, quota and plan changes. The first-load JavaScript on the login page is about 188 KB gzipped, and the SDK is about 2.4 KB gzipped. Known limits are written down: browser web push only (no native mobile push or in-app messages), iOS Safari needs the site on the Home Screen, a simulated sender and payment gateway in the demo that refuse to run in production, and no built-in geo-IP.

Tech stack

Area Technologies
Application Next.js 16 App Router, React 19, Tailwind CSS 4, Worker process for fan-out and schedules
Push Native VAPID (RFC 8292), RFC 8291 payload encryption, JavaScript SDK and service worker, Allow-listed push hosts
Data and security MongoDB 6+, Fail-closed tenant plugin, Encrypted VAPID keys, DNS-pinned outbound requests, Signed click links
Quality Vitest unit and race tests, Headless smoke tests, Secret scan of the zip

Inside the build

Home: Bring visitors back with web push on your own keys, with notification cards over a lighthouse at dusk. Home — Bring visitors back with web push on your own keys, with notification cards over a lighthouse at dusk.

How web push works: Your own VAPID keys, encrypted payloads and signed clicks, in four steps. How web push works — Your own VAPID keys, encrypted payloads and signed clicks, in four steps.

Guides & articles

Practical guides and engineering write-ups for DEV3 Nudgeflare.

Web push notifications: 7 things to check before you pick a platform

Last updated
Web push notifications: 7 things to check before you pick a platform: DEV3 Nudgeflare

Web push brings visitors back without an app or an email address, but platforms differ in the parts you cannot see. Here are seven things to check, with DEV3 Nudgeflare as the worked example.

The overview with subscribers, sends against the quota and click-through rate

1. Who holds the keys?

Web push is signed with a VAPID key pair. If the platform owns it, your subscribers belong to the platform. Nudgeflare generates one pair per site on your server, encrypts the private key and never shows it again, and it sends with its own VAPID and RFC 8291 code rather than a third-party push package.

The site install page with the script tag and the service-worker file

2. Is the opt-in prompt yours to design?

Asking at the wrong moment burns your audience. Look for delay and scroll rules, pages to skip, and a preview before you publish.

The prompt designer with desktop and Android previews

3. Can you target without exposing people?

Segments should use allow-listed rules with a live audience estimate, and the subscriber list should never show raw push endpoints or keys.

The segment builder with a live estimate

4. Does it send at the right local time?

A 9:00 send should arrive at 9:00 for each subscriber. Check for per-timezone waves, throttling, expiry and A/B tests with a winner.

A local-time campaign sending in timezone waves

Video: a tour of the Nudgeflare site, campaigns and analytics

5. Can it run on its own?

Welcome series, RSS-to-push and API-triggered sends save daily work, as long as each item is pushed once.

A welcome series automation

6. Can your developers reach it?

Look for scoped API keys, an OpenAPI document and signed webhooks.

API keys with scopes and site restrictions

7. What about AI and translation?

Nudgeflare adds Gemini AI admin tools: title variants, tone checks, plain-English segment filters and result explanations. Only copy and aggregate numbers are sent, suggestions are previews, and the product ships with the Gemini key blank, so you add your own. A Google Translate switcher is on the public site and workspace.

AI settings with the key supplied by your server environment

One last check: read the limits. Nudgeflare is browser web push only, with no native mobile push or in-app messages, and iOS Safari needs the site added to the Home Screen.

Frequently asked questions

The complete source code (version 1.0.0) as a download from your account, with the setup and usage guides shown on this page. You can modify the code to suit your product.

Questions about this product (0)

Answers from the DEV3 team and the community.

Ask a question

No questions yet.

Wondering about setup, licensing or customisation? Ask, and the DEV3 team will help.

More from this author

View all

Related in Enterprise SaaS Starters

View all