Our take
Inactiveno commits in over a year- Activity
- 19
- Community
- 31
- Issues
- 21
- Pull requests
- 20
+0 stars in the last 30 days
- Fewer contributors than 82% of the projects we track
Notify covers a useful combination of REST-based and message-driven email and SMS delivery, but its prolonged inactivity makes it a cautious choice for new production dependencies.
Good fit if
- You are building on ASP.NET Core and MongoDB and want to evaluate an existing notification-service design.
- Your use case needs both REST and asynchronous messaging approaches for email or SMS.
- You can review and maintain the code yourself under the MIT license.
Look elsewhere if
- You need an actively maintained dependency: there have been no commits in over two years and no release in over a year.
- You need clear evidence of ongoing issue or pull request handling, which the recent activity data does not show.
- Your team cannot take on maintenance risk from a project where most contributions come from one person.
All health signals
| Last commit | 2024-09-22 (2.1 years ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 |
| Contributors | 3 (top contributor: 75% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 2 years |
Checked on 2026-10-30 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
166Forks
45Change since Nov 16, 2026: 0 stars·0 forks
Overview
Notify is an email and SMS notification service built on ASP.NET Core and MongoDB. It aims to give applications a shared way to send messages synchronously through REST or asynchronously through messaging, with delivery checks to support reliable dispatch.
The project also describes webhook integrations, background services, MassTransit, and RabbitMQ as part of its approach. It is aimed at teams building ASP.NET Core applications that want notification capabilities in a service they can run and extend.
Key Features
- Send email notifications through REST endpoints or messaging.
- Dispatch SMS through REST endpoints or messaging.
- Integrate with multiple SMS providers.
- Persist and manage notification data in MongoDB.
- Use webhooks to connect notifications with other services.
- Handle long-running operations with background services.
- Use MassTransit and RabbitMQ for asynchronous messaging.
Use Cases
- An ASP.NET Core team needs a shared service for sending application emails through an API or message queue.
- A product needs to send SMS through different providers and wants provider flexibility in its notification layer.
- A system needs to dispatch notifications asynchronously using RabbitMQ and MassTransit.
- A service needs webhook-based notification integrations alongside persistent notification data.
What you need
Detected in the repository
- C# (main language on GitHub)
- A test suite
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Clone the repository:
git clone https://github.com/thisisnabi/Notify.git
See the README for project details and setup guidance.
Alternatives
- mailroom: Mailroom is a Go framework for routing external events to email or Slack, while Notify is an ASP.NET Core service for email and SMS delivery via APIs or messaging.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| Notify | C# | MIT | 166 | Inactive |
| mailroom | Go | Apache-2.0 | 576 | Quiet |
Considerations
The project is marked inactive, with no recent commits or releases, so teams should assess whether they can maintain it if issues arise. The repository reports three contributors, with most contributions concentrated in one person. MongoDB is part of the stated design, and the README names RabbitMQ and MassTransit for asynchronous messaging. The README does not provide deployment instructions or explain the delivery-check behavior in detail.
Found this useful?
Share it with someone who would like Notify.