Notificator

Notificator is an open-source notification ecosystem that turns events from websites and server applications into alerts people can actually act on. It gives a WordPress administrator, Strapi team, or developer a defined path from an event to a readable message and then to the right destination. The stable WordPress plugin can watch core, plugin, commerce, form, and custom hooks. Preview integrations cover Strapi and Astro, while an official Node.js SDK connects other trusted server applications. The goal is to avoid building and maintaining a separate alert delivery system for every project and team.

The basic workflow keeps the source, rule, and destination distinct. A user chooses the event worth watching, names the notification, and builds its message from the details exposed by that event. Conditions narrow when it should fire, priorities communicate importance, and throttling cuts down repetitive noise. The finished notification can remain in the local administration area or travel to connected destinations. This separation makes it easier to understand why an alert appeared, what information it contains, and where it is supposed to go.

WordPress is the most mature starting point. Its plugin scans installed plugins, surfaces hooks with plain-language descriptions, and offers built-in and third-party templates. Users can keep activity entirely inside the WordPress dashboard without creating a Notificator account or adding an API key. Configurations can also be exported and imported on another WordPress site, which is useful for agencies or maintainers who repeat the same monitoring rules across installations. The Strapi 5 extension follows a similar idea for create, update, publish, unpublish, and delete activity, but the site clearly labels that extension as a preview rather than a finished stable release.

Connected delivery expands the same rules beyond a CMS dashboard. The web dashboard and mobile app provide a shared inbox, while the mobile app adds push notifications. Account email can be enabled as another destination. For physical alerts, compatible devices receive structured messages through a user-controlled HiveMQ Cloud MQTT connection. Notificator publishes firmware for a compact ESP32-C3 Base device and a richer Touch preview for tested touchscreen hardware. These device projects are optional, so a team can begin with local alerts and add an account, phone, email, or dedicated display only when the event justifies more reach.

The Astro integration and Node.js SDK make the project relevant outside traditional content management. Astro can send alerts from Actions, API routes, webhooks, server workflows, and successful production builds. The SDK gives Node.js applications, workers, queues, and functions a supported route into the hosted API. This is best suited to developers and site operators who know which operational or business events deserve attention, such as a new order, failed form, content change, or completed backend job. It isn't a general chat app or a replacement for full observability. Its narrower job is turning selected application events into concise signals.

What sets Notificator apart is its local-first posture and the unusual link between software events and physical devices. A WordPress user doesn't have to open an account just to see useful activity in the dashboard, and remote channels are selected per notification instead of becoming an all-or-nothing requirement. The integrations, SDKs, and device firmware are developed publicly, so technical users can inspect the code, report issues, or build another path. Public documentation also gives developers a clearer route through installation, API use, and device setup. That openness is valuable, though the ecosystem is still uneven in maturity. WordPress and the Base device are stable, while Strapi, Astro, the web dashboard, and Touch experience carry preview, new, or beta labels.

The project presents itself as free and open source, with public repositories and optional donation or sponsorship links rather than commercial subscription tiers. That makes it approachable for a developer willing to install and configure the relevant integration. Some remote and device paths still require outside pieces, including a Notificator account, an active API key, compatible hardware, or a user-owned MQTT service. Buyers should treat it as an actively developed independent project with a solid WordPress core and a broader ecosystem that is still taking shape.