---
title: Glowo
description: Uptime monitoring, alerting, and public status pages. Watch what you ship, tell people when it breaks.
sidebar:
  label: Introduction
  order: 0
---

Glowo checks that your services are up, tells the right people when they are not,
and gives your users somewhere to look when they ask "is it just me?".

## What Glowo does

<CardGroup cols={2}>
  <Card title="Monitor" href="/monitors" icon="activity">
    HTTP, TCP, ping, DNS, WebSocket, gRPC and heartbeat checks, run from nine regions
    on the interval you choose.
  </Card>
  <Card title="Alert" href="/alerting" icon="bell">
    Route failures to email, Slack, Discord, Telegram, SMS, PagerDuty or your own
    webhook — and acknowledge them in one click.
  </Card>
  <Card title="Publish" href="/status-pages" icon="globe">
    A branded status page on your own domain, with incidents, maintenance
    windows and subscriber notifications.
  </Card>
  <Card title="Automate" href="/ai-agents" icon="sparkles">
    Drive Glowo from an AI coding agent over MCP, or from your own scripts with
    an API key.
  </Card>
</CardGroup>

## Start here

If you are new, [Getting started](/getting-started) walks you from signing up to a
working monitor with alerts in about ten minutes.

If you already have monitors and want a specific answer, the sidebar is grouped
the way the product is: **Monitors**, **Alerting**, **Status pages**,
**Organization**, and **Plans**.

:::note
Something wrong or missing in these docs? They live alongside the code — say so
and it gets fixed in the same pull request as the behaviour.
:::