/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

novuhq/novu

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T15:47:00.908Z

1mo ago

novuhq/novu

Novu is a large, actively maintained open-source notification infrastructure repository for multi-channel delivery. It focuses on a unified API, an embeddable Inbox / notification center, workflow handling, and support for Email, SMS, Push, Slack, and chat. The repo appears broad and production-oriented, with a large community footprint and frequent recent commits.

Loading tags...

Stars38,745

Forks4,249

Default branchnext

Last pushed2026-03-30T15:39:48Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if you want a customized Novu derivative and can tolerate substantial drift from upstream. For most adopters, upstream Novu is the safer base; this fork is best for teams that need the specific added workflow/UI behavior and are prepared to maintain it themselves.

Prefer this fork only if its custom workflow/tooling changes are exactly what you need and you are comfortable owning a large, stale codebase. If you want current Novu features, compatibility, and lower maintenance risk, upstream is the safer choice.

Prefer this fork only if its dashboard/workflow changes match your product requirements and you are prepared to maintain a large downstream codebase. If you want an actively maintained, upstream-compatible notification platform, upstream Novu is the safer choice.

Choose this fork only if you need its custom operational workflow changes and are prepared to maintain a large, stale divergence. For most adopters, upstream Novu is the safer choice because it is far more current and feature-complete.

Choose this fork only if its custom behavior is the goal and you can maintain it yourself. If you want the latest Novu platform with minimal drift and faster access to upstream fixes, upstream is the safer choice.

Prefer upstream unless you specifically need this fork's custom workflow/runtime changes and are prepared to maintain a large, stale divergence. The fork looks better as an internal snapshot than as a foundation for a fresh adoption.

Choose this fork only if you specifically need its older provider-focused shape and are willing to own the maintenance burden. For most adopters, upstream is the safer choice because this fork is materially behind and likely missing major current features and fixes.

Adopt this only if you specifically want a clean Novu baseline to customize yourself. If you want the latest Novu capabilities and fixes out of the box, upstream is the better choice.

Choose this fork if you want Novu plus custom workflow and operational behavior and can accept ongoing merge work. Choose upstream if you want the latest maintained baseline with lower drift and fewer upgrade risks.

Prefer this fork only if you need its specific custom workflow and framework changes and are willing to own long-term merge and upgrade work. If you want the latest Novu features, compatibility, and active maintenance, upstream is the safer choice.

Fork comparison

midday-ai/novu

38/100

stale

significant_divergence

Choose this fork only if you want a customized Novu derivative and can tolerate substantial drift from upstream. For most adopters, upstream Novu is the safer base; this fork is best for teams that need the specific added workflow/UI behavior and are prepared to maintain it themselves.

Likely purpose

To serve as a product-specific notification platform fork, likely adding internal workflow/product integrations and customizing the dashboard, API, and generated SDK artifacts for a narrower deployment than upstream Novu.

Best for

A team that wants a bespoke notification platform and is willing to own a long-lived fork.; Developers embedding a notification center into a specific product with custom workflow rules and dashboard behavior.; Organizations that value product-specific control over staying current with upstream Novu.; Teams with enough engineering capacity to absorb upstream changes selectively rather than track mainline closely.

Additional features

Custom embedded notification-center experience and related UI polish, based on changes in dashboard/chat and notification-center paths.
Expanded workflow handling around step resolution, including delay, digest, and throttle step types.
API property-optionality checks and generated API/Postman artifacts, suggesting tighter SDK/spec generation workflows.
Environment-variable and system configuration fixes in the API service, indicating more deployment-specific operational support.
Email and locale-related tooling/customization, including updates in email renderers and shared locale utilities.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.

Missing features

The fork lags upstream substantially, so newer upstream work after 2024-03 is likely missing or incomplete.
Large upstream API/spec and test-suite changes suggest the fork may be missing newer notification workflow, inbox, and provider improvements.
Removed files/exports and large deletions indicate some upstream utilities, generated assets, or integration surfaces may no longer be present or are harder to use.
Because it is far behind upstream, adopters should expect missing security fixes, dependency updates, and platform refinements that landed later upstream.
It trails upstream by 203 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Much larger than a lightly customized fork: the diff spans core API, dashboard, workflows, SDK generation, and docs.
Likely better suited for a team that wants control over notification UX and workflow behavior than for someone wanting upstream parity.
Recent commits show active internal maintenance in 2026 on the upstream side, so the codebase it forked from is still moving quickly.

Risks

Very high maintenance burden from the divergence size and 203 commits behind upstream.
Upstream compatibility is likely poor, so merging future changes will be expensive.
The fork appears dormant relative to the current date, so adopters may inherit unreviewed technical debt and stale dependencies.
Potential feature regressions are hard to rule out because the structured facts show many deletions and renamed files, not just additive customization.

novuhq/novu · Discofork