How Deploy Gate scoring works.

Strake combines evaluated signals into a deterministic deploy verdict. Missing signals lower confidence instead of pretending coverage is complete.

The five signals

Active Incidents

PagerDuty

Open incidents on the service or its dependencies increase deploy risk.

Change Velocity

GitHub Actions

Recent deploy frequency and failures show whether the pipeline is already unstable.

SLO Budget

Datadog / manual SLO

Budget burn and service health help avoid deploying into fragile production.

System Health

Datadog

Latency, errors, and infrastructure stress become part of the PR decision.

Dependency Changes

GitHub Actions

Lockfile movement highlights dependency risk at the deploy boundary.

GO

All evaluated signals are OK. The verdict is strongest when three or more signals are connected.

HOLD

One or more signals are warning. Review the context before merging or approving an override.

CRITICAL

At least one signal is critical. Treat the deploy as unsafe until the condition is resolved or explicitly accepted.

Confidence

HIGH means three or more signals were evaluated. MEDIUM means two signals were evaluated. LOW means one signal was evaluated. Not Evaluated signals are excluded from the decision and shown so teams know what Strake cannot see yet.

Thresholds

Custom thresholds per service are on the roadmap. Today, thresholds are fixed around the signal table above. If your team needs a specific threshold, email rob@strake.dev.