Integrations
Deployment Platforms
Connect Vercel, Railway, Netlify, Render, Fly.io, AWS CodeDeploy, and Buildkite to correlate deployments with deploy risk scores and incident outcomes.
Overview
Koalr integrates with 10+ deployment platforms to capture deployment events in real time. Each deployment is automatically correlated with:
- The pull request(s) it contains
- The pre-merge deploy risk score for those PRs
- Any incidents that occur within 2 hours of the deployment
- DORA metrics (deployment frequency, lead time, change failure rate, MTTR)
Supported platforms
| Platform | Connection method | Data captured |
|---|---|---|
| Vercel | Vercel webhook → Koalr | Deploy started, succeeded, failed; preview vs. production |
| Railway | Railway webhook → Koalr | Deploy started, succeeded, failed; service name, environment |
| Netlify | Netlify webhook → Koalr | Build started, succeeded, failed; branch, deploy context |
| Render | Render webhook → Koalr | Deploy started, live, failed; service type |
| Fly.io | Fly.io webhook → Koalr | Deploy events, machine restarts |
| AWS CodeDeploy | AWS EventBridge rule → Koalr | Deployment group, revision, lifecycle events |
| Buildkite | Buildkite webhook → Koalr | Build queued, running, passed, failed; pipeline name |
| ArgoCD | ArgoCD notification → Koalr | Application sync status, health, revision |
| GitHub Actions | GitHub webhook (workflow_run) | Workflow run start/completion; job-level outcomes |
| Azure DevOps | Azure Service Hook → Koalr | Release pipeline events, stage status |
Connecting a deployment platform
- Navigate to Settings → Deployment Sources
- Click Connect next to your platform
- Copy the Koalr webhook URL shown in the modal
- Paste it into your platform's webhook settings (see platform-specific instructions below)
- Send a test event — Koalr will confirm receipt and show the deployment in your Deployments dashboard
Vercel
- Go to Vercel → Your Project → Settings → Webhooks
- Add webhook URL:
https://api.koalr.com/webhooks/vercel - Select events:
deployment.created,deployment.succeeded,deployment.error,deployment.canceled - Add the
X-Koalr-Tokenheader (found in your Koalr integration settings) for authentication
Railway
- Go to Railway → Project → Settings → Webhooks
- Add webhook URL:
https://api.koalr.com/webhooks/railway - Railway sends all deployment events by default — no event selection needed
Netlify
- Go to Netlify → Site → Site configuration → Build & deploy → Deploy notifications → Outgoing webhooks
- Add webhook URL:
https://api.koalr.com/webhooks/netlify - Select events:
Deploy started,Deploy succeeded,Deploy failed,Deploy locked,Deploy unlocked
Fly.io
- Use the Fly CLI:
fly webhooks create --app YOUR_APP --url https://api.koalr.com/webhooks/flyio --events deploy - Or use the Fly dashboard → App → Webhooks
AWS CodeDeploy
- Create an EventBridge rule in your AWS account:
- Event source:
aws.codedeploy - Events:
CodeDeploy Deployment State-change Notification
- Event source:
- Set the target to an API Gateway endpoint or Lambda that forwards to
https://api.koalr.com/webhooks/aws-codedeploy - Add your
X-Koalr-Tokenin the HTTP header
GitHub Actions
GitHub Actions events are captured automatically via your existing GitHub integration — no additional webhook setup required. Koalr listens for workflow_run events on your connected repositories.
Deployment data in Koalr
Once connected, deployments appear in:
- Deployments dashboard — timeline, success rate, per-environment breakdown
- Deploy Heatmap — frequency by day/hour heatmap
- Deploy Risk — each deployment linked to its PR risk score and outcome
- DORA Metrics — deployment frequency and change failure rate computed from deployment events
- Incidents — auto-correlated with PagerDuty/Opsgenie incidents occurring within 2 hours
Environment tagging
Koalr distinguishes production from staging/preview deployments. Production deployments count toward DORA metrics; staging deployments are tracked separately. Platform-specific environment detection:
- Vercel:
target === "production"= production; preview deployments are staging - Railway: deployments to the
productionenvironment = production - Netlify:
context === "production"= production; deploy previews = staging - Others: configurable via the environment mapping in Settings → Deployment Sources