Why our status page costs $1 a month

为什么我们的状态页面每月只需 1 美元

The full InBrief price list, and why incident communication is sold per feature instead of per tier. Every status page tool I have used is sold the same way. A free tier that is missing the one thing you need. A middle tier that costs more than the product you are monitoring. An enterprise tier behind a “contact us” button. You pay for a bundle so that you can use two things in it.

这是 InBrief 的完整价目表，以及为什么我们将事故沟通服务按功能而非按套餐进行销售的原因。我使用过的每一个状态页面工具，销售模式都如出一辙：免费套餐总是缺少你最需要的那一个功能；中端套餐的价格比你正在监控的产品本身还要贵；企业级套餐则隐藏在“联系我们”的按钮之后。你为了使用其中的两项功能，不得不为整个捆绑包买单。

I run a status page for a real product, status.sakneen.com, and I built InBrief because I wanted to pay for what I actually use. So InBrief is priced per feature. Here is the whole list. Nothing is behind a sales call.

我为一个真实的产品（status.sakneen.com）运营着一个状态页面，我开发 InBrief 是因为我想为我实际使用的功能付费。因此，InBrief 采用按功能定价的模式。以下是完整列表，没有任何功能需要通过销售电话咨询。

The price list 价目表

• Public status page: $1 a month

• Incident management: $3

• Monitoring and automatic detection: $3

• Outage continuity: $3

• Branding and a custom domain: $2

• Subscriber updates by email, Discord, Microsoft Teams, Telegram and browser push: $2

• Multilingual status pages in English, Arabic, French and Spanish: $2

• Team roles: $2

• Status page analytics: $2

• Outbound webhooks: $1

• Badges, feeds and embeds: $1

• Slack alerts for your responders: $1

• 公共状态页面：每月 1 美元

• 事故管理：3 美元

• 监控与自动检测：3 美元

• 宕机持续性保障：3 美元

• 品牌定制与自定义域名：2 美元

• 通过电子邮件、Discord、Microsoft Teams、Telegram 和浏览器推送进行订阅者更新：2 美元

• 支持英语、阿拉伯语、法语和西班牙语的多语言状态页面：2 美元

• 团队角色：2 美元

• 状态页面分析：2 美元

• 出站 Webhooks：1 美元

• 徽章、订阅源与嵌入：1 美元

• 针对响应人员的 Slack 提醒：1 美元

Add what you need and drop it when you stop needing it. A status page with incident management and email subscribers is $6 a month. If you would rather not think about it, there are two bundles. Start is $10 for one page with the nine features a single product needs, which would be $16 bought separately. Pro is $20 for three pages with everything above plus a write API and an audit log, which would be $27 separately. A bundle is always cheaper than its parts, so nobody is punished for taking the easy option.

按需添加，不再需要时即可取消。一个包含事故管理和电子邮件订阅功能的状态页面每月仅需 6 美元。如果你不想费心挑选，我们还提供了两个捆绑套餐。Start 套餐每月 10 美元，包含单个产品所需的 9 项功能（如果单独购买则需 16 美元）。Pro 套餐每月 20 美元，包含上述所有功能，外加写入 API 和审计日志（如果单独购买则需 27 美元）。捆绑套餐总是比单独购买更便宜，因此选择省心方案的用户不会受到“惩罚”。

There is a free plan to start with, and the plan builder shows the price of any combination before you sign up. The plan builder at inbrief.sh/build. A bundle is always cheaper than its parts.

我们提供免费入门计划，且在注册前，套餐构建器会显示任何组合的价格。套餐构建器地址：inbrief.sh/build。捆绑套餐永远比单独购买更划算。

What per-feature pricing changes 按功能定价带来的改变

Two things. First, the product has to earn each dollar on its own. If monitoring is not worth $3 to you, you do not buy it, and I find out. A tier hides which features people actually value. A price list does not. Second, the upgrade moment is yours. You add a capability when you want it, not when you hit a wall that was placed in your way.

主要有两点改变。首先，产品必须靠自身价值赚取每一美元。如果监控功能对你来说不值 3 美元，你就不会购买，我也会因此获知反馈。套餐制会掩盖用户真正看重的功能，而价目表则不会。其次，升级的主动权在你手中。你可以在需要时添加功能，而不是在遇到人为设置的障碍时才被迫升级。

The part that matters more than the price 比价格更重要的部分

A status page is worth nothing on the day your site is down if the status page goes down with it. InBrief’s outage continuity is a separate page, served independently of your main site, that visitors see when your site cannot answer. It is the feature I would keep if I could keep only one, and it costs $3.

如果你的网站宕机时状态页面也随之瘫痪，那么这个状态页面就毫无意义。InBrief 的“宕机持续性保障”是一个独立页面，与你的主站分开托管，当你的网站无法响应时，访客依然能看到它。如果我只能保留一个功能，那一定是这个，它的价格是 3 美元。

The other thing I insisted on is that one incident update reaches everyone. You write it once. It goes to the status page, to email, to RSS, to every chat channel you connected, and into every language you publish. Writing the same update four times during an outage is how updates stop being written.

我坚持的另一件事是：一次事故更新必须触达所有人。你只需写一次，它就会自动同步到状态页面、电子邮件、RSS、你连接的所有聊天频道，以及你发布的所有语言版本中。在宕机期间重复写四次同样的更新，只会导致更新工作最终被放弃。

Who this is for 适用人群

Small teams and solo founders who run something people depend on, and who are tired of choosing between a free page that embarrasses them and a plan built for a company of two hundred. If that is you, build a plan at inbrief.sh/build and see the number before you sign up. If you are comparing against a tool you already use, there is a page for each of the common ones at inbrief.sh/alternatives. Each one lists what InBrief does and costs, and makes no claims about the other tool. You know it better than I do.

适用于那些运营着人们所依赖的产品、且厌倦了在“令人尴尬的免费页面”与“为两百人规模公司设计的昂贵套餐”之间做选择的小型团队和独立开发者。如果你是这样的人，请前往 inbrief.sh/build 构建你的套餐，在注册前查看价格。如果你正在与现有的工具进行对比，可以在 inbrief.sh/alternatives 查看常见竞品的对比页面。每个页面都列出了 InBrief 的功能和价格，且不对其他工具做任何评价。毕竟，你比我更了解它们。