> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Pricing
> Learn about the pricing models and plans for Flashduty products
## On-call Pricing
***
On-call uses a **License subscription** model, billed by the number of active users.
### Pricing Model
Each License corresponds to one account member. Only members with a License can use all On-call features.
| Plan | Description | Use Case |
| ------------ | ------------------------------------ | ----------------------------------- |
| **Free** | Free forever with limited features | Personal use or small team trial |
| **Standard** | Complete basic features | Daily use for small to medium teams |
| **Pro** | All features + advanced capabilities | Enterprise production environments |
### Feature Comparison
| Feature | Free | Standard | Pro |
| -------------------------------------------------------- | :--: | :------: | :-: |
| **Single sign-on (SSO)** | ✅ | ✅ | ✅ |
| **Alert routing** | ✅ | ✅ | ✅ |
| **Incident collaboration** | ✅ | ✅ | ✅ |
| **Incident assignment** | ✅ | ✅ | ✅ |
| **Incident escalation** | ✅ | ✅ | ✅ |
| **Incident snooze** | ✅ | ✅ | ✅ |
| **Incident flapping detection** | ✅ | ✅ | ✅ |
| **Silence rules** | ✅ | ✅ | ✅ |
| **Usage dashboard** | ✅ | ✅ | ✅ |
| **Inhibit rules** | ❌ | ✅ | ✅ |
| **Alert grouping** | ❌ | ✅ | ✅ |
| **Pattern alert grouping** | ❌ | ✅ | ✅ |
| **Intelligent alert grouping** | ❌ | ❌ | ✅ |
| **Alert storm** | ❌ | ✅ | ✅ |
| **Insights dashboard** | ❌ | ✅ | ✅ |
| **Change integration** | ❌ | ✅ | ✅ |
| **Webhook integration** | ❌ | ✅ | ✅ |
| **Custom fields** | ❌ | ✅ | ✅ |
| **IM integration** (Lark, DingTalk, WeCom, Slack, Teams) | ❌ | ❌ | ✅ |
| **Service calendar** | ❌ | ❌ | ✅ |
| **Custom notification templates** | ❌ | ❌ | ✅ |
| **Custom schedule roles** | ❌ | ❌ | ✅ |
| **Advanced label enrichment** | ❌ | ❌ | ✅ |
| **Past incident history** | ❌ | ❌ | ✅ |
| **Outlier incident detection** | ❌ | ❌ | ✅ |
| **External incident creation** | ❌ | ❌ | ✅ |
| **Post-mortem** | ❌ | ❌ | ✅ |
| **Public status page** | ✅ | ✅ | ✅ |
| **Internal status page** | ❌ | ❌ | ✅ |
| **AI incident summary** | ❌ | ❌ | ✅ |
| **War room** | ❌ | ❌ | ✅ |
| **Ticketing integration** (Jira, ServiceNow) | ❌ | ❌ | ✅ |
For detailed feature comparison, also visit: [Pricing Page](https://flashcat.cloud/flashduty/price/)
### Resource Limits
| Resource | Free | Standard | Pro |
| --------------------- | ------------- | ------------- | --------- |
| Maximum users | 5 | Unlimited | Unlimited |
| Maximum schedules | 1 | Unlimited | Unlimited |
| Maximum channels | 1 | Unlimited | Unlimited |
| Daily alert limit | 100 | Unlimited | Unlimited |
| Public status pages | 1 | 1 | 5 |
| Internal status pages | Not available | Not available | 20 |
| Data retention | 30 days | 180 days | 360 days |
| Audit logs | Not available | 10 days | 30 days |
The Free plan accepts a maximum of 100 alerts per day. Alerts exceeding this limit are **silently dropped** with no error returned. Upgrade to Standard or Pro for unlimited alerts.
### Notification Quota
Each plan includes free notification quotas, calculated **per user per month**. Total quota = per-user allowance × number of Licenses.
| Channel | Free | Standard | Pro |
| ---------------------- | ------------------ | ----------------- | ------------------ |
| Free SMS | 10/user/month | 500/user/month | 1,000/user/month |
| Additional SMS | Notifications stop | ¥0.05/message | ¥0.05/message |
| Free voice calls | 10 min/user/month | 50 min/user/month | 100 min/user/month |
| Additional voice calls | Notifications stop | ¥0.12/minute | ¥0.12/minute |
| Free emails | 100/user/month | 2,000/user/month | 5,000/user/month |
| Additional emails | Notifications stop | ¥0.0018/email | ¥0.0018/email |
| Webhook | Unlimited | Unlimited | Unlimited |
On the Free plan, notifications **stop** once the quota is exhausted. On Standard and Pro plans, additional usage is billed on demand; notifications also stop if the account balance is insufficient.
### Customer Support
| Plan | Support Channel | Service Hours |
| -------- | ----------------------- | ------------- |
| Free | None | — |
| Standard | Email / Ticket | 5×8 hours |
| Pro | Dedicated support group | 7×8 hours |
### License Model Explained
Unlike products such as PagerDuty that charge for **every user**, Flashduty uses a **License (active user)** billing model—only members who need to **view and handle incidents** require a License. Other members can receive alert notifications at no additional cost.
#### Who Needs a License?
| Role | License Required? | Explanation |
| ------------------------- | :---------------: | ------------------------------------------------------------------------ |
| On-call engineers | ✅ | Need to view incident details, acknowledge, and handle incidents |
| Team leads | ✅ | Need to view incidents, configure escalation rules and schedules |
| Notified developers / ops | ❌ | Only need to passively receive notifications, no platform login required |
| Management | ❌ | Can monitor overall status via analytics dashboards or status pages |
| External collaborators | ❌ | Get information through webhooks, email, or status pages |
**Cost advantage for large teams**: In practice, a 100-person engineering team typically has only 10–20 people who actively handle incidents day-to-day. The rest only need to receive notifications when relevant incidents occur. This means you may only need 10–20 Licenses instead of paying for all 100 people—**reducing costs by 80%–90%**.
#### Why the License Model?
Traditional per-user pricing (like PagerDuty) requires purchasing a seat for every user who receives notifications, which creates two problems in practice:
1. **Wasted spend**: Most team members only need to receive notifications when incidents occur—they never log in to view or handle incidents—yet each still requires a full-price seat
2. **Insufficient notification coverage**: To control costs, organizations often limit who receives notifications, causing critical information to miss key stakeholders
Flashduty's License model decouples **incident handling capability** from **notification delivery**:
* **Members with a License**: Full permissions to view, handle, and configure incidents
* **Members without a License**: Can passively receive all alert notifications (email, SMS, voice call, IM), share the tenant's notification quota, ensuring information reaches everyone who needs it
This approach ensures comprehensive notification coverage while significantly reducing total cost of ownership.
#### License Types
* **Permanently valid** within the purchase period
* **Cannot be preempted**
* **Administrators** can grant fixed Licenses to members
* Suitable for members who need to handle incidents and configure business settings
* **Permanently valid** within the purchase period
* **Automatically released** at the end of each cycle
* **Administrators** can grant temporary Licenses to members
* Can be occupied through assignment or preemption when sufficient Licenses are available
* Suitable for members who participate temporarily or use occasionally
#### Permissions for Members Without License
Members without a License have limited functionality and can only passively receive alert messages.
| Capability | Description |
| ------------------------- | ------------------------------------------------------------------- |
| View incidents | ❌ Cannot view incident list/details |
| Handle incidents | ❌ Cannot acknowledge, close, or perform other operations |
| Receive notifications | ✅ Can passively receive alert messages (email, SMS, voice call, IM) |
| Escalation rule reference | ✅ Can be added as notification targets in escalation rules |
| Notification quota | ✅ Shares the tenant's email, SMS, and phone call quota |
***
## RUM Pricing
***
RUM uses a **pay-as-you-go** model, billed by the number of sessions used.
### Plan Comparison
**¥0** / Free forever
For testing and evaluation
**Pay-as-you-go**
For production environments, all application types
### Features and Pricing Details
| Feature | Free | Pro |
| ----------------------------------------------------- | ------------------- | ------------------------------ |
| **Session Analysis** (views, resources, errors, etc.) | 1,000/month per app | Unlimited, ¥9.0 / 1K sessions |
| **Session Replay** (user behavior recording) | 500/month per app | Unlimited, ¥12.0 / 1K sessions |
| **Web Performance Monitoring** | ❌ | ✅ |
| **AI Error Tracking** | ❌ | ✅ |
| **Advanced Dashboards** | ❌ | ✅ |
| **Frontend-Backend Correlation** (Tracing) | ❌ | ✅ |
### Data Retention
| Data Type | Free | Pro |
| ----------------------------------- | ------- | ------- |
| Sessions / Views / Errors / Actions | 30 days | 30 days |
| Resources / Long Tasks | 15 days | 15 days |
The Free plan is suitable for evaluating product features. The Pro plan is billed based on actual usage with no large upfront costs.
***
## FAQ
***
Members who use commercial features (viewing or handling incidents) within the month are counted as active users. **Receiving alert notifications alone does not count as active usage.** At the end of each monthly cycle:
* Fixed Licenses remain valid
* Temporary Licenses are automatically released
* When a member is deleted, their License is automatically released
Only members who need to **log in to the platform to view incident details, acknowledge, and handle incidents** require a License. Members who only receive alert notifications do not need one.
**How to estimate**: Count the core personnel in your team who participate in daily on-call and incident response, typically:
* Frontline on-call engineers
* Team leads involved in incident handling
* Administrators who configure escalation rules and schedules on the platform
**Real-world example**: For a 100-person engineering team, typically only 10–20 people need to log in and handle incidents daily. The remaining 80–90 people only need to receive notifications when relevant incidents occur. Therefore, you only need 10–20 Licenses, **saving 80%–90% compared to paying for every team member**.
* **Can**: Passively receive alert messages (email, SMS, voice call, IM), be referenced as notification targets in escalation rules, share tenant notification quota
* **Cannot**: View/handle incidents, perform any platform configuration operations
In escalation rules, you can choose to notify members without a License about incidents, but they cannot perform any operations on the incident. This means you can include your entire team in the notification scope without purchasing a License for every person.
* **Session Analysis**: Each complete session of a user visiting the application, including page views, resource loads, errors, etc.
* **Session Replay**: Sessions that record user behavior for replaying user interactions
Both are billed independently based on the actual number of sessions generated.
Yes. Flashduty offers an **On-Premises** edition with all Pro features, plus:
* Local data storage
* Internal system integration
* No public network dependency
Private deployment has higher maintenance costs and a different pricing model than SaaS. Unless you have specific requirements, we recommend using the cloud service.
Please contact us for On-Premises pricing.
Yes. The On-call Pro plan offers a free trial with full access to all Pro features. Contact our sales team to request a trial.
***
## Contact Sales
***
For more pricing details or enterprise quotes, please contact our sales team.
📧 [contact-us@flashcat.cloud](mailto:contact-us@flashcat.cloud)\
📞 010-53675832