Welcome to SutramX

SutramX checks your websites, APIs, servers and scheduled jobs from probe regions around the world. When something breaks, it confirms the failure, opens an incident, tells you why it alerted (including when the cause is probably not yours), alerts the right people and can update a public status page. These docs explain how to set it up and how each part works.

You don't need to install anything. SutramX sends real requests to your endpoints from outside your infrastructure, so there is no agent, SDK or code change. The only exception is heartbeat monitors: your job calls a SutramX URL when it runs.

What you can do with SutramX#

• Monitor almost anything that answers on the network. HTTP and website checks with keyword rules, API checks with assertions, multi-step API flows, ping (ICMP), TCP and UDP ports, DNS records, remote MCP servers, and heartbeat checks for cron jobs and background workers. On plans that include them, browser checks run scripted journeys in a real browser.
• Know why every alert fired. Each incident shows every region's result, the quorum rule, the failure class, the alert decision and a fault verdict, and each monitor gets a flakiness score. See Why this alert.
• Tell your outage from a vendor's. SutramX flags vendor APIs such as Stripe or OpenAI that are failing for several customers at once: see Vendor health.
• See what Indian users see. Check from Jio, Airtel, Vi, BSNL and ACT networks to catch ISP blocks: see Last-mile checks.
• Catch expiring certificates and domains. Turn on email reminders before an SSL certificate or domain registration expires on any HTTP or API monitor.
• Avoid false alarms. A failed check is retried. On paid plans, which check from more than one probe region, the regions must agree before an incident opens.
• Alert people where they work. Email, browser push, Slack, Discord, Microsoft Teams, Google Chat, Mattermost and Telegram, plus webhooks, Zapier, GitHub issues, PagerDuty, Opsgenie, SMS, WhatsApp and voice calls, depending on your plan.
• Run on-call. Escalation policies, on-call rotations, quiet hours and runbooks are available on the plans that include them.
• Work incidents. Acknowledge, snooze, resolve, add notes, write postmortems and, on plans that include it, use AI summaries and drafts.
• Tell your users. Publish status pages with live status, 90-day uptime, incident history and maintenance notices. Higher plans add custom domains, password or SSO protection, extra languages and white-labelling.
• Plan downtime. Maintenance windows silence alerts and are left out of uptime figures.
• Understand reliability. Reliability IQ covers SLOs and error budgets, tail latency, anomalies, dependencies and health scores. You can also track deploys and run website health crawls.
• Automate. Use the REST API, the CLI, the GitHub Action, the Terraform provider or the MCP server with an API key to manage monitors and read results from your own tools.

Start here#

• Quickstart: create an account and your first monitor, set up alerts, publish a status page and invite your team.
• Core concepts: the vocabulary used throughout the product, such as monitors, regions, confirmation, incidents and workspaces.
• Dashboard tour: a walk through every area of the dashboard and what it's for.

Explore the docs#

• Monitors: every monitor type, its settings, regions and confirmation, and maintenance windows.
• Alerts & incidents: how alerts are routed, every alert channel, escalation and on-call, and the incident workflow.
• Status pages: public pages, branding, custom domains, private pages and subscribers.
• Reliability: Reliability IQ, deployment correlation, and reports and exports.
• Account & team: sign-in and security, team members and roles, workspaces, and your profile.
• Plans & billing: what each plan includes, payments and invoices, changing plans, alert credits and the affiliate program.
• Developers: the REST API and API reference, the CLI and GitHub Action, the Terraform provider and the MCP server.
• Help: FAQ, troubleshooting, glossary and how to contact support.

How these docs are organised#

The sidebar follows how you use SutramX:

Each page opens with a short summary and puts settings in tables. Most pages end with common questions and links to related pages. Interface labels appear in bold, and navigation paths are written like Monitors → New monitor.

Coming soon#

The following are in development and not available yet: OpenTelemetry export, deploy-platform integrations (Netlify and Render) and the iPhone app. Their pages explain what is planned.