docs(comparison): tighten competitive facts, add cost chart, fix dollar rendering

- War room: supported on Slack too, drop the China-IM-only qualifier (Teams not yet supported)
- Status Pages: full feature parity from the free tier vs plan-tiered features
- AI SRE: reflect PagerDuty's four preset AI Agents (SRE/Scribe/Shift/Insights) and their
  extensibility model (preset connector list + prompt-style Skills, outward-facing MCP);
  contrast with the open-ended Agent loop (Skills/MCP/Subagents/A2A); concretize AI Actions
  allowances per plan
- Developer ecosystem: add a PagerDuty column (CLI status, official client libraries)
- SSO: compare protocols only
- Escape bare dollar signs that triggered LaTeX math rendering in tables
- Add an SVG cost-curve chart (zh/en) to the cost comparison example

Author: ysyneu

en/on-call/quickstart/comparison.mdx

@@ -118,7 +118,7 @@ Response solves "closing the loop quickly once the right person is found": a sin
 | --- | --- | --- |
 | **Basic Operations** | Manually create, acknowledge, close, comment on, snooze, merge, and bulk-assign incidents | ✅ Both support |
 | **Closure Automation** | Auto-close on timeout (countdown can be based on the last event time), auto-cancel snooze on timeout | ✅ Both support |
-| **[War Room](/en/on-call/advanced/war-room)** | One-click creation of a Feishu/Lark, Dingtalk, WeCom, or Slack group chat, automatically inviting responders, with a pinned incident card that updates in real time, and acknowledge/escalate/close actions in the chat syncing back to Flashduty | ✅ **Flashduty exclusive** (for China-region IM scenarios) |
+| **[War Room](/en/on-call/advanced/war-room)** | One-click creation of a Feishu/Lark, Dingtalk, WeCom, or Slack group chat (Teams not yet supported), automatically inviting responders, with a pinned incident card that updates in real time, and acknowledge/escalate/close actions in the chat syncing back to Flashduty | ✅ **Flashduty exclusive** |
 | **[Postmortems](/en/on-call/post-mortem/what-is-post-mortem)** | Full postmortem reports: timeline capture, collaborative editing, permission controls, with support for **[AI-generated postmortems](/en/on-call/post-mortem/ai-generate-post-mortem)** | Both support; Flashduty can generate a structured postmortem in one click from the incident timeline and alert data |
 | **Similar Incidents** | Identify and associate similar incidents | ✅ Both support |
 | **[Outlier Incidents](/en/on-call/incident/outlier-incidents)** | Automatic alerts for outlier incidents | ✅ **Flashduty exclusive** |
@@ -135,7 +135,7 @@ Communicating service status to the outside world is the last mile of incident m
 
 | Dimension | Flashduty | PagerDuty |
 | --- | --- | --- |
-| **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 |
+| **Availability** | [Status Page](/en/on-call/statuspage/statuspage) ships with the On-call product—public status pages are included starting from the free tier with **full feature parity across every tier**, and public + internal status pages are unified in one (internal status pages included from Professional up) | Each plan includes 1 public status page, **with features tiered by plan**; internal status pages require Business or above, and private status pages are a Premium add-on |
 | **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** |
 | **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 |
 | **Multilingual Notifications** | ✅ Natively preserves each subscriber's language preference | Not found in public materials |
@@ -150,23 +150,23 @@ If you're currently using Atlassian Statuspage, see our in-depth [Flashduty vs A
 
 ### AI SRE
 
-The two vendors take different approaches to AI: **PagerDuty splits AI across multiple products**—AIOps handles incident noise reduction and correlation (a separate add-on), Advance provides generative Q&A and summaries, and SRE Agent can autonomously analyze logs and metrics for diagnosis, though its remediation actions depend on pre-configured automation scripts. **Flashduty, beyond its built-in AI summaries and AI postmortems, also provides [AI SRE](/en/ai-sre): an autonomous SRE Agent connected to your real environment that dynamically calls tools and executes commands within a session—able to investigate problems it has never seen before**.
+The two vendors take different approaches to AI: **PagerDuty splits AI across multiple products and preset agents**—AIOps handles incident noise reduction and correlation (a separate add-on), Advance provides generative Q&A and summaries, and there are four purpose-built preset AI Agents (SRE for incident diagnosis, Scribe for meeting notes, Shift for schedule swaps, and Insights for data Q&A). **Flashduty, beyond its built-in AI summaries and AI postmortems, also provides [AI SRE](/en/ai-sre): a fully capable autonomous Agent loop connected to your real environment that dynamically calls tools and executes commands, extensible without limit through Skills, MCP, Subagents, and A2A—able to investigate problems it has never seen before**.
 
 | Dimension | Flashduty AI SRE | PagerDuty (AIOps / Advance / AI Agents) |
 | --- | --- | --- |
