devkitshq
devkitshq presents notifkit as self-hosted notification infrastructure: a durable orchestration engine and typed SDK that lets an application send one notification call while notifkit handles routing, preferences, quiet hours, retries, fallback, scheduling, workflows, suppression, and delivery logs. It is intended to run inside the customer's own infrastructure and use the customer's provider accounts and data.
At a Glance
- Developers and product teams building applications with transactional notifications
- Small and medium applications, side projects, and staging environments
- Production teams wanting to own notification data and infrastructure
- AI-assisted development and terminal-agent users
- +1 more
AI Tools by devkitshq
(1)
notifkit
Self-Hosted Notification SDK
Discussions
No discussions yet
Be the first to start a discussion about devkitshq
Latest News
Client SDK adds dynamic contacts arrays, ergonomic addUser signature, and stronger SDK types
Added notifkit-create-project CLI helper and updated quickstart documentation
Resend provider switched to the Resend SDK for webhook verification; package bumped to 0.1.3
Slack promoted to a dedicated native notification channel
Products & Services
MIT-licensed, self-hosted notification infrastructure and TypeScript/Node.js SDK. It provides a REST API, server and worker pipelines, multi-channel notification orchestration, templates, preferences, quiet hours, suppression, retries, fallbacks, scheduling, workflows, segments/topics, delivery logs, metrics, and a dead-letter queue.
A stateless Model Context Protocol server over the notifkit REST API. It lets Claude Code, Claude Desktop, Cursor, Gemini, and other terminal agents send campaigns and notifications, manage templates and audiences, operate workflows, and inspect delivery logs.
An included read-only local dashboard for inspecting delivery and operational data; the project emphasizes terminal/API operation rather than a hosted console.
Market Position
notifkit positions itself as a durable, self-hosted notification layer rather than a marketing automation suite or hosted notification SaaS. Its README explicitly contrasts the project with Novu and says it does not replace Customer.io, OneSignal, or SendGrid; its differentiators are running in the customer's stack, bringing provider accounts, code-reviewed workflows, and built-in reliability/operational plumbing.
Founding Story
The repository says notification infrastructure looks simple until teams must handle queues, retries, provider adapters, preferences, quiet-hour logic, workflows, suppression, and operations. The creator says notifkit was built for their own company's need to deliver more than 100,000 notifications a day, to avoid rebuilding distributed notification plumbing and paying a SaaS fee per alert; the initial vision was a self-hosted durable notification layer.
Business Model
Revenue Model
The official site describes a self-hosted, open-source model: $0 to the project for running it, with no plans, seats, or per-message fee. Customers run the software on their own servers and bring their own provider accounts and keys, paying providers such as Resend, Firebase, or Twilio directly.
Pricing Tiers
No plans, seats, or per-message fee; runs on the customer's servers.
Target Markets
- Developers and product teams building applications with transactional notifications
- Small and medium applications, side projects, and staging environments
- Production teams wanting to own notification data and infrastructure
- AI-assisted development and terminal-agent users
- Teams seeking an alternative to hosted notification/marketing automation services
- Product notifications such as order, payment, onboarding, and activation messages
- Transactional and multi-channel delivery with provider fallback
- Cart-abandonment, reminder, drip, and other event-driven workflows
- Campaign sends and operational reporting from a terminal or AI agent
- Teams that need notification infrastructure in their own stack rather than a hosted SaaS
- Small and medium applications, side projects, staging, and production deployments