What tools does Opsrift include?

Opsrift includes six product areas: (1) Postmortem Generator — 9-section incident postmortems; (2) Shift Handover Generator — structured handovers with auto-imported incidents; (3) Runbook Generator — operational runbooks from incidents or postmortems; (4) Incident Investigation — AI-assisted Q&A over your incident context; (5) Status Page — hosted public status with components and incidents; (6) Incident Forecast — proactive risk signals from your postmortem history. All six tools are available today.

How does Opsrift generate postmortems?

Opsrift uses Anthropic's Claude AI to generate 9 structured sections in parallel: Executive Summary, Timeline, Root Cause Analysis, Impact, Detection & Response, Resolution, Process & Organizational Gaps, Action Items, and Lessons Learned. Import from PagerDuty, OpsGenie, Datadog, Grafana, or Jira (where connected), or enter data manually.

What integrations are available?

Opsrift supports PagerDuty and OpsGenie for incident import, Datadog and Grafana for alert and metric import, Jira for import and action item push, Confluence for one-click publishing, Slack and Microsoft Teams for webhook notifications and summaries, and GitHub for deploy-to-incident correlation. All nine integrations are available now.

What does the Starter plan include?

The Starter plan at $10/month gives you 10 AI generations per month, all core tools (postmortem, handover, runbook, investigation), 1 status page, PagerDuty & OpsGenie import, and exports. Every plan includes a 7-day free trial — a card is required to start, but you can cancel anytime.

How to automate shift handovers?

Connect PagerDuty or Jira, define your shift window (including quick presets like last 8h / 12h / 24h), and Opsrift generates a 7-section handover with summary, active incidents, tasks, escalations, metrics, upcoming changes, and notes — in under a minute instead of a long verbal passdown.

What is Incident Forecast?

Incident Forecast analyzes your saved postmortem history to surface proactive risk signals: recurring systems, deploy-to-incident correlation, unresolved action item debt, severity trend (worsening/improving/stable), and mean time between incidents (MTBI). An AI-generated risk brief summarizes the overall picture so you can act before the next incident hits.

Can I edit the generated reports?

Yes. Every section can be edited inline or regenerated individually with AI. You can click any section heading to enter edit mode, make changes, and the report updates in real time. You can also regenerate a specific section while keeping the rest intact.

Is my incident data secure?

Yes. Opsrift uses Clerk for authentication, Supabase with Row Level Security for data storage, and all API calls are encrypted via HTTPS. Your incident data is only used to generate your reports and is never used for AI model training.

Jira & Confluence Integration

Opsrift's Jira integration is two-way: import issues from Jira to generate postmortems, and push action items back to Jira as tickets with automatic priority mapping. Confluence publishing uses the same Atlassian credentials — publish your postmortem with one click and get full ADF formatting with cross-linked Jira references.

For a comparison of how Opsrift and Jira Service Management work together, see Opsrift vs Jira Service Management.

Import from Jira

Connect Atlassian credentials (domain, email, API token) — stored per-user, reused
Select a Jira project
Filter issues by type (Bug, Incident, Task, etc.)
Search by issue key or keyword
Select an issue — details auto-fill into the generation form
Uses the Jira Cloud REST API v3 (GET /rest/api/3/search/jql)

Push Action Items to Jira

After generating a postmortem:

Click "Push to Jira" on the action items section
Each action item creates a Jira ticket in your selected project
Priority auto-maps: High → Jira "High", Medium → Jira "Medium", Low → Jira "Low"
Action item IDs in the postmortem report become hyperlinks to the created Jira tickets
Track follow-through directly in Jira where your team already works

Publish to Confluence

Uses the same Atlassian credentials as Jira (no separate connection)
One-click publish converts the postmortem to Atlassian Document Format (ADF)
Supported ADF elements: headings, tables, bold, code inline, code blocks, blockquotes, bullet lists, ordered lists, links
Jira ticket links are embedded in the action items section of the Confluence page
After publishing, the Confluence page URL is automatically commented on all linked Jira action item tickets
This creates full cross-referencing: Jira tickets link to Confluence, Confluence links to Jira

Setup Requirements

An Atlassian Cloud account (Jira Cloud and/or Confluence Cloud)
An Atlassian API token (generated at id.atlassian.com)
Your Atlassian domain (e.g., yourcompany.atlassian.net)
The email associated with your Atlassian account
Available on Opsrift Pro plan ($29/month)

Security

Atlassian credentials are stored per-user in Supabase with row-level security
Credentials are never shared across users or exposed in client-side code
Opsrift reads issues for import, creates tickets for action items, and creates/updates Confluence pages — it does not delete or modify existing Jira issues or Confluence content
Incident data passes through the Anthropic API for generation only and is not used for model training

Frequently Asked Questions

Does Opsrift work with Jira Cloud or Jira Server?

Currently Jira Cloud only, using the REST API v3.

Is Jira integration available on the Starter plan?

Jira integration (import + push + Confluence) requires the Pro plan at $29/month. PagerDuty import is available on all plans.

Can Opsrift modify or delete my existing Jira issues?

No. Opsrift only reads existing issues for import and creates new tickets for action items. It does not modify or delete anything already in Jira.

Does Confluence publishing require a separate connection?

No. Confluence uses the same Atlassian credentials as Jira. If you've connected Jira, Confluence publishing works automatically.