Introduction

Teravor in one minute. Add your first monitor, ship a status page, and understand the four primitives every workflow is built on.

What is Teravor?#

Teravor is an uptime and synthetic monitoring platform built for teams that want the control of self-hosting without giving up the convenience of a managed service. Every check runs from our global probe network, incidents page on-call in seconds, and your status page is one endpoint away.

If you've used Pingdom, Uptime Kuma, or Better Stack, Teravor will feel familiar — but with a first-class API, predictable pricing, and zero SaaS lock-in for the data plane.

The four primitives#

Everything in Teravor composes from four objects. Learn these once and the rest of the product maps to them.

Five-minute quickstart#

The simplest way to create a monitor: generate an API key in Settings → API keys, then fire this request:

curl -X POST https://monitor.teravor.com/api/monitors \
  -H "Authorization: Bearer $TERAVOR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "api.acme.io health",
    "type": "http",
    "config": {
      "url": "https://api.acme.io/healthz",
      "method": "GET",
      "expected_status": [200]
    },
    "interval_sec": 60
  }'

Next steps#

• Pick a monitor type from the monitor types reference — HTTP, TCP, DNS, SSL, ping, or heartbeat.
• Wire up an alert channel in Settings → Integrations so you get paged when something breaks.
• Publish a status page — turn your monitors into a public uptime dashboard in one click.
• Manage monitors as code via the Terraform provider or the CLI (available on Pro).