-| **Product Form** | Autonomous SRE Agent: conversational troubleshooting + autonomous planning and execution + knowledge accumulation | AIOps for incident noise reduction/correlation; Advance as a generative AI assistant (summaries, Q&A, postmortem drafts); SRE Agent for autonomous diagnosis |
+| **Product Form** | Autonomous SRE Agent: conversational troubleshooting + autonomous planning and execution + knowledge accumulation | AIOps for incident noise reduction/correlation; Advance as a generative AI assistant (summaries, Q&A, postmortem drafts); four preset AI Agents each own a slice: SRE (diagnosis + pre-configured remediation), Scribe (meeting notes), Shift (scheduling), Insights (data Q&A) |
 | **Troubleshooting & Remediation** | Cloud sandbox + self-hosted [Runner (BYOC)](/en/ai-sre/environments), dynamically executing diagnostic commands and querying monitoring data and logs within your environment—**able to investigate problems it has never seen before** | SRE Agent can automatically analyze logs/metrics and match them against historical incidents; remediation actions depend on **pre-configured** Automation Actions scripts |
 | **Native IM Collaboration** | [Group-chat @-mentions and private-chat troubleshooting](/en/ai-sre/im) across Feishu/Lark, Dingtalk, WeCom, and Slack, with **automatic initial diagnosis triggered once a war room is created** | Primarily Slack and Teams, no China-region IM support |
 | **Code Repositories & K8s** | [GitHub/GitLab App](/en/ai-sre/apps) accesses code repositories from within the sandbox and can submit PRs/MRs/Issues; a Kubernetes App connects to clusters at the namespace level | Not found in public materials |
 | **AI Automation Tasks** | [Automations](/en/ai-sre/automations) trigger on a cron schedule, via HTTP API, or on incident events, with built-in templates for alert noise analysis, incident postmortems, on-call insights, and more | Relies on the separate Event Orchestration and Runbook Automation product lines |
-| **Extensibility** | [Skills marketplace](/en/ai-sre/skills), [MCP external tools](/en/ai-sre/mcp), [Subagent and A2A delegation](/en/ai-sre/agents) | No equivalent extension system found in public materials |
+| **Extensibility** | [Skills marketplace](/en/ai-sre/skills), [MCP external tools](/en/ai-sre/mcp), [Subagent and A2A delegation](/en/ai-sre/agents), **with no ceiling on the extension surface** | SRE Agent is limited to toggling official preset connectors (about 23, e.g. Datadog, Splunk, CloudWatch) and appending prompt-style Skills; it doesn't support mounting arbitrary MCP tools to its own agents, has no subagent spawning, and cross-vendor agent collaboration is still in early access |
 | **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 |
 | **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 |
 | **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 |
-| **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 |
+| **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); each plan includes a one-time AI Actions allowance (Professional 1,000 / Business 5,000 / Enterprise 20,000), with SRE Agent queries and Scribe meetings metered per use—additional usage requires an add-on |
 
 <Note>
-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.
+PagerDuty's AIOps has been refined over many years for large-scale event correlation and is a mature capability; its MCP Server is built for third-party AI tools to query PagerDuty data, not to extend its own Agents' capabilities. 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 is a fully open-ended Agent loop that investigates and resolves dynamically within a session, while PagerDuty runs four preset Agents each covering a fixed scenario, with automated remediation depending on pre-configured scripts.
 </Note>
 
 ### Platform
@@ -218,7 +218,7 @@ Before reaching the team, alerts pass through routing, filtering, and transforma
 
 | Feature | Description | Comparison |
 | --- | --- | --- |
-| **Single Sign-On** | SSO protocol support | Flashduty: SAML, OIDC, CAS, LDAP, with support for **dedicated subdomain login**, plus setup guides for Authing, Keycloak, and OpenLDAP; PagerDuty: SAML, OAuth2 |
+| **Single Sign-On** | SSO protocol support | Flashduty: SAML, OIDC, CAS, LDAP; PagerDuty: SAML, OAuth2 |
 | **[Roles & Data Permissions](/en/platform/permission-design)** | Preset RBAC + custom roles, team-level data permissions | Flashduty supports custom roles and team-level data permissions; PagerDuty provides RBAC role management |
 | **Data Isolation** | Incident data isolated by team | ✅ Flashduty supports a **private access level** for collaboration spaces — incident data in a private space is visible only to team members and admins |
 | **[Custom Menu](/en/platform/custom-menu)** | Embed external links or iframe pages in the sidebar, visible based on role authorization | ✅ **Flashduty exclusive** |
