Skip to content

Commit 38b5ed4

Browse files
authored
Merge pull request #234 from flashcatcloud/docs/comparison-refresh
docs(comparison): sharpen status page, AI SRE billing, and stakeholder pricing points
2 parents 27e611a + 17c267d commit 38b5ed4

2 files changed

Lines changed: 34 additions & 20 deletions

File tree

en/on-call/quickstart/comparison.mdx

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ The two vendors take different approaches to AI: **PagerDuty splits AI across mu
207207
| **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 |
208208
| **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 |
209209
| **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 |
211211

212212
<Note>
213213
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
237237

238238
---
239239

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.
241241

242242
| Dimension | Flashduty | PagerDuty |
243243
| --- | --- | --- |
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 |
250+
| **Display Customization** | Custom domain, calendar + list dual views, configurable availability display, component visibility controls | Custom domain, logo/color scheme/header and footer |
251+
| **Atlassian Migration** | **Compatible subscription URLs** (`history.rss` / `history.atom`) + one-click CLI migration of components, incidents, and subscribers ||
249252

250253
<Tip>
251254
If you're currently using Atlassian Statuspage, see our in-depth [Flashduty vs Atlassian Statuspage comparison](/en/on-call/statuspage/comparison).
@@ -277,9 +280,10 @@ Pricing is a critical factor in enterprise decisions—you need to choose the mo
277280
| --- | --- | --- |
278281
| **Pricing Page** | [flashduty.com/pricing](https://www.flashduty.com/pricing) | [pagerduty.com/pricing](https://www.pagerduty.com/pricing/incident-response/) |
279282
| **Billing Model** | License fee + excess communication fees | Seat fee + Add-Ons |
280-
| **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 |
281284
| **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 |
283287
| **Free Trial** | Professional 14 days free, extendable on request | Business 14 days free |
284288

285289
### Billing Model Difference: License vs Full-team Seats
@@ -290,13 +294,15 @@ This is the most fundamental pricing difference between Flashduty and PagerDuty.
290294
<Tab title="PagerDuty Model">
291295
PagerDuty requires **a paid seat for every user who needs to receive notifications**. This means:
292296
- 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
293298
- To control costs, organizations often buy seats only for core personnel, causing **critical notifications to miss** relevant stakeholders
294299
- Total cost = seat price × the number of users who need notifications
295300
</Tab>
296301
<Tab title="Flashduty Model">
297302
Flashduty decouples **incident handling permissions** from **notification delivery**:
298303
- Only members who need to log in to the platform to **view and handle** incidents require a License
299304
- **All members** (including those without a License) can passively receive alert notifications
305+
- Status page subscribers are likewise **free and require no account registration**
300306
- Total cost = License price × active handler count (typically only 10%–20% of the team)
301307
</Tab>
302308
</Tabs>
@@ -364,7 +370,8 @@ Quality service support is essential for successful product implementation.
364370
<CardGroup cols={2}>
365371
<Card title="Flashduty Highlights" icon="star">
366372
- **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
368375
- **Localization Advantages**: Complete Mainland China IM support (including on-premises versions), voice/SMS support
369376
- **Feature Innovation Leadership**: Incident inhibition, storm warning, dynamic assignment, AI postmortems, war rooms, external incident submission, and more
370377
- **Thoughtful Service Experience**: Dedicated IM groups, remote expert support, fast on-demand integration support

zh/on-call/quickstart/comparison.mdx

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ keywords: ["产品对比", "PagerDuty", "功能对比", "价格对比", "竞品
207207
| **知识与记忆** | [知识库](/zh/ai-sre/knowledge)(DUTY.md + 文件引用)、[自动记忆提炼](/zh/ai-sre/memory)`/init` 可导入 Claude Code、Cursor 等工具的已有知识 | 公开资料未见 |
208208
| **AI 复盘** | 故障复盘一键生成 + 自动化定时复盘 | 复盘(原 Jeli,正并入主产品)随 Professional 及以上提供,Professional/Business 档限每年 300 次 |
209209
| **使用洞察** | [/insight](/zh/ai-sre/insight) 复盘近 30 天 AI 使用情况,量化摩擦并给出改进建议 | 公开资料未见 |
210-
| **计费方式** | 专业版提供,详见[官网价格页](https://www.flashduty.com/zh/pricing) | AIOps 单独加购($699+/月起,按事件量计费);Advance 各档位含一次性 AI Action 额度,超额需购买 AI credits |
210+
| **计费方式** | **公测期间免费**,正式商用后按 credits 用量计费,详见[官网价格页](https://www.flashduty.com/zh/pricing) | AIOps 单独加购($699+/月起,按事件量计费);Advance 各档位含一次性 AI Action 额度,超额需购买 AI credits |
211211

212212
<Note>
213213
PagerDuty AIOps 在超大规模事件关联场景上打磨多年,能力成熟。两者的核心差异:一是**售卖方式**——Flashduty 一体化提供,PagerDuty 分产品加购;二是**处置路径**——Flashduty 在会话中动态排查处置,PagerDuty 的自动修复依赖预先配置的固定脚本。
@@ -237,15 +237,18 @@ PagerDuty AIOps 在超大规模事件关联场景上打磨多年,能力成熟
237237

238238
---
239239

240-
对外传递服务状态是故障管理的最后一公里。
240+
对外传递服务状态是故障管理的最后一公里。Flashduty 状态页随 On-call 提供且功能更全;PagerDuty Status Pages 按套餐与订阅量分层收费。
241241

242242
| 维度 | Flashduty | PagerDuty |
243243
| --- | --- | --- |
244-
| **提供方式** | [状态页](/zh/on-call/statuspage/statuspage)随 On-call 产品提供 | 基础套餐仅含 1 个公开状态页,更多页面与订阅者需付费加购(价格需询销售) |
245-
| **订阅方式** | 邮件订阅 + **RSS 2.0 / Atom 1.0 免确认订阅**,支持 ETag 缓存 | Email / Slack / Webhook,未见 RSS/Atom 订阅 |
246-
| **Atlassian 迁移** | **兼容 Atlassian Statuspage 订阅地址**`history.rss` / `history.atom`),迁移后订阅者无感 ||
247-
| **可用性证明** | 自动沉淀历史 Uptime 数据,将 SLA 承诺转化为可验证记录 | 支持 7/30/90 天 uptime 展示 |
248-
| **维护公告** | ✅ 计划内维护窗口提前公布 ||
244+
| **提供方式** | [状态页](/zh/on-call/statuspage/statuspage)随 On-call 产品提供,**公开 + 内部状态页一体** | 基础套餐仅含 1 个公开状态页;内部状态页需 Business 及以上,私有状态页在 Premium 加购包 |
245+
| **订阅费用** |**订阅者免费、无需账号** | 公开页订阅免费但按套餐限名额(Professional 250 / Business 500 / Enterprise 1,000,超出需向销售加购);**内部状态页与内部事件动态的围观者需持账号,最低为付费 Stakeholder 席位** |
246+
| **订阅粒度与方式** | 全量/组件/事件**三级订阅**,邮件 + **RSS 2.0 / Atom 1.0 免确认订阅**,订阅者批量导入导出与自助管理 | Email / Slack / Webhook,未见 RSS/Atom 订阅 |
247+
| **多语言通知** | ✅ 原生保留订阅者语言偏好 | 公开资料未见 |
248+
| **内部状态页通知** | 飞书/钉钉/企业微信/Slack 原生推送 | 查看者需 PagerDuty 账号(Stakeholder 席位起) |
249+
| **可用性证明** | 自动沉淀历史 Uptime,**维护事件不计入 uptime 损耗** | 支持 7/30/90 天 uptime 展示 |
250+
| **展示定制** | 自定义域名、日历 + 列表双视图、可用性展示方式可配置、组件展示控制 | 自定义域名、Logo/配色/页头页脚 |
251+
| **Atlassian 迁移** | **兼容订阅地址**`history.rss` / `history.atom`)+ CLI 一键迁移组件、事件与订阅者 ||
249252

250253
<Tip>
251254
如果您正在使用 Atlassian Statuspage,可参考 [Flashduty vs Atlassian Statuspage 深度对比](/zh/on-call/statuspage/comparison)
@@ -277,9 +280,10 @@ PagerDuty AIOps 在超大规模事件关联场景上打磨多年,能力成熟
277280
| --- | --- | --- |
278281
| **价格页面** | [flashduty.com/zh/pricing](https://www.flashduty.com/zh/pricing) | [pagerduty.com/pricing](https://www.pagerduty.com/pricing/incident-response/) |
279282
| **收费模式** | License 费 + 超额通信费用 | 席位费 + Add-Ons |
280-
| **版本定价** | **专业版 ¥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 额度、超额另付 |
281284
| **计费对象** |**仅对活跃用户收费**——只有查看和处理故障的成员需要 License |**所有用户都需付费**——包括仅接收通知的成员 |
282-
| **通知能力** | ✅ 无 License 成员也可接收所有通知(邮件、短信、电话、IM) | ❌ 必须购买席位才能接收通知 |
285+
| **通知能力** | ✅ 无 License 成员也可接收所有通知(邮件、短信、电话、IM) | ❌ 接收通知需购买席位;仅围观内部事件动态也需最低 Stakeholder 付费席位 |
286+
| **状态页订阅** | ✅ 免费、无需账号、不占 License | 公开页订阅按套餐限名额(250/500/1,000)、超出加购;内部状态页围观需 Stakeholder 席位 |
283287
| **免费试用** | 专业版 14 天免费,可申请延长 | Business 版 14 天免费 |
284288

285289
### 计费模式差异:License vs 全员席位
@@ -290,13 +294,15 @@ PagerDuty AIOps 在超大规模事件关联场景上打磨多年,能力成熟
290294
<Tab title="PagerDuty 模式">
291295
PagerDuty 要求**每一个需要接收通知的用户都购买席位**。这意味着:
292296
- 一个 100 人的团队,如果所有人都需要在故障时收到通知,就需要购买 100 个席位
297+
- 仅需**围观**内部事件动态的干系人(管理层、客服等),也要购买最低档的 Stakeholder 付费席位
293298
- 为控制成本,企业往往只为核心人员购买席位,导致**关键通知无法触达**相关人员
294299
- 总费用 = 席位单价 × 全部需通知的用户数
295300
</Tab>
296301
<Tab title="Flashduty 模式">
297302
Flashduty 将**故障处理权限****通知接收**解耦:
298303
- 只有需要登录平台**查看和处理**故障的成员才需要 License
299304
- **所有成员**(包括无 License 成员)都可以被动接收告警通知
305+
- 状态页订阅者同样**免费且无需注册账号**
300306
- 总费用 = License 单价 × 活跃处理人数(通常仅为团队的 10%~20%)
301307
</Tab>
302308
</Tabs>
@@ -364,7 +370,8 @@ PagerDuty AIOps 在超大规模事件关联场景上打磨多年,能力成熟
364370
<CardGroup cols={2}>
365371
<Card title="Flashduty 突出优势" icon="star">
366372
- **AI SRE 自治排障**:能进入真实环境执行诊断的 SRE Agent,IM 原生协同
367-
- **更优价格策略**:仅活跃处理人员需要 License,大团队可节省 80%~90% 费用
373+
- **更优价格策略**:仅活跃处理人员需要 License,通知接收与状态页订阅零费用,大团队可节省 80%~90% 费用
374+
- **状态页更全更省**:公开 + 内部一体、多语言通知、三级订阅粒度,随产品提供
368375
- **本土化优势**:完善的中国大陆 IM(含私有化版本)、语音短信支持
369376
- **功能创新领先**:故障抑制、风暴预警、动态分派、AI 复盘、作战室、外部故障提交等
370377
- **贴心服务体验**:专属 IM 群、远程专家支持、集成按需快速支持

0 commit comments

Comments
 (0)