Our take
Quietno commits in the last 90 days- Activity
- 31
- Community
- 47
- Issues
- 21
- Pull requests
- 20
+0 stars in the last 30 days
Mailroom is a focused Go framework for teams prepared to build and maintain custom notification logic, with a quiet recent development period worth factoring into adoption plans.
Good fit if
- You need to turn external events or webhooks into user-specific notifications across transports.
- Your team is comfortable implementing event transformations and extending integrations in Go.
- You value an actively released project with multiple contributors, while accepting that no commits have landed in the last 90 days.
Look elsewhere if
- You need a complete, ready-to-use notification service rather than a framework that expects custom code.
- Your project cannot accept an API that the maintainers describe as alpha and potentially subject to change.
- You require visible recent issue or pull-request throughput, since none were recorded as closed or merged in the last 90 days.
All health signals
| Last commit | 2026-09-17 (22 days ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 1 (latest v0.6.1, 2026-02-25) |
| Contributors | 7 (top contributor: 55% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 23 months |
Checked on 2026-10-10 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
576Forks
19Change since Nov 16, 2026: 0 stars·0 forks
Overview
Mailroom provides a framework for receiving events from external systems and turning them into notifications for users. It addresses the integration work between incoming webhooks, identity matching, user preferences, message formatting, and delivery through channels such as email or Slack.
It is aimed at developers who want to implement their own event-to-notification logic while relying on Mailroom for routing and delivery concerns. It is not a ready-made notification product: teams need to supply the code that transforms events into notifications and configure the relevant integrations.
Key Features
- Accepts incoming webhooks as a notification relay for external systems.
- Routes notifications to users according to their preferences and notification type.
- Supports formatting notifications for different transports, including email and Slack.
- Helps match usernames, email addresses, and IDs across systems.
- Provides logging, error handling, and retries as part of the delivery flow.
- Allows teams to add event types and transports as their requirements evolve.
Use Cases
- A platform team can centralize webhook handling and route code review or build events to users through their preferred channels.
- Developers integrating multiple external systems can map each system's user identifiers to a shared identity model.
- An application team can build custom notifications from its own event transformations without implementing every delivery and retry concern itself.
- Teams with different notification preferences can send different event categories through different transports, such as Slack for build failures and email for review requests.
What you need
Detected in the repository
- Go 1.26.0 or newer (from go.mod)
- A test suite and automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
See the Getting Started guide and internal/example.go for setup and usage. Run make to run the project's linters and tests locally. See the README for the full documentation links.
Alternatives
- ntfy: ntfy sends HTTP-published messages to phone and desktop subscribers, rather than providing a Go framework for preference-based user notification routing.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| mailroom | Go | Apache-2.0 | 576 | Quiet |
| ntfy | Go | Apache-2.0 | 34.6k | Active |
Considerations
The project describes itself as alpha, so its API may change. Measured activity is quiet: there have been no commits in the last 90 days and no issues closed or pull requests merged in that period, although a release was published within the last year. Seven contributors are recorded, and contributions are not concentrated primarily in one person. The project requires Go 1.26.0; the provided requirements do not list Docker, a database, or other runtime services.
Found this useful?
Share it with someone who would like mailroom.