Skip to content

docs: explain License billing model and PagerDuty cost comparison#32

Merged
ysyneu merged 4 commits intomainfrom
doc-review/2026-03-26-feature-matrix
Mar 26, 2026
Merged

docs: explain License billing model and PagerDuty cost comparison#32
ysyneu merged 4 commits intomainfrom
doc-review/2026-03-26-feature-matrix

Conversation

@ysyneu
Copy link
Copy Markdown
Contributor

@ysyneu ysyneu commented Mar 26, 2026

Summary

  • Pricing pages (zh + en): Added comprehensive "License Model Explained" section covering who needs a License, why the model exists, role-based table, and real-world cost savings example (100-person team, 10-20 Licenses, 80-90% savings)
  • Pricing FAQ: Added new "How many Licenses does my team need?" FAQ with estimation guide and concrete example
  • Comparison pages (zh + en): Expanded pricing comparison with side-by-side billing model analysis (PagerDuty full-seat vs Flashduty License), concrete cost comparison table, and tabbed model explanation
  • Enhanced existing FAQ and permissions tables with more detail (IM channels, escalation rule references)

Context

Many customers ask about the "active user / License" concept — this is a key differentiator from PagerDuty's per-seat model. The documentation now clearly explains what it is, why it works this way, and demonstrates the cost advantage with real numbers.

Test plan

  • Verify pricing pages render correctly in both zh and en
  • Verify comparison pages render correctly
  • Check internal links between pricing and comparison pages work
  • Run mint broken-links to validate

🤖 Generated with Claude Code

ysyneu and others added 4 commits March 26, 2026 11:47
…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>
Pattern alert grouping (规则告警分组) is Standard+ while Intelligent alert
grouping (智能告警分组) is Pro-only. These are two distinct features gated
separately in fc-event, not a single combined feature.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The correct Chinese term is 告警聚合 (aggregation), not 告警分组 (grouping).
Added 规则告警聚合/智能告警聚合 terminology to both the glossary and CLAUDE.md.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The codebase consistently uses "grouping" (pattern alert grouping,
intelligent alert grouping, alert_grouping_time_window). Updated pricing
page, glossary, and CLAUDE.md terminology.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ysyneu ysyneu merged commit 7f394a6 into main Mar 26, 2026
1 check passed
@ysyneu ysyneu deleted the doc-review/2026-03-26-feature-matrix branch March 26, 2026 03:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant