Auto Slack & Teams alerts

Keep your team in the loop when Safe-to-Deploy flips from safe → risky → blocked. Alerts are designed for on-call engineers, SREs, and release managers.

Slack channel alerts

Post Safe-to-Deploy decisions into a Slack channel using a simple incoming webhook.

Available today

Alerts on risky and blocked deployments.
Includes service, environment, risk level, and reason.
Ideal for on-call or release-coordination channels.

Microsoft Teams (roadmap)

Future support for posting the same alerts into Teams channels using incoming webhooks or connectors.

Coming soon

Mirrored payloads from Slack alerts.
Per-team routing and channel targeting.
Configurable per-environment policies.

How alerts are triggered

Whenever the Safe-to-Deploy engine evaluates a deployment, it produces a decision like safe, risky, or blocked. Alert channels can subscribe to these events.

A CI/CD pipeline calls the Safe-to-Deploy API or deployment-risk API.
The backend decides the outcome (safe / risky / blocked) based on SLOs, recent incidents, and deployment risk.
If the outcome is risky or blocked, the platform sends a notification to all matching channels (e.g. Slack webhooks) configured for that organisation.

Configure Slack alerts for your organisation

Configuration is done in the web UI by an organisation admin or risk policy manager. No code changes are required for your engineers.

In Slack, create an Incoming Webhook for the channel where you want Safe-to-Deploy alerts to appear.
In this platform, go to Settings → Notifications → Slack alerts (or ask your SRE admin to do this).
Paste the Slack webhook URL and choose which decisions should trigger alerts: Blocked, Risky, or both.
Save the configuration and (optionally) send a Test alert from the UI to confirm everything is wired up.

Permissions
Only organisation admins or users with the Risk Policy Manager role should be able to change alert destinations. Regular users will still see the alert history and Safe-to-Deploy decisions, but cannot change who gets notified.

Example Slack message

This is roughly what a blocked deployment alert looks like once configured:

{
  "text": "⛔ Deployment blocked for *Network* in *prod*",
  "attachments": [
    {
      "color": "#dc2626",
      "fields": [
        { "title": "Service",      "value": "Network",       "short": true },
        { "title": "Environment",  "value": "prod",          "short": true },
        { "title": "Risk level",   "value": "red / blocked", "short": true },
        { "title": "Reason",       "value": "SLO burn rate too high" }
      ]
    }
  ]
}

Roadmap

Microsoft Teams connectors for the same Safe-to-Deploy events.
Per-service and per-environment routing rules.
Configurable templates for Slack / Teams payloads.
Alert noise-reduction: cooldowns and deduplication.

← Back to Safe-to-Deploy cockpit