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
Copy file name to clipboardExpand all lines: en/on-call/quickstart/comparison.mdx
+17-10Lines changed: 17 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -207,7 +207,7 @@ The two vendors take different approaches to AI: **PagerDuty splits AI across mu
207
207
|**Knowledge & Memory**|[Knowledge base](/en/ai-sre/knowledge) (DUTY.md + file references), [automatic memory extraction](/en/ai-sre/memory); `/init` can import existing knowledge from tools like Claude Code and Cursor | Not found in public materials |
208
208
|**AI Postmortems**| One-click postmortem generation + scheduled automated postmortems | Postmortems (formerly Jeli, being merged into the core product) are available from Professional up, capped at 300 per year on the Professional/Business tiers |
209
209
|**Usage Insight**|[/insight](/en/ai-sre/insight) reviews the last 30 days of AI usage, quantifying friction points and providing improvement recommendations | Not found in public materials |
210
-
|**Billing**|Included with the Professional plan—see the [pricing page](https://www.flashduty.com/pricing) for details | AIOps sold as a separate add-on (starting at $699+/month, billed by event volume); Advance tiers each include a one-time AI Action allowance, with additional AI credits required beyond that |
210
+
|**Billing**|**Free during the public beta**; usage-based credits billing after general availability—see the [pricing page](https://www.flashduty.com/pricing) for details | AIOps sold as a separate add-on (starting at $699+/month, billed by event volume); Advance tiers each include a one-time AI Action allowance, with additional AI credits required beyond that |
211
211
212
212
<Note>
213
213
PagerDuty's AIOps has been refined over many years for large-scale event correlation and is a mature capability. The core differences between the two: first, **how it's sold**—Flashduty bundles it in, while PagerDuty sells it as separate product add-ons; second, **the remediation path**—Flashduty investigates and resolves dynamically within a session, while PagerDuty's automated remediation depends on pre-configured, fixed scripts.
@@ -237,15 +237,18 @@ Incident handling workflows differ from team to team—**every step in the proce
237
237
238
238
---
239
239
240
-
Communicating service status to the outside world is the last mile of incident management.
240
+
Communicating service status to the outside world is the last mile of incident management. Flashduty's Status Page ships with On-call and is more full-featured; PagerDuty Status Pages are tiered by plan and subscriber volume.
241
241
242
242
| Dimension | Flashduty | PagerDuty |
243
243
| --- | --- | --- |
244
-
|**Availability**|[Status Page](/en/on-call/statuspage/statuspage) is included with the On-call product | The base plan includes only 1 public status page; additional pages and subscribers require a paid add-on (pricing on request) |
245
-
|**Subscription Methods**| Email subscription + **confirmation-free RSS 2.0 / Atom 1.0 subscriptions**, with ETag caching support | Email / Slack / Webhook; no RSS/Atom subscription found |
246
-
|**Atlassian Migration**|**Compatible with Atlassian Statuspage subscription URLs** (`history.rss` / `history.atom`)—subscribers notice nothing after migration | — |
247
-
|**Proof of Availability**| Automatically accumulates historical uptime data, turning SLA commitments into verifiable records | Supports 7/30/90-day uptime display |
248
-
|**Maintenance Announcements**| ✅ Planned maintenance windows announced in advance | ✅ |
244
+
|**Availability**|[Status Page](/en/on-call/statuspage/statuspage) is included with the On-call product, **public + internal status pages in one**| The base plan includes only 1 public status page; internal status pages require Business or above, and private status pages are a Premium add-on |
245
+
|**Subscription Cost**| ✅ **Free for subscribers, no account required**| Public-page subscriptions are free but capped by plan (Professional 250 / Business 500 / Enterprise 1,000; exceeding the cap requires a sales add-on); **viewers of internal status pages and internal incident activity must hold an account, at minimum a paid Stakeholder license**|
246
+
|**Subscription Granularity & Methods**|**Three-tier subscriptions** (all / component / event level), email + **confirmation-free RSS 2.0 / Atom 1.0 subscriptions**, with bulk import/export and self-service subscriber management | Email / Slack / Webhook; no RSS/Atom subscription found |
247
+
|**Multilingual Notifications**| ✅ Natively preserves each subscriber's language preference | Not found in public materials |
248
+
|**Internal Status Page Notifications**| Native push to Feishu/Lark, Dingtalk, WeCom, and Slack | Viewers need a PagerDuty account (starting at a Stakeholder license) |
249
+
|**Proof of Availability**| Automatically accumulates historical uptime, **with maintenance events excluded from uptime loss**| Supports 7/30/90-day uptime display |
|**Edition Pricing**|**Professional ¥199/user/month**, including AI capabilities like AI SRE autonomous troubleshooting, intelligent grouping, AI summaries, and AI postmortems| Business $41/user/month (annual billing); AIOps requires a separate add-on (starting at $699+/month, billed by event volume); Advance tiers each include a one-time AI Action allowance, with extra usage billed separately |
283
+
|**Edition Pricing**|**Professional ¥199/user/month**, including intelligent grouping, AI summaries, and AI postmortems; AI SRE is free during the public beta and billed on usage-based credits after general availability| Business $41/user/month (annual billing); AIOps requires a separate add-on (starting at $699+/month, billed by event volume); Advance tiers each include a one-time AI Action allowance, with extra usage billed separately |
281
284
|**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 |
282
-
|**Notification Capability**| ✅ Members without a License can still receive all notifications (email, SMS, voice call, IM) | ❌ A paid seat is required to receive notifications |
285
+
|**Notification Capability**| ✅ Members without a License can still receive all notifications (email, SMS, voice call, IM) | ❌ A paid seat is required to receive notifications; even just viewing internal incident activity requires at least a paid Stakeholder license |
286
+
|**Status Page Subscriptions**| ✅ Free, no account required, doesn't consume a License | Public-page subscriptions are capped by plan (250/500/1,000), with an add-on required beyond that; viewing internal status pages requires a Stakeholder license |
283
287
|**Free Trial**| Professional 14 days free, extendable on request | Business 14 days free |
284
288
285
289
### Billing Model Difference: License vs Full-team Seats
@@ -290,13 +294,15 @@ This is the most fundamental pricing difference between Flashduty and PagerDuty.
290
294
<Tabtitle="PagerDuty Model">
291
295
PagerDuty requires **a paid seat for every user who needs to receive notifications**. This means:
292
296
- A 100-person team where everyone needs incident notifications requires purchasing 100 seats
297
+
- Stakeholders who only need to **view** internal incident activity (management, customer support, etc.) must also purchase at least the entry-level paid Stakeholder license
293
298
- To control costs, organizations often buy seats only for core personnel, causing **critical notifications to miss** relevant stakeholders
294
299
- Total cost = seat price × the number of users who need notifications
295
300
</Tab>
296
301
<Tabtitle="Flashduty Model">
297
302
Flashduty decouples **incident handling permissions** from **notification delivery**:
298
303
- Only members who need to log in to the platform to **view and handle** incidents require a License
299
304
- **All members** (including those without a License) can passively receive alert notifications
305
+
- Status page subscribers are likewise **free and require no account registration**
300
306
- Total cost = License price × active handler count (typically only 10%–20% of the team)
301
307
</Tab>
302
308
</Tabs>
@@ -364,7 +370,8 @@ Quality service support is essential for successful product implementation.
364
370
<CardGroupcols={2}>
365
371
<Cardtitle="Flashduty Highlights"icon="star">
366
372
-**AI SRE Autonomous Troubleshooting**: An SRE Agent that can enter your real environment to run diagnostics, with native IM collaboration
367
-
-**Better Pricing Strategy**: Only active incident handlers need a License, saving 80%–90% for large teams
373
+
-**Better Pricing Strategy**: Only active incident handlers need a License, with zero cost for notification recipients and status page subscribers, saving 80%–90% for large teams
374
+
-**Status Pages, More Complete and More Affordable**: Public + internal in one, multilingual notifications, three-tier subscription granularity, included with the product
368
375
-**Localization Advantages**: Complete Mainland China IM support (including on-premises versions), voice/SMS support
369
376
-**Feature Innovation Leadership**: Incident inhibition, storm warning, dynamic assignment, AI postmortems, war rooms, external incident submission, and more
370
377
-**Thoughtful Service Experience**: Dedicated IM groups, remote expert support, fast on-demand integration support
|**版本定价**|**专业版 ¥199/人/月**,含 AI SRE 自治排障、智能聚合、AI 摘要、AI 复盘等 AI 能力| Business 版 $41/人/月(年付);AIOps 需单独加购($699+/月起,按事件量计费),Advance 各档含一次性 AI Action 额度、超额另付 |
283
+
|**版本定价**|**专业版 ¥199/人/月**,含智能聚合、AI 摘要、AI 复盘;AI SRE 公测期免费,正式商用后按 credits 用量计费| Business 版 $41/人/月(年付);AIOps 需单独加购($699+/月起,按事件量计费),Advance 各档含一次性 AI Action 额度、超额另付 |
0 commit comments