Skip to content

SYSTEM Cited by 1 source

Slack ReleaseBot

What it is

ReleaseBot is Slack's earlier (2018-era) automated deployment orchestrator for the Webapp backend, canonicalised in Slack Engineering's 2018-11-20 post The Scary Thing About Automating Deploys.

ReleaseBot was the canonical Slack substrate for metrics-based deploys with automatic rollback on Webapp backend — the blueprint that the 2023-2025 Deploy Safety Program then generalised across the company's other deployment systems.

This wiki stub exists to anchor ReleaseBot as the named predecessor of the centralised deployment orchestration system that succeeded it.

Named role in the Deploy Safety Program

Slack's 2025-10-07 Deploy Safety retrospective cites ReleaseBot as one of two direct inspirations for the cross-system centralised orchestration (Source: sources/2025-10-07-slack-deploy-safety-reducing-customer-impact-from-change):

"Aligned further investment toward Slack's centralised deployment orchestration system inspired by ReleaseBot and the AWS Pipelines deployment system to unify the use of metrics-based deployments with automatic remediation beyond Slack Bedrock / Kubernetes to many other deployment systems"

The lineage is:

  1. ReleaseBot (2018) — metrics-based-deploy + automatic rollback for Webapp backend only.
  2. Deploy Safety Program (2023-2025) — generalise the pattern across all deploy substrates.
  3. Centralised deployment orchestration (ongoing) — the unified orchestrator that replaces per-substrate ad-hoc deploy logic.

Core capabilities (from the 2018 Slack post + Deploy Safety context)

  • Metric-watching during deploy phases. The bot watches production metrics during the rollout and can halt or roll back based on alarm signal.
  • Automated rollback on regression. The rollback is triggered by automation, not by human on-call judgement — eliminating the 5-10-minute floor of human-mediated rollback.
  • Webapp-backend-specific. ReleaseBot was scoped to Webapp backend; it did not generalise to frontend / mobile / infra / EC2 until the 2023-2025 program extension.

Why this page is a stub

The 2018 post is not ingested as a canonical wiki source (yet). This page exists to:

  • Give the Deploy Safety Program retrospective a well-formed wiki reference for its named inspiration.
  • Anchor the lineage — ReleaseBot → Deploy Safety → centralised orchestration.
  • Leave room for a fuller canonicalisation once the 2018 post is ingested (future work).

Caveats

  • Stub-level coverage. ReleaseBot's specific metrics, thresholds, phase structure, API, and internals are not canonicalised on this page — they are in the 2018 post that is not yet ingested.
  • The Deploy Safety Program's centralised orchestration is inspired by ReleaseBot, not an extension of its codebase. Whether the new orchestrator reuses ReleaseBot's code or is a green-field re-implementation is not disclosed in the 2025-10-07 retrospective.
  • ReleaseBot is Webapp-backend-only in its 2018 form. Later evolution prior to the 2023 program is not disclosed.

Seen in

Last updated · 470 distilled / 1,213 read