Uptime monitoring by SoftDoes

Know your sites are downbefore your customers do

Checks as often as every minute, outages confirmed on the second failed check, an alert by email, Slack, Teams or Telegram, and a status page with your logo on it.

Heedery / Workspace overview

A preview of the workspace overview: twelve monitored sites, one of them down with an open incident.

  • 60sec

    Between checks

    As often as once a minute.

  • 2checks

    To confirm an outage

    A second failure confirms it.

  • 90days

    Of uptime history

    See the pattern over time.

  • 7channels

    For alerts

    Reach the people who respond.

    • Email
    • Slack
    • Microsoft Teams
    • Discord
    • Telegram
    • Webhook
    • Phone push

One workspace. Every critical endpoint.

  • HTTP(S)
  • TCP / UDP
  • DNS
  • Ping
  • Mail servers
  • Browser flows
  • Cron
  • Change monitoring

Checked from several regions. Every live region confirms an outage before the incident opens.

01 — The essentials

Checks, alerts, a status page, and a team that sees the right sites.

  • Checks as often as every minute, alerts on the second failure

    HTTP, TCP, DNS, ping, mail servers, browser flows and cron heartbeats. One timeout is noted; two in a row open an incident and the alert goes to email, Slack, Teams, Discord, Telegram, a webhook or your phone.

  • A status page with your name on it

    Your logo, theme and domain, 90 days of uptime bars per site, maintenance notices and email subscribers.

  • A team where each person sees their own sites

    Owners, admins, site admins who get only the sites you assign, and viewers who see everything and change nothing.

02 — Beyond up or down

Why it went down, what is about to, and what broke quietly.

Every incident says why it happened

The check that opens an incident records what it saw: the DNS answer, the connection, the TLS handshake, each timing phase and the response. One plain sentence names the cause, so nobody starts by guessing.

Incident · What we sawRead the guide
  • DNS, connect, TLS and first-byte timings of the failed check
  • The status code, headers and the start of the response
  • A screenshot of the page as it was, from Pro

Broken, while the page still loads

Once a day each site is read from the outside for what no uptime check sees: a noindex tag that reached production, an analytics tag that vanished, WordPress plugins with known vulnerabilities, API keys and source maps left in public scripts.

Site health · read once a dayHow it works
  • A noindex tag, a robots.txt that blocks crawlers, a canonical to another host
  • Analytics and pixel tags that were there and are gone
  • Leaked keys and source maps, on domains you verify

A warning while the site is still up

Heedery learns each site’s usual response time from the last seven days. When it gets clearly slower, suddenly or week over week, you hear about it before it turns into an outage.

Response time · last 3 hoursRead the guide
  • Sudden: the last hour is at least twice as slow as usual
  • Creeping: this week is 50% slower than the week before
  • Outages and maintenance never teach it that slow is normal

A PageSpeed report, and what to fix first

PageSpeed is measured for you and a drop is logged as a change. Claude reads the stored report and writes a short plan: what to fix first, what it should bring and how to do it on your stack.

PageSpeed · the planRead the guide
  • Lab metrics, real-user data and audits with their savings
  • A plan that cites the audits, with numbers from the report only
  • Copy the prompt into your own AI assistant

Ask your AI assistant what is down

A REST API and an MCP server over the same workspace. Connect Claude or Cursor and ask what is down, read an incident or add a monitor without opening the dashboard.

MCP · in your AI assistantHow it works
  • Read-only tokens from Pro
  • Add monitors and acknowledge incidents from Team
  • An OpenAPI reference for every endpoint

Bring your monitors over with an API key

Paste the API key of your UptimeRobot or Better Stack account. Heedery shows what will come over, what changes on the way and why, and creates only what you tick.

Import · the previewRead the guide
  • Monitors, alert contacts and status pages
  • A preview before anything is created
  • Every plan, the free one included
03 — Signal over noise

Two failed checks open an incident. Two good ones close it.

Every site is checked on its own schedule, down to once a minute: HTTP with DNS, connect, TLS and first-byte timing, TCP and UDP ports, DNS lookups, ICMP ping, and SMTP, IMAP or POP3 servers. Browser flows walk through a site in a real browser and cron jobs ping a heartbeat URL. A single timeout is usually the network, so nothing is reported until the next check fails too.

  • Status codes, a keyword or a JSON value checked per site
  • Alerts by email, Slack, Teams, Discord, Telegram, signed webhooks or a phone push
  • A second message when the site is back
Read the guide
Incident lifecycle
  1. 14:02:00Check fails

    pay.acme.com did not answer within 10 s. Nothing is sent yet.

  2. 14:03:00Confirmed

    The next check fails too. The incident opens and the status page shows Checkout as down.

  3. 14:03:02Alert sentTeams · #ops

    Microsoft Teams message in #ops, right away or after the delay set on that channel.

  4. 14:05:00Recovered

    Two good checks in a row. The incident closes after 2 min and #ops hears about that too.

Confirmed signals. Clear recovery.
04 — Keep customers informed

One link for customers, with your logo and theme on it.

Each status page has its own address, name, logo and theme, scheduled maintenance and an announcement banner, and 90 days of uptime bars per site. Visitors can subscribe to hear about incidents and maintenance by email. SSL and domain expiry are checked daily so renewals stop being surprises.

  • Your own domain, with the certificate issued for you
  • Email subscribers with double opt-in and one-click unsubscribe
  • Categories, search and six themes
  • Only the sites you choose to publish
Your public status page
AC
Acme status
status.acme.com
Planned maintenance Sunday 02:00–03:00 UTC. Checkout may be slow for a few minutes.
Website
100%
API
99.98%
Checkout
99.95%
Powered by Heedery90 days
Theme
Your domain. Your brand. One trusted link.
05 — Wake the right person

