Atlassian Statuspage alternative · pay once
Status page,paid once
DurianStatus gives your service a public status page with incidents, maintenance, uptime checks and email updates for subscribers, paid once, an alternative to Atlassian Statuspage.
Add a URL, DurianStatus checks it every 5 minutes and tells your users when something breaks. Nothing to install, no monthly bill.
DurianStatus is one of 8 apps you pay for once. Get all of them: $49 once.
Tell people before they ask,without renting a status page
A public status page
Your name, description, website link and brand color. One clear banner on top: all systems operational, or what isn't.
Components
Website, API, app, emails: each with its own status, from operational to major outage, set by hand or by a check.
Uptime checks every 5 minutes
An HTTP GET or HEAD on the URL you choose, with a 10-second timeout. Nothing to install on your servers.
Incidents open themselves
After 3 failed checks in a row an incident opens, and it resolves when the check recovers.
Confirmed from a second region
Before an incident opens, a second region checks the site. Down there too: incident. Up there: treated as a network problem on our side, not counted as downtime.
Incidents and maintenance
Post updates as you go (investigating, identified, monitoring, resolved) and schedule maintenance windows ahead.
Slack, Discord and Teams alerts
Paste an incoming-webhook URL (Teams: a Workflows URL): incidents, maintenance and component changes are posted to your channel. Up to 5 destinations per status page.
Signed webhooks
A JSON POST to your URL for every incident, maintenance or component change, signed with HMAC-SHA256 and retried for up to 2 hours.
Your status page on your domain
Pro: serve it on status.yoursite.com. Add the domain, publish the TXT proof and the record shown, verify.
No DurianStatus branding
Pro: hide "Powered by DurianStatus" on your page and in incident emails.
Private status pages
Pro: protect a page with a password (at least 10 characters). Visitors without it see a sign-in gate; the widget and the JSON feed are closed.
Email subscribers
Visitors subscribe with double opt-in and hear about incidents, updates and resolutions. One click to unsubscribe.
90 days of uptime
One bar per day per monitored component with its uptime percentage, and the last 14 days of incidents on the page.
Badge, widget and JSON
A README badge, a small status widget for your site (script or iframe) and a public JSON endpoint.
The math,no fine print
Atlassian Statuspage Hobby costs $348 a year ($29 a month, monthly billing only, their pricing page, checked October 10, 2026). DurianStatus costs $39, once. We're not everything Atlassian Statuspage is, so here's what we don't do:
- SMS alerts
- Continuous checks from several regions (a second region only confirms failures)
- Per-user logins or SSO for private pages
Atlassian Statuspage, year 1
$348
Atlassian Statuspage, year 3
$1,044
DurianStatus, once
$39
paid once · $0 monthly
Stop paying monthlyfor your status page
DurianStatus
$39 once
Everything above, one payment, future updates included.
Several products or clients? Pro covers unlimited status pages and 25 monitors.
No renewal · 14-day refund · or all 8 apps in the bundle
Will this disappear?
Fair question for a one-time product. Here is what you can check, and what we commit to.
30 days' notice
If we ever shut an app down, you get at least 30 days' notice by email and can export your data.
Read the termsQuestions
What does one-time mean?
You pay once and use DurianStatus for as long as we operate it, with updates. If we ever shut it down, you get 30 days' notice and an export of your data.
Can I get a refund?
Yes, within 14 days of purchase, in full.
How do the uptime checks work?
Every 5 minutes, from one region, DurianStatus requests the URL of each monitor (GET or HEAD, 10-second timeout). A failed check counts as downtime. After 3 failed checks in a row, a second region checks the URL: if it is down there too, DurianStatus opens an incident; if it is up there, those failed checks are treated as a network problem on our side, are not counted as downtime, and no incident opens. You can always edit or resolve an incident by hand.
What are the limits?
Solo: 1 status page, 5 monitors, 500 email subscribers. Pro: unlimited status pages, 25 monitors in total and 2,000 email subscribers. Incident emails to subscribers (incidents, maintenance, updates; one per recipient) are limited per status page and calendar month: 2,000 on Solo, 10,000 on Pro. If what is left can't reach every confirmed subscriber, that update isn't emailed (never half your list) until the next month; your status page, Slack, Discord and webhooks keep working, and you get an email at 80% and when it runs out. Confirmation emails don't count.
