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.

Opsrift vs Jira Service Management

This isn't an either/or comparison. Opsrift and Jira Service Management (JSM) serve different functions in the incident management lifecycle. JSM is a ticketing and ITSM platform — it tracks incidents, manages workflows, and handles service requests. Opsrift is a documentation generation tool — it takes incident data (including from Jira) and produces structured postmortems, shift handovers, and runbooks. They work together, not against each other.

What Jira Service Management Does

Incident ticketing and tracking
Service request management
SLA tracking and reporting
Workflow automation (status transitions, assignments)
Integration with Confluence, Opsgenie, and the Atlassian ecosystem
Post-incident review templates (manual)
ITIL-aligned processes

What Opsrift Does

AI-powered postmortem generation from incident data
Shift handover document generation
Operational runbook generation
Import incidents from PagerDuty and Jira
Push action items to Jira as tickets with priority mapping
Publish reports to Confluence with ADF formatting
Per-section editing, regeneration, and export

Where They Overlap — and Where They Don't

JSM has a built-in post-incident review (PIR) feature, but it's a manual template. You fill in each section by hand — the same process as opening a blank document, just inside the Jira interface.

Opsrift automates the generation part. It imports the incident from Jira, generates a structured 9-section postmortem using AI, and pushes results back to Jira and Confluence. The output is more detailed and more consistent than what most teams produce manually.

If you use JSM for incident tracking, adding Opsrift means your postmortems get written in 60 seconds instead of 1–3 hours, with consistent structure every time.

Side-by-Side Comparison

Capability	Jira Service Management	Opsrift
Incident tracking & ticketing	Yes (core feature)	No (imports from Jira)
SLA management	Yes	No
Workflow automation	Yes	No
Postmortem generation	Manual template	AI-generated, 9 sections, under 60s
Postmortem structure consistency	Depends on author	Same structure every time
PagerDuty import	Via Opsgenie integration	Native, one-click
Action item → Jira ticket	Manual ticket creation	Automatic push with priority mapping
Confluence publishing	Manual (copy/paste or link)	One-click with ADF formatting
Shift handover generation	Not a feature	7-section AI generation with auto-fetch
Runbook generation	Not a feature	8-section AI generation
Per-section editing	Edit full template	Inline split editor per section
Per-section regeneration	N/A	Yes, regenerate independently
Pricing	Free (3 agents) to $47.82/agent/mo	Starter $10/mo, Pro $29/mo

When to Use Both Together

The recommended workflow for teams already on Jira:

Incident occurs — tracked in JSM as usual
Incident resolves — open Opsrift, import the Jira issue
Opsrift generates the postmortem in 60 seconds
Review and refine the output
Push action items back to Jira as new tickets
Publish the postmortem to Confluence
Confluence page auto-links back to the Jira action items

This keeps Jira as your system of record while eliminating the manual documentation bottleneck. For integration details, see the Jira & Confluence Integration page.

When Opsrift Isn't the Right Tool

If you need incident ticketing, alerting, or SLA tracking — that's JSM/PagerDuty territory, not Opsrift. Opsrift is a documentation generation tool, not an incident management platform.

If your team writes fewer than 3 postmortems per month, the Starter plan covers you. Below that volume, the ROI of any additional tooling is low.

If your organization requires a specific proprietary postmortem format that can't be achieved with per-section editing, a manual template might be more appropriate.

Frequently Asked Questions

Does Opsrift replace Jira Service Management?

No. Opsrift complements Jira by automating the postmortem documentation that JSM handles manually. You keep Jira for ticketing and tracking; Opsrift handles report generation.

Can Opsrift import incidents from Jira?

Yes. Connect your Atlassian credentials, select a project, and import any issue. Incident details auto-fill into the generation form.

Does Opsrift push action items back to Jira?

Yes. After generating a postmortem, you can push action items as Jira tickets with automatic priority mapping (High→High, Medium→Medium, Low→Low). The action item IDs in the report hyperlink to the created Jira tickets.

Can Opsrift publish to Confluence?

Yes. One-click publishing with proper Atlassian Document Format (ADF) — headings, tables, code blocks, and linked Jira action items. After publishing, the Confluence page URL is auto-commented on all linked Jira tickets.

How much does Opsrift cost compared to Jira?

Opsrift's Starter plan is $10/month with 10 AI generations and PagerDuty import. Pro is $29/month for unlimited generations plus full Jira integration and Confluence publishing. JSM pricing ranges from free (3 agents) to $47.82/agent/month for Premium.