Browse the sections below or use the quick navigation chips.
IncidentPulse is an internal and public incident management platform that helps teams log outages, coordinate responders, and communicate status transparently. It replaces spreadsheets and siloed tools with a single system of record for incidents, teams, and customer-facing updates.
Fragmented tooling slows response and frustrates customers. IncidentPulse centralizes detection, response, and communication so every stakeholder sees the same truth.
Designed for Admins, Operators, and Public stakeholders who need accountability and transparency.
Admin
Platform owners orchestrating policy, integrations, and governance.
Operator
On-call responders executing playbooks and communicating progress.
Public
Customers, partners, or executives monitoring health and uptime.
Each incident moves through a connected lifecycle so no context is lost between teams.
Alerts and monitors create an incident with auto severity.
Operators assign roles, run playbooks, and capture updates.
Stakeholders receive timeline posts, email, and status page updates.
Admins review analytics, publish postmortems, and refine SLAs.
Map responsibilities to clear permissions so the right people can act quickly without risking governance.
Configures the platform, enforces governance, and provides leadership with holistic visibility.
Frontline responders who run playbooks, collaborate in the timeline, and keep stakeholders informed.
Stakeholders, customers, or partners who consume the read-only status page and historical reports.
| Capability | Admin | Operator | Public |
|---|---|---|---|
| Create / triage incidents | Full | Full | No |
| Edit SLAs & playbooks | Full | Suggest | No |
| Publish status updates | Full | Full | Read |
| Manage team members | Full | No | No |
| View analytics & MTTR | Full | Full | Summary |
| Configure integrations | Full | Request | No |
| Brand public status site | Full | Request | No |
Each capability pairs a polished UI with deep operational workflows so you can launch quickly and scale with confidence.
Unify alert intake, manual reports, and automation triggers into a single prioritized queue.
Keep stakeholders aligned with templated updates across email, Slack, and public channels.
Model each customer-facing surface—website, APIs, data stores—and monitor them independently.
Clarify ownership by assigning incident commanders, communications leads, and subject experts.
Monitor MTTR, detection time, and customer impact with ready-to-share analytics dashboards.
Give responders a single place to upload screenshots, HAR files, or log bundles alongside each timeline update.
Deliver a trustworthy, branded status experience that reflects the latest internal truth.
Govern identity providers, integrations, webhooks, and audit trails from a single control center.
IncidentPulse separates marketing, operator, and public surfaces while sharing a secure core API and database.
Next.js marketing site and authenticated dashboard deployed on Vercel with React Server Components for performance.
Node/Express service hosted on Render exposes REST endpoints, handles auth, and orchestrates incident workflows.
PostgreSQL managed by Prisma migrations stores incidents, updates, user roles, and SLA policies with auditing.
Static, cache-friendly status site hydrated via incremental revalidation so customers always see accurate data.
A streamlined developer experience keeps onboarding fast whether you are evaluating locally or deploying to the cloud.
Follow these steps to stay productive.
Follow these steps to stay productive.
Follow these steps to stay productive.
Connect monitoring platforms, scheduled jobs, or custom scripts to IncidentPulse. Alerts create or update incidents automatically, while recovery events close them and notify the assigned operator.
X-Signature (HMAC-SHA256 using WEBHOOK_HMAC_SECRET). Trusted internal tools can fall back to X-Webhook-Token.X-Idempotency-Key, a 60 requests/minute rate limit per token, and a ±10 minute skew window onoccurredAt keeps integrations reliable.WEBHOOK_HMAC_SECRET – required hex string used when calculating HMAC signatures. Generate it once (for exampleopenssl rand -hex 32), store it in Render → Environment, and distribute it to downstream tools via your secrets manager — it is not displayed in the dashboard.WEBHOOK_SHARED_TOKEN – optional bearer token for services that cannot sign requests.WEBHOOK_SYSTEM_USER_ID – optional UUID of the automation account that should author webhook incidents.GET /metrics/webhook (requires admin authentication).Treat the HMAC secret like any other credential: rotate it from Render if compromised and share it with integrators through a secure channel (password vault, secret manager). Open the dashboard’s Webhooks & Integrations tab to copy the alert and recovery endpoints, grab ready-to-run cURL/Postman snippets, and wire up Slack, Discord, Teams, or Telegram notifications. The panel reiterates which secrets live in Render but intentionally never exposes the raw values to prevent leakage.
POST /webhooks/incidents
Content-Type: application/json
X-Signature: <hex-hmac-from-WEBHOOK_HMAC_SECRET>
{
"service": "checkout-api",
"environment": "production",
"eventType": "error_spike",
"message": "500 errors exceeded 5% in the last 2 minutes",
"severity": "high",
"occurredAt": "2024-11-05T22:55:00Z",
"fingerprint": "checkout-api|production|error_spike",
"meta": {
"errorCount": 324,
"threshold": "5%"
}
}POST /webhooks/incidents/recovery
Content-Type: application/json
X-Signature: <hex-hmac-from-WEBHOOK_HMAC_SECRET>
{
"fingerprint": "checkout-api|production|error_spike",
"occurredAt": "2024-11-05T23:05:00Z",
"meta": {
"note": "Service restored automatically"
}
}- name: Notify IncidentPulse when workflow fails
if: failure()
env:
INCIDENT_URL: ${{ secrets.INCIDENTPULSE_ALERT_URL }}
INCIDENT_SECRET: ${{ secrets.INCIDENTPULSE_HMAC }}
run: |
payload=$(cat <<'JSON'
{
"service": "ci-pipeline",
"environment": "${{ github.ref_name }}",
"eventType": "workflow_failure",
"message": "Workflow ${{ github.workflow }} failed on ${{ github.sha }}",
"severity": "high",
"occurredAt": "${{ github.event.head_commit.timestamp }}",
"fingerprint": "ci|${{ github.repository }}|${{ github.workflow }}"
}
JSON
)
signature=$(echo -n "$payload" | openssl dgst -sha256 -hmac "$INCIDENT_SECRET" | sed 's/^.* //')
curl -sSf -X POST "$INCIDENT_URL" \
-H "Content-Type: application/json" \
-H "X-Signature: $signature" \
--data "$payload"{
"service": "edge-api",
"environment": "production",
"eventType": "uptimerobot_{{ALERT_TYPE}}",
"message": "Monitor {{MONITOR_NAME}} reported {{ALERT_TYPE}}",
"severity": "high",
"fingerprint": "uptimerobot|{{MONITOR_ID}}",
"occurredAt": "{{ALERT_TIME_ISO}}",
"meta": {
"monitorUrl": "{{URL}}",
"friendlyStatus": "{{ALERT_TYPE}}"
}
}fingerprint for ten minutes while the incident is open; higher severity replays automatically escalate.resolvedAt, and notify the assigned operator plus the incident timeline.Pair the API with React Query on the frontend or integrate with other systems for automation and reporting.
POST /auth/login
Content-Type: application/json
{
"email": "oncall@example.com",
"password": "super-secret"
}200 OK
Content-Type: application/json
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
"user": {
"id": "usr_123",
"name": "Riley SRE",
"role": "admin",
"team": "Site Reliability"
}
}GET /incidents?status=active&severity=high
Accept: application/json200 OK
Content-Type: application/json
{
"data": [
{
"id": "inc_481",
"title": "Checkout latency spike",
"severity": "high",
"state": "investigating",
"owner": "Alex Rivera",
"opened_at": "2025-11-02T16:21:00.000Z"
}
],
"meta": {
"page": 1,
"pageSize": 25,
"total": 74
}
}PATCH /incidents/inc_481
Content-Type: application/json
{
"state": "mitigated",
"assignee": "Jordan Lee",
"timeline": [
{
"type": "update",
"body": "Applied hotfix to rollback release 2025.11.02"
}
]
}200 OK
Content-Type: application/json
{
"id": "inc_481",
"state": "mitigated",
"resolved_at": "2025-11-02T17:05:00.000Z",
"timeline": [
{
"at": "2025-11-02T16:45:00.000Z",
"body": "Applied hotfix to rollback release 2025.11.02",
"author": "Jordan Lee"
}
]
}POST /incidents/inc_481/attachments
Content-Type: multipart/form-data
file: outage-dashboard.png201 Created
Content-Type: application/json
{
"error": false,
"data": {
"id": "att_901",
"filename": "outage-dashboard.png",
"mimeType": "image/png",
"size": 418204,
"url": "/uploads/incidents/inc_481/outage-dashboard.png"
}
}DELETE /incidents/inc_481/attachments/att_901204 No ContentPOST /maintenance
Content-Type: application/json
{
"title": "Database maintenance",
"description": "Upgrading storage tier. Read-only for 15 minutes.",
"startsAt": "2025-11-10T01:00:00Z",
"endsAt": "2025-11-10T01:15:00Z",
"appliesToAll": false,
"serviceId": "svc_db_primary"
}201 Created
Content-Type: application/json
{
"error": false,
"data": {
"id": "mnt_901",
"status": "scheduled",
"startsAt": "2025-11-10T01:00:00.000Z",
"endsAt": "2025-11-10T01:15:00.000Z",
"appliesToAll": false,
"service": {
"id": "svc_db_primary",
"name": "Primary Database"
}
}
}GET /maintenance?window=upcoming
Accept: application/json200 OK
Content-Type: application/json
{
"data": [
{
"id": "mnt_901",
"title": "Database maintenance",
"status": "scheduled",
"startsAt": "2025-11-10T01:00:00.000Z",
"endsAt": "2025-11-10T01:15:00.000Z",
"appliesToAll": false,
"service": {
"id": "svc_db_primary",
"name": "Primary Database"
}
}
]
}Guide operators and admins through frequent blockers to keep the platform running smoothly.
Operators only see incidents tied to their services or assignments. Ask an Admin to extend your service scope or grant temporary all-incident access when needed.
The public page only shows incidents marked as customer-impacting or scheduled maintenance. Confirm incidents have published updates and that cache invalidation has completed.
The backend streams files into the directory referenced by UPLOAD_DIR (uploads/ by default, relative to the backend app) and serves them via the /uploads prefix. Point UPLOAD_DIR at persistent storage so artifacts survive restarts.
Admins can connect Slack, Discord, Microsoft Teams, or Telegram under System Settings → Integrations. Paste the webhook URL or bot credentials, choose the destination channel, and IncidentPulse will publish incident creation, assignment, and resolution events automatically.
Yes. Import CSV data or use the bulk API to seed legacy incidents. Run "npm run seed" in the backend to load sample data for demos.
Developed by the IncidentPulse team for demonstration and portfolio scenarios. Contributions, bug reports, and feature requests are welcome.