Help & Guide

First analysis takes about 2-5 minutes: sign in, paste logs, click generate, review root cause and fix suggestions.

1. Sign in (required for all plans and checkout pages)
2. Paste logs (Datadog, CloudWatch, JSON, plain text)
3. Generate report (timeline + RCA + evidence refs)
4. Download PDF or share link

Simple model:

• Free: 1 analysis
• Pay-per-use: $5 / incident (flat)
• Pro: $29/month: unlimited analyses, evidence-backed RCA, and Slack integration (in-channel /incident and mentions)
• Team: same Slack as Pro, plus GitHub commit import, deploy webhooks, suggested fixes, and shared workspace controls: onboarded after Pro when you’re ready (contact us).
• Enterprise: larger seats, SSO/SAML depth, procurement: contact us

Free and pay-per-use are paste-in workflows. Pro is self-serve with full Slack. Team is the usual next step when you need repo-connected automation; we scope onboarding together.

Pro and Team only. After upgrading, connect once and then fetch threads/channels, run /incident, or @mention the bot for in-channel reports. Slack is not available on the Starter (free) plan: paste logs in the web app instead.

1. Account -> Add to Slack
2. Invite app to incident channel with/invite @ProdRescue AI
3. Generate from thread link/channel or in-channel trigger

Privacy: only channels where the app is invited; no DM reads by default.

Team (GitHub onboarding). Connect repository, run deploy analysis, generate suggested fixes, and review proposed changes before sending to GitHub: contact us to enable Team.

• Account -> GitHub -> Connect
• Choose repo and default target branch
• Use Suggest Fix, review diff, propose merge on GitHub

Safety: ProdRescue does not auto-merge. Your branch protection and approvals stay active.

• Slack post failed: make sure app is invited to that channel and workspace is the currently connected one.
• Generic report: include larger incident window and clear timestamps.
• Merge proposal failed: check GitHub repo permissions and branch protection requirements.
• Revenue impact missing: appears only if logs include measurable transaction/revenue signals.

• Sensitive fields are anonymized before model calls.
• No training on your incident content.
• Processing is designed to be ephemeral on our side.

Open-source anonymizer: github.com/Devrim0/prodrescue-anonymizer

• Slack connect path: Account -> Add to Slack
• Channel ID: right-click channel -> Copy link -> value after archives/
• Reports: App and Dashboard
• Need help: info@prodrescueai.com