Notifi

• Name: Notifi
• URL: https://notifi.network/
• Category: hosted notification control plane / onchain-event monitoring / cross-channel messaging middleware
• Summary: Notifi is hosted notification ops for crypto apps. The part worth keeping is the topic-filter-target model, hosted monitoring, and parser infrastructure; the rest is mostly admin-shell packaging around message delivery.
• What it does:
  • Lets application teams define notification topics, subscription flows, filters, and delivery targets for their users
  • Supports multiple trigger paths including manual community broadcasts, API-triggered notifications, and Notifi-hosted monitoring of on-chain or off-chain conditions
  • Provides an admin portal plus embeddable signup UI flows, including a React card component and related frontend tooling
  • Publishes TypeScript packages for frontend, React, Node.js, GraphQL, and web-push use cases
  • Maintains parser tooling for blockchain parsers that run on Notifi Fusion infrastructure
• Key claims:
  • The homepage title frames Notifi as “Web3 Notifications, Real-Time Alerts & Growth Marketing Tools,” which is useful mostly as a positioning clue; the real substance sits in the docs and repos
  • The Getting Started guide shows a full application control plane with Dapp accounts, topics, UI-card configuration, destinations, and first-message workflows rather than a thin API-only relay
  • The alerts docs define the basic unit cleanly: topic plus filter plus target, with topics triggerable manually, by API, or by Notifi-hosted monitoring services
  • The SDK surface spans frontend, React, Node, GraphQL, and web-push flows, which makes Notifi broader than a wallet-plugin or one-channel alert bot
  • The parser SDK is the useful wrinkle because it shows Notifi maintaining ingestion tooling for Fusion infrastructure instead of only running a marketer dashboard
  • The public GitHub org confirms an actual SDK and parser stack under a verified notifi.network organization
• Whitepaper: No canonical Notifi whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs, SDK repositories, parser tooling, and admin-portal-oriented integration guides; see ../whitepapers/notifi-primary-sources-2026-04-28.md.
• Sources:
  • https://notifi.network/
  • https://docs.notifi.network/docs/getting-started
  • https://docs.notifi.network/docs/integration-overview/alerts-in-depth
  • https://github.com/notifi-network
  • https://github.com/notifi-network/notifi-sdk-ts
  • https://raw.githubusercontent.com/notifi-network/notifi-sdk-ts/main/README.md
  • https://raw.githubusercontent.com/notifi-network/notifi-parser-sdk/master/README.md

Internal linkages

• Closest application-layer analogue: dialect.
• Useful wallet-address communication contrast: push-protocol.
• Useful wallet-scoped notification contrast: walletconnect-notify.

Control surface

• The leverage sits in topic design, filter logic, destination ownership, monitoring coverage, parser quality, and who actually gets to trigger delivery.

• Treat Notifi as hosted notification operations, not as a neutral messaging rail.

• Last reviewed: 2026-06-08 UTC