Key terms we use and their definition
Name | Text |
|---|---|
Active Community Members | A member that did, in the last month, at least one of the following: • PR Submitted (Databox CommonRoom?) • Opened Issues (Databox CommonRoom?) • 5 Discord messages (Databox CommonRoom?) • GitHub comment (Databox CommonRoom?) |
Active Community Moderator | An active community member that has at least a Discord moderator role or Github moderator role |
Active Organization | An Organization that uses Novu Cloud or Hybrid-cloud and is already serving at least 50 unique subscribers and has more than 1K events per month. |
Channel | A medium for sending notifications. Supported channels are email, SMS, push notitications, in-app, and chat. |
Churn Organization | An Organization that was Active before and stopped (minimum last month) |
Cloud GUI / Cloud Product | Novu’s user interface for the cloud offering at https://web.novu.co. |
Cloud Organizations | Amount of Organizations in Novu Cloud. |
Cloud Users | Amount of registered users in Novu Cloud. |
Components | Embeddable UI Components for web applications such as the <NotifcationCenter/> |
Content components | UI Components for content generation for the email, sms and chat notification channels |
Customers | Amount of paying Cloud Organization and On-Prem Organization. |
Novu V2 | The new way of defining notification workflows in a code following the durable execution function pattern. |
Evaluating Organization | An Organization that uses Novu Cloud or Hybrid-cloud and has less than 1K events per month but at least 1 event. |
Monthly Events | Trigger API call after the fanout for unique end-user, not including tests. |
Monthly Trigger API Calls | Trigger API call before the fanout for unique subscribers, not including tests. |
Non Evaluating Organization | An Organizations that is signed up to Novu Cloud or Hybrid-cloud and has zero events. |
Novu Business Use Case | A composition of various building blocks of Novu, and how it’s being used from the business or product perspective. |
Novu Cloud | Novu Platform hosted by Novu and data managed by Novu. |
Novu Hybrid-Cloud | Novu Platform hosted by Novu and data managed by our client. |
Novu Hybrid-Cloud Instance | A specific customers Novu Platform hosted by Novu and data managed by our client. |
Novu Technical Use Case | A composition of various building blocks of Novu, and how it’s being used from the engineer perspective. |
On-Prem Organizations | Organizations running a commercial Novu contract on their machines. |
Power Community Member | An active community member who has at least one of the following: • 3 PR Submitted • 3 Opened Issues • 10 Discord messages • 3 GitHub comment |
Power Organization | An Organization that uses Novu Cloud or Hybrid-cloud and is already serving at least 200 unique subscribers and has more than 60K events per month. |
Providers | Vendors that implement a channel specific delivery such as Sendgrid, Twilio or Firebase. |
Subscriber | User or Customer of one of our Organizations. |
Worker | The BullMQ Pro worker that processes jobs in the queue such as sending emails and SMS. |
Workflow | A workflow acts as the blueprint for the notifications that will be sent. The workflow encapsulates the entire flow and rules of messages that are being sent. This is where all the different channels, filters, rules and actions are tied together under a single entity. |