postmortem.so/Docs

Getting Started

Get your first incident pipeline running in under 2 minutes. Connect your existing monitoring tools, add endpoints to monitor directly, or both.

1. Create an account

Sign up at postmortem.so — no credit card required for the free tier.

2. Create a project

Click New project + from the dashboard. Enter:

  • Project name — your service name (e.g., “My API”)
  • Base URL — the root URL of your service (e.g., https://api.example.com)
  • Slug — used for your public status page URL (e.g., postmortem.so/status/my-api)

3. Choose your path

postmortem.so has two ways to feed incidents into your project. You can use either or both.

Option A — Connect existing tools

If you already use Sentry, Grafana, or any tool that sends webhook alerts, enable Webhook ingestion in Project Settings. Alerts flow in automatically — incidents are created and enriched with the external signal data.

  • Go to Project Settings → Incident Sources → Webhook ingestion
  • Toggle it on and generate a secret
  • Paste the webhook URL into your monitoring tool

See the Integrations guide for setup instructions for Sentry, Grafana, and the generic adapter.

Option B — Use built-in monitoring

Import your API spec or add endpoints manually. postmortem.so runs uptime checks and opens incidents automatically when checks fail.

  • Free plan — checks every 5 minutes
  • Pro and Team — checks every minute

See How Monitoring Works for check intervals, incident detection, and flap protection.

4. Your status page is live

Your public status page is immediately available at:

postmortem.so/status/your-slug

Share it with your users or embed it in your documentation. Subscribers can opt in to email notifications on Pro and Team plans.

5. Set up alerts

Slack — go to Project Settings and add your Slack webhook URL. You'll get notifications when incidents are created and resolved.

Email — on Pro and Team plans, your status page subscribers receive email notifications automatically.

What happens when something goes down?

Whether triggered by a webhook alert or a failed uptime check, the incident lifecycle is the same:

  1. An incident is created automatically
  2. You're alerted via email and Slack
  3. The incident appears on your public status page in real-time
  4. You can post timeline updates as you investigate
  5. When resolved, generate an AI post-mortem with one click (Pro and Team) — Claude reads every signal including webhook payloads, check history, and timeline updates

Next steps