@@ -227,13 +227,13 @@ Before reaching the team, alerts pass through routing, filtering, and transforma
 
 #### Developer Ecosystem
 
-| Tool | Flashduty | Notes |
+| Tool | Flashduty | PagerDuty |
 | --- | --- | --- |
-| **[Open API](/en/openapi/api-catalog)** | 290 endpoints: On-call 176, Monitors 36, RUM 18, AI SRE 33, Platform 27 | Both provide rich APIs; Flashduty opens its full endpoint set with bilingual documentation |
-| **[CLI](/en/developer/cli)** | 288 API operation commands + 10 built-in Agent Skills, ready to hand directly to AI coding tools like Claude Code, Cursor, and Codex | Lets AI coding tools operate the incident management platform directly |
-| **[Go SDK](/en/developer/go-sdk)** | go-github-style wrapper covering 288 API operations across 32 services | |
-| **[Terraform Provider](/en/developer/terraform)** | 12 resource types + 13 data source types, managing collaboration spaces, escalation policies, schedules, and more as IaC | Both support Terraform |
-| **[MCP Server](/en/developer/mcp-server)** | 8 tool sets with 23 tools, deployable remotely, via Docker, or from source | Both provide an official MCP Server |
+| **[Open API](/en/openapi/api-catalog)** | 290 endpoints covering On-call, Monitors, RUM, AI SRE, and platform management, with bilingual docs | ✅ Full-featured REST API, mature documentation |
+| **[CLI](/en/developer/cli)** | 288 API operation commands + built-in Agent Skills, ready to hand directly to AI coding tools like Claude Code, Cursor, and Codex | No official CLI actively promoted: the community's most-used `pagerduty-cli` is an employee's personal project (officially not endorsed, and the author has announced it's archived); the official go-pagerduty library ships a limited `pd` command-line tool |
+| **SDK** | [Go SDK](/en/developer/go-sdk): a go-github-style wrapper covering 288 API operations across 32 services | PagerDuty officially maintains go-pagerduty, python-pagerduty, and other client libraries |
+| **[Terraform Provider](/en/developer/terraform)** | 12 resource types + 13 data source types, managing collaboration spaces, escalation policies, schedules, and more as IaC | ✅ Official Terraform Provider, mature ecosystem |
+| **[MCP Server](/en/developer/mcp-server)** | 8 tool sets with 23 tools, deployable remotely, via Docker, or from source | ✅ Official MCP Server |
 
 ---
 
@@ -247,7 +247,7 @@ Pricing is a critical factor in enterprise decisions—you need to choose the mo
 | --- | --- | --- |
 | **Pricing Page** | [flashduty.com/pricing](https://www.flashduty.com/pricing) | [pagerduty.com/pricing](https://www.pagerduty.com/pricing/incident-response/) |
 | **Billing Model** | License fee + excess communication fees | Seat fee + Add-Ons |
-| **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 |
+| **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 |
 | **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 |
 | **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 |
 | **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 |
@@ -276,12 +276,14 @@ This is the most fundamental pricing difference between Flashduty and PagerDuty.
 
 ### Cost Comparison Example
 
+<img src="/images/oncall/comparison-cost-en.svg" alt="Estimated monthly cost: every seat vs active users only" />
+
 Take a 100-person engineering team where 15 people are routinely involved in incident handling as an example:
 
 | Cost Item | Flashduty Professional | PagerDuty Business |
 | --- | --- | --- |
 | Seats/Licenses required | **15** Licenses | **100** seats |
-| Monthly cost | 15 × ¥199 = **¥2,985/month** | 100 × $41 ≈ **¥29,500/month** |
+| Monthly cost | 15 × ¥199 = **¥2,985/month** | 100 × \$41 ≈ **¥29,500/month** |
 | Notification coverage | **100 people** (everyone can receive notifications) | **100 people** (but everyone must pay) |
 | Annual total cost | **~¥35,820** | **~¥354,000** |
 | **Savings** | — | **~90% savings** |