A push to whoever is on call. The team lead next, if nobody answers.

The Heedery app for iPhone and Android gets a push the moment an incident opens. It is marked time-sensitive, so it gets through Focus, and a tap opens the incident to acknowledge it. On Pro and up, an escalation policy decides who hears next and when, and an on-call schedule decides who that is this week.

  • Push alerts in the iOS and Android app, through Focus
  • Acknowledge from the phone and the escalation stops
  • Escalation policies and on-call rotations from Pro
Escalation · Checkout API
Time Sensitivenow
Checkout API is down
2 failed checks · pay.acme.com
Escalation policy
  1. Step 1 · nowPaged 14:03
    AAna RuizOn call · Primary rotation
    PushEmail
  2. Step 2 · after 15 minWaits 15 min
    SSam PatelTeam lead
    PushEmailSlack #ops
On call · weekly rotation
  • Ana Ruiznow, until Mon 09:00
  • Lee Chennext, from Mon 09:00
One tap from the lock screen stops the next step.
06 — For agencies

Monthly reports and status pages in your client’s name.

From Team up, each client can get a monthly report by email: a PDF with their logo, uptime against the target you agreed, downtime, incidents, response times and the month day by day. Their status page can go white label: no “Powered by”, their domain and favicon, and subscriber emails sent from their own address.

  • Branded PDF reports every month, from Team
  • 5 white-label status pages included on Agency
  • On Pro and Team, white label is added one page at a time
Client reporting
NW
Northwind · Monthly report
September 2026 · prepared by your agency

Target metUptime was 99.92% vs 99.9%

Uptime
99.92%
Target 99.9% · met
Total downtime
35 min
Across 3 sites
Incidents
2
2 resolved
Mean time to resolve
17 min
First failure to recovery
Day by day
Incidents
8 SepCheckout18 min
21 SepBooking API17 min
Sites
northwind-2026-09.pdf
status.northwind.co
NW
Northwind status
All systems operational
Shop
Booking API
  • No “Powered by” anywhere
  • Their logo as the favicon
  • Subscriber emails from status@northwind.co
Their brand on every page, none of ours.
07 — Built for your team

Owners run the workspace. Site admins see only what they own.

Invite the team and give each person a role: owners manage billing and people, admins manage every site, site admins get the sites you assign and nothing else, and viewers see everything without changing a thing.

  • Owner, admin and site admin roles
  • Per-site access for site admins
  • A read-only viewer role
Workspace access
Team & site permissions
Sites visible to Lee2 of 4
  • Marketing sitewww.acme.comNo access
  • Public APIapi.acme.comCan edit
  • Customer portalapp.acme.comNo access
  • Checkoutpay.acme.comCan edit
Every person sees the sites they own.

08 — And more

  • Change monitoring

    DNS records and the certificate from Pro, page content and PageSpeed from Team. Every change is logged; you pick which ones alert.

  • Deploy markers on charts

    From Pro, CI reports each deploy with one request. It is marked on the charts, and an incident that starts within 30 minutes names it.

  • AI incident updates and postmortems

    Claude writes the status update from the incident’s facts, and the postmortem once it is resolved. You check it, edit it and publish; nothing goes out on its own.

Also in the box: maintenance windows that keep incidents and alerts quiet, two-factor sign-in, SSL and domain expiry checked daily, average response times in 5-minute buckets for 30 days and hourly for 90, daily uptime kept forever, and a checker that reports its own health.
Pricing

Start free. Scale when you’re ready.

Choose by the sites you monitor and the people on your team.

Save up to 21% with yearly billing

Starter

For a personal project or a small shop.

$0/ month

Free, no card required

Start for free
20 monitors
sites, APIs or servers you check
1 team member
  • Checks every 10 minutes
  • Email alerts
  • 30 days of latency and uptime history

Pro

For a freelancer or a small team with a few sites.

$11/ month

$132 billed yearly

Get Pro
25 monitors
sites, APIs or servers you check
3 team members
  • Checks every minute
  • Slack, Teams, Discord, Telegram & webhooks
  • 3 browser flows

Team

Recommended

For product teams that run a few services.

$32/ month

$384 billed yearly

Get Team
100 monitors
sites, APIs or servers you check
10 team members
  • Monthly client reports
  • 90 days of latency, uptime kept forever
  • 10 browser flows
  • 50 SMS/call credits a month included

Agency

For agencies that run status pages for their clients.

$82/ month

$984 billed yearly

Get Agency
250 monitors
sites, APIs or servers you check
25 team members
  • Everything in Team
  • 5 white-label status pages
  • 25 browser flows
  • 200 SMS/call credits a month included

Enterprise. On your terms.

1,000 monitors · Unlimited team members · SLA

From $250 / month
Annual contract
Talk to sales

No trial needed: Starter is free with no card. A paid plan's button creates your account, then takes you to the plan's checkout; it starts as soon as the payment goes through. Or start free and pick a plan later under Settings → Plan.

Prices in USD, excluding VAT. Every plan includes the public status page with unlimited viewers. White label is per status page: $49 a page a month on Pro, $29 on Team, and on Agency 5 pages are included and each further one is $19.

09: A few more details

Questions people ask before they sign up.

Something else? Write to us.

With one-minute checks an outage is confirmed by the second failed check, so within about two minutes. Email goes out right away; Slack, Teams, Discord, Telegram and webhooks right away or after the delay you set on the channel.

Contact

Questions? Write to us.

Setup, alerts, billing or a plan for your company: a person reads every message and answers within one working day.

All fields are required.

Topic
0 / 5,000

We use what you send only to answer you. See the Privacy Policy.

Add your first site.

The first check runs within a minute.

Start for free

20 monitors free, No card required

See what a status page looks like