Skip to content

Commit 382698f

Browse files
debidongdebidong
authored
docs: add Flashduty vs Atlassian Statuspage comparison (#57)
* docs: add Flashduty vs Atlassian Statuspage comparison article Add bilingual (zh + en) comparison article covering features, pricing, and migration compatibility. Claims verified against both products' official documentation. * docs: restructure statuspage comparison to emphasize features, pricing, and migration - Remove generic "procurement guide" section - Restructure feature comparison tables for direct side-by-side readability - Add concrete cost comparison example (Flashduty $0 vs Atlassian $4,800-8,400+/yr) - Replace migration comparison tab with simple 4-step migration guide - Replace generic Q&A summary with focused 3-pillar summary cards * docs: add third-party rationale and Flashduty reliability sections - Add "Why choose a third-party status page" section explaining risks of self-built pages (shared infrastructure, maintenance burden) - Add "Flashduty reliability" section with concrete SLA data: 99.9% availability, multi-datacenter active-active, multi-vendor failover, 10x SLA breach compensation - Link to existing SLA compliance docs for full details * docs: add dedicated Atlassian Statuspage migration guide - Create bilingual migration guide with CLI commands, flags, phases, and complete workflow example - Cover two-step process: structure migration (no notifications) then subscriber migration (triggers verification emails) - Include prerequisites (CLI install, auth, API key, page ID) - Add domain switch and RSS/Atom compatibility instructions - Update comparison article migration section to link to new guide - Register new pages in docs.json navigation * fix: replace Go Install with Manual Download in migration guide Go install is no longer supported by flashduty-cli. Replace with Manual Download tab matching the official README. * fix: remove Go Install option from CLI docs Go install is no longer supported by flashduty-cli per the official README. Only macOS/Linux, Windows, and Manual Download remain.
1 parent a9bc980 commit 382698f

7 files changed

Lines changed: 924 additions & 18 deletions

File tree

‎docs.json‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,9 @@
141141
"zh/on-call/statuspage/components-sections",
142142
"zh/on-call/statuspage/publish-events",
143143
"zh/on-call/statuspage/templates",
144-
"zh/on-call/statuspage/subscriptions"
144+
"zh/on-call/statuspage/subscriptions",
145+
"zh/on-call/statuspage/migrate-from-atlassian",
146+
"zh/on-call/statuspage/comparison"
145147
]
146148
},
147149
{
@@ -1093,7 +1095,9 @@
10931095
"en/on-call/statuspage/components-sections",
10941096
"en/on-call/statuspage/publish-events",
10951097
"en/on-call/statuspage/templates",
1096-
"en/on-call/statuspage/subscriptions"
1098+
"en/on-call/statuspage/subscriptions",
1099+
"en/on-call/statuspage/migrate-from-atlassian",
1100+
"en/on-call/statuspage/comparison"
10971101
]
10981102
},
10991103
{

‎en/developer/cli.mdx‎

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,6 @@ irm https://raw.githubusercontent.com/flashcatcloud/flashduty-cli/main/install.p
2929
Installs to `~\.flashduty\bin` by default. Override with the `FLASHDUTY_INSTALL_DIR` environment variable.
3030
</Tab>
3131

32-
<Tab title="Go Install">
33-
```bash
34-
go install github.com/flashcatcloud/flashduty-cli/cmd/flashduty@latest
35-
```
36-
37-
Make sure `$(go env GOPATH)/bin` is on your `PATH`.
38-
</Tab>
39-
4032
<Tab title="Manual download">
4133
Grab the binary for your platform from [GitHub Releases](https://github.com/flashcatcloud/flashduty-cli/releases), extract it, and place it on your `PATH`.
4234
</Tab>

‎en/on-call/statuspage/comparison.mdx‎

Lines changed: 233 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,233 @@
1+
---
2+
title: "Status Page Comparison"
3+
description: "In-depth comparison of Flashduty Status Page vs Atlassian Statuspage: more features, lower price, easier migration"
4+
---
5+
6+
## Introduction
7+
8+
---
9+
10+
A **status page** is a critical bridge for building service transparency and trust between businesses and their users. When service disruptions or planned maintenance occur, a clear, timely, and subscribable status page significantly reduces customer anxiety, cuts down on support tickets, and demonstrates professional incident communication.
11+
12+
Flashduty Status Page and Atlassian Statuspage are two leading status page products, but they have a **fundamentally different positioning**:
13+
14+
<CardGroup cols={2}>
15+
<Card title="Flashduty Status Page" icon="puzzle-piece">
16+
Part of the incident response system -- status pages, subscriptions, incidents, maintenance, historical statistics, and internal notifications tightly integrated, **included in the On-call module at no extra cost**
17+
</Card>
18+
<Card title="Atlassian Statuspage" icon="browser">
19+
A standalone status communication page -- feature-rich but **billed as a separate product**, with full capabilities requiring higher-tier plans
20+
</Card>
21+
</CardGroup>
22+
23+
---
24+
25+
## Why Choose a Third-Party Status Page?
26+
27+
---
28+
29+
Before evaluating specific products, there's a more fundamental question to answer: **should you build your own status page or use a third-party service?**
30+
31+
<AccordionGroup>
32+
<Accordion title="The risks of building your own" icon="triangle-exclamation">
33+
The biggest problem with a self-built status page is that it **shares infrastructure with your business services**. When your services go down, your self-built status page is likely to go down with them -- precisely when you need it most.
34+
35+
Additionally, building your own means:
36+
- Implementing subscription notifications, email delivery, and availability statistics from scratch
37+
- Ongoing engineering effort for maintenance and iteration
38+
- Difficulty ensuring email deliverability and notification timeliness
39+
</Accordion>
40+
<Accordion title="The advantages of a third-party service" icon="shield-check">
41+
A professional third-party status page runs on **infrastructure independent from your business**, ensuring it stays up even when your services are down. This is the core value of a status page -- **remaining available during outages**.
42+
43+
Third-party services also provide:
44+
- Out-of-the-box subscription management, push notifications, and availability statistics
45+
- Professional email delivery infrastructure and multi-channel notifications
46+
- Continuous feature iteration with no maintenance burden on your team
47+
</Accordion>
48+
</AccordionGroup>
49+
50+
---
51+
52+
## Product Feature Comparison
53+
54+
---
55+
56+
### Status Page Types
57+
58+
| Core Capability | Flashduty | Atlassian Statuspage |
59+
| --- | --- | --- |
60+
| **Public Status Page** | ✅ Supported | ✅ Supported |
61+
| **Internal Status Page** | ✅ Built-in with IM channel notifications | Private and Audience-specific pages billed under separate models; Audience-specific is a separate product line |
62+
| **Unified Management** | ✅ Single product | ❌ Different page types billed and managed separately |
63+
64+
### Detailed Feature Comparison
65+
66+
<Tabs>
67+
<Tab title="Incident Management">
68+
| Feature | Flashduty | Atlassian Statuspage |
69+
| --- | --- | --- |
70+
| **Incident Publishing** | ✅ Create incidents, update timelines, notify subscribers | ✅ Supported |
71+
| **Maintenance Events** | ✅ Schedule start/end times with auto-progression and manual override; **maintenance excluded from uptime calculation**, ideal for separating outages from planned maintenance | ❌ Not supported |
72+
| **Backfill Incidents** | ✅ Backfill incidents included in event history and availability statistics, with impact periods calculated from component status changes in the timeline -- **complete closed loop for historical records and availability tracking** | ✅ Supports backfill incidents, but with limited integration between backfill and availability statistics |
73+
| **Incident Templates** | ✅ Supported | ✅ Supported |
74+
| **Component Status Linking** | ✅ Supported | ✅ Supported |
75+
</Tab>
76+
77+
<Tab title="Subscription Management">
78+
| Feature | Flashduty | Atlassian Statuspage |
79+
| --- | --- | --- |
80+
| **Full Subscription** | ✅ Supported | ✅ Supported |
81+
| **Component Subscription** | ✅ **Available in all editions** | Business and above only |
82+
| **Incident Subscription** | ✅ Subscribe to updates for a specific incident | ❌ Not supported |
83+
| **Bulk Import/Export** | ✅ Admins can bulk import and export subscribers | ❌ Not supported |
84+
| **Self-service Management** | ✅ Subscribers manage their own scope or unsubscribe via management tokens | Limited self-service capabilities |
85+
86+
<Tip>
87+
Flashduty offers finer-grained subscription management: full, component, and incident-level subscriptions all included, with no plan-tier restrictions.
88+
</Tip>
89+
</Tab>
90+
91+
<Tab title="Display & Customization">
92+
| Feature | Flashduty | Atlassian Statuspage |
93+
| --- | --- | --- |
94+
| **Custom Domain** | ✅ Supported | ✅ Supported (paid plans) |
95+
| **Incident History View** | ✅ **Calendar view + list view** | List view |
96+
| **Availability Display** | ✅ Configurable as **chart with percentage, chart only, or hidden** | Fixed display mode |
97+
| **Branding** | ✅ Logo, dark mode logo, header/footer, custom links and contact info | ✅ Logo, page settings |
98+
| **Component Grouping** | ✅ Supported | ✅ Supported (Business and above) |
99+
| **Component Display Control** | ✅ Hide availability or fully hide components -- **express real service structure while controlling external exposure** | ❌ Not supported |
100+
</Tab>
101+
102+
<Tab title="Notification Channels">
103+
| Method | Flashduty | Atlassian Statuspage |
104+
| --- | --- | --- |
105+
| **Email** | ✅ Supported | ✅ Supported |
106+
| **SMS** | Covered via IM channels | ✅ Supported, but with limited triggers -- intermediate updates do not send SMS |
107+
| **Webhook** | ✅ Supported | ✅ Supported |
108+
| **Feishu/Lark** | ✅ Supported | ❌ Not supported |
109+
| **Dingtalk** | ✅ Supported | ❌ Not supported |
110+
| **WeCom** | ✅ Supported | ❌ Not supported |
111+
| **Slack** | ✅ Supported | ✅ Supported |
112+
| **RSS/Atom** | ✅ Supported, compatible with Atlassian history.rss / history.atom link format | ✅ Supported |
113+
| **Multi-language Notifications** | ✅ Natively preserves language preferences | Relies on third-party integration (Localize) |
114+
115+
<Tip>
116+
Flashduty offers notification channels better suited for enterprise collaboration, with native support for Feishu/Lark, Dingtalk, WeCom, and Slack.
117+
</Tip>
118+
</Tab>
119+
</Tabs>
120+
121+
---
122+
123+
## Pricing Comparison
124+
125+
---
126+
127+
Atlassian Statuspage is billed as a standalone product, with pricing increasing across tiers based on subscribers, components, team members, and more. Flashduty Status Page is **included in the On-call module at no extra cost**.
128+
129+
| Dimension | Flashduty Status Page | Atlassian Statuspage |
130+
| --- | --- | --- |
131+
| **Pricing Page** | [flashcat.cloud/flashduty/price](https://flashcat.cloud/flashduty/price/) | [atlassian.com/statuspage/pricing](https://www.atlassian.com/software/statuspage/pricing) |
132+
| **Billing Model** | **Included in the On-call module**, not sold separately | Standalone product, tiered across multiple dimensions |
133+
| **Traffic Limits** | ✅ **Unlimited** | Limited by plan |
134+
| **Public Page** | ✅ Included | Tiered by subscribers, components, team members, and metrics |
135+
| **Private Page** | ✅ Included | Tiered by authenticated subscribers |
136+
| **Audience-specific** | ✅ Included | **Separate product line, starting at $300/month** |
137+
| **Component Subscription** | ✅ All editions | Business and above only |
138+
| **Component Grouping** | ✅ All editions | Business and above only |
139+
140+
### Cost Comparison Example
141+
142+
For a typical scenario requiring a public status page + internal status page, 1,000 subscribers, and 10 components:
143+
144+
| Cost Item | Flashduty | Atlassian Statuspage |
145+
| --- | --- | --- |
146+
| **Public Status Page** | Included in On-call | Startup plan from $99/month; 1,000 subscribers requires Business plan |
147+
| **Internal Status Page** | Included in On-call | Audience-specific is a separate product, starting at $300/month |
148+
| **Annual Status Page Cost** | **$0 (additional)** | **~$4,800–$8,400+/year** (Public Business + Audience-specific) |
149+
150+
<Note>
151+
The additional cost of Flashduty Status Page is zero -- it's a built-in capability of your On-call subscription. If you're already using Flashduty On-call for incident management, the status page is **ready to use out of the box**.
152+
</Note>
153+
154+
---
155+
156+
## Flashduty Status Page Reliability
157+
158+
---
159+
160+
As a third-party status page service, Flashduty's own reliability is paramount -- you need confidence that when your services go down, the status page stays up.
161+
162+
<CardGroup cols={2}>
163+
<Card title="Infrastructure" icon="server">
164+
- **Multi-datacenter active-active**: built on multiple data centers with all stateful components running in active-active mode
165+
- **Auto-scaling**: supports rapid automatic scaling to handle traffic spikes
166+
- **Global acceleration**: api.flashcat.cloud enabled with global acceleration for stable access from all regions
167+
</Card>
168+
<Card title="Notification Delivery" icon="paper-plane">
169+
- **Multi-vendor redundancy**: voice, SMS, and email backed by multiple cloud vendors with rapid failover
170+
- **IM automatic fallback**: failed IM messages automatically fall back to SMS and email
171+
- **High email deliverability**: professional email infrastructure ensuring subscribers receive timely status updates
172+
</Card>
173+
</CardGroup>
174+
175+
| Guarantee | Commitment |
176+
| --- | --- |
177+
| **Feature Availability SLA** | **99.9%** |
178+
| **Alert Delivery SLA** | **99.9%** of alerts delivered within 5 minutes |
179+
| **SLA Compensation** | Breached period x per-minute fee x **10x compensation** |
180+
| **Continuous Monitoring** | Comprehensive system metrics collection + regular stress testing |
181+
182+
<Note>
183+
See the [Service Level Agreement (SLA)](/en/compliance/service-sla) for full availability commitments and compensation details.
184+
</Note>
185+
186+
---
187+
188+
## Migrating from Atlassian Statuspage
189+
190+
---
191+
192+
Flashduty CLI supports one-click migration of components, sections, incident history, and email subscribers from Atlassian Statuspage, with `history.rss` and `history.atom` link format compatibility so existing RSS/Atom subscribers need no changes.
193+
194+
<Steps>
195+
<Step title="Migrate structure and history">
196+
Use `flashduty statuspage migrate structure` to automatically import components, sections, historical incidents, and notification templates -- this step does not notify subscribers
197+
</Step>
198+
<Step title="Verify imported content">
199+
Check the imported components, sections, and incident history in the Flashduty Console
200+
</Step>
201+
<Step title="Migrate email subscribers">
202+
Use `flashduty statuspage migrate email-subscribers` to import subscribers -- this step triggers verification emails
203+
</Step>
204+
<Step title="Switch domain and go live">
205+
Point your custom domain CNAME to Flashduty, confirm everything works, and go live
206+
</Step>
207+
</Steps>
208+
209+
<Tip>
210+
For detailed command flags and a complete migration walkthrough, see the [Migrate from Atlassian Statuspage guide](/en/on-call/statuspage/migrate-from-atlassian).
211+
</Tip>
212+
213+
---
214+
215+
## Summary
216+
217+
---
218+
219+
<CardGroup cols={3}>
220+
<Card title="More Comprehensive Features" icon="layer-group">
221+
Maintenance events, incident subscriptions, component display controls, bulk import/export, native IM notifications, and more **exclusive capabilities** -- with no plan-tier restrictions
222+
</Card>
223+
<Card title="Dramatically Lower Price" icon="piggy-bank">
224+
Status page included in the On-call module, **no separate purchase needed**. Compared to Atlassian Statuspage's thousands of dollars per year in standalone fees, the additional cost is zero
225+
</Card>
226+
<Card title="Simpler Migration" icon="arrow-right-arrow-left">
227+
Flashduty CLI completes component, incident, and subscriber migration in one click, with RSS/Atom link format compatibility -- **zero-friction switch**
228+
</Card>
229+
</CardGroup>
230+
231+
<Tip>
232+
If you're already using or planning to use Flashduty On-call, the status page is available as a built-in capability -- no extra investment, no separate purchase, ready out of the box. [Start your free trial now](https://console.flashcat.cloud/).
233+
</Tip>

0 commit comments

Comments
 (0)