Skip to content
upcertain
Early access

Uptime you can be certain of.

Upcertain checks your websites, APIs, ports and certificates on the schedule you set. When a failure is confirmed it opens an incident, alerts the people who own the service and shows the outage on your status page.

Create your accountView a live status page
6
check types
6
alert channels
1
account for monitors, incidents and status pages

01How it works

From a failed check to a clear answer

There is nothing to install. Upcertain checks from the outside, the way your customers reach you.

  1. 01

    Add what you run

    Paste a URL or a host, pick the check type and interval, and choose which channels hear about it.

  2. 02

    Failures are confirmed

    A failed check is re-checked before anything happens, so one dropped request does not page anyone. You set how many failures in a row count.

  3. 03

    The right people hear once

    An incident opens, alerts go to that monitor's channels, and the status page shows the component as down until it recovers.

02Features

Everything an outage touches, in one account

Monitors, incidents, alerts and status pages share one account, so an outage goes from the first failed check to your customers without anyone copying it between tools.

  • Six check types

    HTTP(S), keyword, ping, port and SSL checks, plus heartbeats for cron jobs and workers that call in.

  • Intervals from 30 s to 24 h

    Set the interval per monitor, down to the fastest one your plan allows.

  • Confirmed before alerting

    Re-checks rule out a single flaky request before an incident opens.

  • Alerts where you work

    Email, Slack, Discord, Microsoft Teams, Google Chat and webhooks, routed per monitor.

  • SSL expiry warnings

    Warnings 30, 14 and 7 days before a certificate expires, and as soon as the chain or hostname stops matching.

  • Maintenance windows

    Alerts pause during a window, the time does not count against uptime, and the status page shows it ahead of time.

  • Roles for your team

    Owner, admin, editor and viewer roles, plus notify-only members who receive alerts and nothing else.

  • Separate accounts

    Each account's monitors, incidents and pages are isolated at the database level. Switch between the accounts you belong to.

  • REST API and MCP

    Read and change monitors and incidents with an account API key, from scripts or AI agents.

03Incidents and alerts

Every outage gets a record, not just a ping

Connect Slack with an incoming webhook and route each monitor to the channel that owns it. The alert links to the incident, where your team acknowledges it to stop repeat alerts; the recovery follows in the same channel.

  • Opened on a confirmed failure, closed on recovery
  • Response code, duration and who acknowledged it on one timeline
  • Comments for your team and public updates for your status page
  • Each email recipient gets a personal link to stop alerts

04Status pages

Answer “is it down?” before anyone asks

Group monitors into components, show 90 days of uptime and post incident updates as they happen. Serve the page from your own subdomain so it looks like part of your product.

  • Custom domain via CNAME, HTTPS issued automatically
  • Public, private or password-protected
  • Subscribers get an email for each announcement you publish
  • Scheduled maintenance shown ahead of time

05API and MCP

Your agents can ask what's down, too

Upcertain ships a REST API and an MCP server. Point Claude, Cursor or your own agent at it and they can list monitors, read uptime and incidents, create checks and acknowledge incidents, scoped to your account's API key.

Read the MCP docs
Agent over MCP
// Claude, via the Upcertain MCP server
> Which of our APIs had incidents this week?
// tool: list_incidents({ since: "7d" })
payments-api · 2 incidents · 14 min total
auth-service · 0 incidents · 100%
webhooks · 0 incidents · 100%
REST API
$ curl -H "Authorization: Bearer $UPC_KEY" \
https://upcertain.com/api/v1/incidents?since=7d
{
  "data": [
    { "monitor_name": "payments-api",
      "status_code": 503,
      "duration_seconds": 559, ... }
  ]
}

06Plans

Plans that follow your monitor count

Every account starts on Basic. Owners and admins move up when they need more monitors or faster checks, and can switch plans any time from Settings.

Compare plans in detail

Basic

For a side project or a single product.

Early access
  • 10 monitors
  • 1-minute checks
  • 1 status page
  • Owner only
Start with Basic

Team

For teams running several services in production.

Early access
  • 100 monitors
  • 30-second checks
  • Unlimited status pages
  • Custom domains for status pages
  • Unlimited team members with roles
  • MCP server for AI agents
Create your account

New accounts start on Basic. Switch to Team in Settings, Plan & usage.

Business

For agencies and platforms monitoring on behalf of clients.

Custom
  • Custom monitor count and check interval
  • Everything in Team
  • Priority support and onboarding
Talk to us

Billing is not enabled yet; plans are assigned from your account settings during early access.

07Questions

Before you sign up

Something else? Send us a message.

What can Upcertain check?
Websites and APIs over HTTP(S), pages that must contain a keyword, hosts by ping, open TCP ports and SSL certificates. Heartbeat monitors work the other way round: your cron job or worker calls a URL, and Upcertain alerts when the calls stop arriving.
How does it avoid false alarms?
When a check fails, Upcertain re-checks before opening an incident, so a single dropped request does not alert anyone. You can set how many failed checks in a row are needed per monitor.
Where do alerts go?
Email, Slack (through an incoming webhook), Discord, Microsoft Teams, Google Chat and your own webhooks. Each monitor can alert different channels, and each email recipient gets a personal link to stop alerts.
Can a status page use our own domain?
Yes, on plans that include custom domains. Point a CNAME record at Upcertain and the HTTPS certificate is issued automatically. Pages can be public, private or password-protected.
Can AI agents use Upcertain?
Yes. The MCP server lets Claude, Cursor or your own agent list monitors, read uptime and incidents, create monitors and acknowledge incidents with an account API key. See the MCP docs.
How much does it cost?
Upcertain is in early access. Billing is not enabled yet, so plans are assigned from your account settings. We will announce prices before any billing starts, and nothing is charged without your agreement.

Put your first URL under watch

Sign up with your email and the website you want to monitor. Upcertain starts checking it right away.

Create your accountView a live status page