Built for developers
who ship fast.
REST API on every plan. A monitors-as-code CLI. MCP for Claude and ChatGPT. AI-authored browser checks. Webhooks and an OpenAPI spec. No GUI required.
Start free — 10 monitors at 30sEverything you need in your workflow
REST API on all plans
Create, update, and delete monitors programmatically. No paid tier required for API access.
Monitors-as-code CLI
One static binary. Define monitors in YAML, `uptrack apply` from CI, review changes in a PR.
MCP integration
Connect Uptrack to Claude or ChatGPT via MCP. Ask your AI to check status or create monitors.
AI-authored checks
Paste a URL and AI drafts a Playwright browser check you can review, edit, and run. Free.
Webhook payloads
Structured JSON on every status change. Route to Slack, Discord, PagerDuty, or your own service.
OpenAPI spec
Full OpenAPI 3.0 spec. Generate a typed client in any language.
Create a monitor in one request
Add monitoring to your deploy script, CI pipeline, or development workflow.
curl -X POST https://api.uptrack.app/api/monitors \
-H "Authorization: Bearer $UPTRACK_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "API health",
"url": "https://myapp.com/health",
"monitor_type": "http",
"interval": 30
}'Or keep your monitors in Git
The uptrack CLI is one static binary — define monitors in YAML and apply them from CI. Review changes in a pull request, sync on merge.
# install (macOS / Linux) curl -fsSL https://raw.githubusercontent.com/Uptrack-App/uptrack-cli/main/install.sh | sh export UPTRACK_API_KEY=utk_… uptrack export -o uptrack.yaml # snapshot what you have uptrack apply -f uptrack.yaml # create/update to match (--dry-run to preview)
Ship, monitor, iterate
You deploy a new service. Your CI pipeline calls the API to create a monitor. Uptrack checks it every 30 seconds. If it goes down, you get a webhook in Slack before your users notice. Fix it, push, move on. No dashboards to click through.