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.
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.
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
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. 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.
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 monitoring, 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.
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.
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.
status.sakneen.com, running on InBrief in production.
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.
Originally published on Medium.
Top comments (0)