You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: explain License (active user) billing model and PagerDuty cost comparison
Expand pricing pages with detailed License model explanation: who needs a
License, why the model decouples handling from notifications, and real-world
example showing 80-90% cost savings for large teams (10-15 Licenses for a
100-person team). Add new FAQ "How many Licenses does my team need?".
Expand comparison pages with side-by-side billing model analysis, tabbed
PagerDuty vs Flashduty model explanation, and concrete cost comparison table.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|**Edition Pricing**|**Professional ¥199/user/month**, full features including AIops | Business $41/user/month, AIops and other features require separate Add-Ons |
187
-
|**Active Users**| ✅ **Only charges for active users** (members who view or handle incidents that month; receiving notifications only doesn't count as active) | ❌ All users must pay |
187
+
|**Billing Target**| ✅ **Only active users are charged**—only members who view and handle incidents need a License | ❌ **All users must pay**—including members who only receive notifications |
188
+
|**Notification Capability**| ✅ Members without a License can still receive all notifications (email, SMS, voice call, IM) | ❌ A paid seat is required to receive notifications |
188
189
|**Free Trial**| Professional 14 days free, can request extension | Business 14 days free |
189
190
191
+
### Billing Model Difference: License vs Full-team Seats
192
+
193
+
This is the most fundamental pricing difference between Flashduty and PagerDuty.
194
+
195
+
<Tabs>
196
+
<Tabtitle="PagerDuty Model">
197
+
PagerDuty requires **a paid seat for every user who needs to receive notifications**. This means:
198
+
- A 100-person team where everyone needs incident notifications requires 100 paid seats
199
+
- To control costs, organizations often limit seats to core personnel, causing **critical notifications to miss** relevant stakeholders
200
+
- Total cost = seat price × all users who need notifications
201
+
</Tab>
202
+
<Tabtitle="Flashduty Model">
203
+
Flashduty decouples **incident handling permissions** from **notification delivery**:
204
+
- Only members who need to log in to **view and handle** incidents require a License
205
+
- **All members** (including those without a License) can passively receive alert notifications
206
+
- Total cost = License price × active incident handlers (typically only 10%–20% of the team)
207
+
</Tab>
208
+
</Tabs>
209
+
210
+
### Cost Comparison Example
211
+
212
+
For a 100-person engineering team where 15 people actively handle incidents:
213
+
214
+
| Cost Item | Flashduty Professional | PagerDuty Business |
**Cost Advantage**: Flashduty's active user billing model can significantly reduce total cost of ownership, especially suitable for large teams.
223
+
**Key Difference**: Flashduty lets you **achieve 100-person notification coverage at the cost of 15 people**. To achieve the same coverage with PagerDuty, you must pay for all 100 users. Learn more about the [License model explained](/en/platform/pricing#license-model-explained).
192
224
</Tip>
193
225
194
226
---
@@ -222,7 +254,7 @@ Quality service support is essential for successful product implementation.
222
254
223
255
<CardGroupcols={2}>
224
256
<Cardtitle="Flashduty Highlights"icon="star">
225
-
-**Better Pricing Strategy**: Active user billing, full features including AIops
257
+
-**Better Pricing Strategy**: Only active incident handlers need a License, saving 80%–90% for large teams
226
258
-**Localization Advantages**: Complete Mainland China IM, voice/SMS support
227
259
-**Feature Innovation Leadership**: Exclusive features like inhibition, storm warning, dynamic assignment
228
260
-**Thoughtful Service Experience**: Dedicated IM groups, remote expert support
Copy file name to clipboardExpand all lines: en/platform/pricing.mdx
+51-7Lines changed: 51 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,7 +103,39 @@ On the Free plan, notifications **stop** once the quota is exhausted. On Standar
103
103
| Standard | Email / Ticket | 5×8 hours |
104
104
| Pro | Dedicated support group | 7×8 hours |
105
105
106
-
### License Types
106
+
### License Model Explained
107
+
108
+
Unlike products such as PagerDuty that charge for **every user**, Flashduty uses a **License (active user)** billing model—only members who need to **view and handle incidents** require a License. Other members can receive alert notifications at no additional cost.
109
+
110
+
#### Who Needs a License?
111
+
112
+
| Role | License Required? | Explanation |
113
+
| --- | :---: | --- |
114
+
| On-call engineers | ✅ | Need to view incident details, acknowledge, and handle incidents |
115
+
| Team leads | ✅ | Need to view incidents, configure escalation rules and schedules |
116
+
| Notified developers / ops | ❌ | Only need to passively receive notifications, no platform login required |
117
+
| Management | ❌ | Can monitor overall status via analytics dashboards or status pages |
118
+
| External collaborators | ❌ | Get information through webhooks, email, or status pages |
119
+
120
+
<Tip>
121
+
**Cost advantage for large teams**: In practice, a 100-person engineering team typically has only 10–20 people who actively handle incidents day-to-day. The rest only need to receive notifications when relevant incidents occur. This means you may only need 10–20 Licenses instead of paying for all 100 people—**reducing costs by 80%–90%**.
122
+
</Tip>
123
+
124
+
#### Why the License Model?
125
+
126
+
Traditional per-user pricing (like PagerDuty) requires purchasing a seat for every user who receives notifications, which creates two problems in practice:
127
+
128
+
1.**Wasted spend**: Most team members only need to receive notifications when incidents occur—they never log in to view or handle incidents—yet each still requires a full-price seat
129
+
2.**Insufficient notification coverage**: To control costs, organizations often limit who receives notifications, causing critical information to miss key stakeholders
130
+
131
+
Flashduty's License model decouples **incident handling capability** from **notification delivery**:
132
+
133
+
-**Members with a License**: Full permissions to view, handle, and configure incidents
134
+
-**Members without a License**: Can passively receive all alert notifications (email, SMS, voice call, IM), share the tenant's notification quota, ensuring information reaches everyone who needs it
135
+
136
+
This approach ensures comprehensive notification coverage while significantly reducing total cost of ownership.
137
+
138
+
#### License Types
107
139
108
140
<Tabs>
109
141
<Tabtitle="Fixed License">
@@ -121,7 +153,7 @@ On the Free plan, notifications **stop** once the quota is exhausted. On Standar
121
153
</Tab>
122
154
</Tabs>
123
155
124
-
### Permissions for Members Without License
156
+
####Permissions for Members Without License
125
157
126
158
<Warning>
127
159
Members without a License have limited functionality and can only passively receive alert messages.
@@ -131,7 +163,8 @@ Members without a License have limited functionality and can only passively rece
| Escalation rule reference | ✅ Can be added as notification targets in escalation rules |
135
168
| Notification quota | ✅ Shares the tenant's email, SMS, and phone call quota |
136
169
137
170
---
@@ -187,17 +220,28 @@ The Free plan is suitable for evaluating product features. The Pro plan is bille
187
220
188
221
<AccordionGroup>
189
222
<Accordiontitle="How does On-call calculate active users?">
190
-
Users who use commercial features within the month are counted as active users. At the end of each monthly cycle:
223
+
Members who use commercial features (viewing or handling incidents) within the month are counted as active users.**Receiving alert notifications alone does not count as active usage.** At the end of each monthly cycle:
191
224
- Fixed Licenses remain valid
192
225
- Temporary Licenses are automatically released
193
226
- When a member is deleted, their License is automatically released
194
227
</Accordion>
195
228
229
+
<Accordiontitle="How many Licenses does my team need?">
230
+
Only members who need to **log in to the platform to view incident details, acknowledge, and handle incidents** require a License. Members who only receive alert notifications do not need one.
231
+
232
+
**How to estimate**: Count the core personnel in your team who participate in daily on-call and incident response, typically:
233
+
- Frontline on-call engineers
234
+
- Team leads involved in incident handling
235
+
- Administrators who configure escalation rules and schedules on the platform
236
+
237
+
**Real-world example**: For a 100-person engineering team, typically only 10–20 people need to log in and handle incidents daily. The remaining 80–90 people only need to receive notifications when relevant incidents occur. Therefore, you only need 10–20 Licenses, **saving 80%–90% compared to paying for every team member**.
238
+
</Accordion>
239
+
196
240
<Accordiontitle="What can members without a License do?">
-**Can**: Passively receive alert messages (email, SMS, voice call, IM), be referenced as notification targets in escalation rules, share tenant notification quota
198
242
-**Cannot**: View/handle incidents, perform any platform configuration operations
199
-
200
-
In escalation rules, you can choose to notify members without a License about incidents, but they cannot perform any operations on the incident.
243
+
244
+
In escalation rules, you can choose to notify members without a License about incidents, but they cannot perform any operations on the incident. This means you can include your entire team in the notification scope without purchasing a License for every person.
201
245
</Accordion>
202
246
203
247
<Accordiontitle="How are RUM sessions calculated?">
0 commit comments