Skip to content

SYSTEM Cited by 1 source

Slack Bedrock

What it is

Slack Bedrock is Slack's internal compute platform — Slack-branded PaaS over Kubernetes that hosts Slack's containerised workloads. Canonicalised in Slack Engineering's post Applying Product Thinking to Slack's Internal Compute Platform (linked from the 2025-10-07 Deploy Safety retrospective).

The platform is also the substrate that hosts the first fully- automated metrics-based-deploy-plus-automatic-rollback regime on Webapp backend (see patterns/automated-detect-remediate-within-10-minutes).

This wiki stub exists to anchor Bedrock as the named internal compute substrate under the Slack Deploy Safety Program's first-fully-automated-deploy-substrate.

Named role in the Deploy Safety Program

Slack's 2025-10-07 Deploy Safety retrospective positions Bedrock as the first substrate where the 10-min auto-remediate goal was reached, with the intent to lift the same target "beyond Slack Bedrock / Kubernetes to many other deployment systems" (Source: sources/2025-10-07-slack-deploy-safety-reducing-customer-impact-from-change).

This positions Bedrock/K8s as both:

  • The substrate on which the Deploy Safety Program's first fully-automated metrics-based-deploy-with-automatic-rollback regime was built (Webapp backend).
  • The baseline from which the centralised deployment orchestration system is expected to generalise out (to Webapp frontend, infra, EC2, Terraform).

Slack's 2022-era blog post How Slack adopted Karpenter to increase operational and cost efficiency (hosted on the AWS containers blog) discloses that Slack adopted Karpenter for node-level autoscaling on its Kubernetes infrastructure — indicating the Bedrock substrate runs on EKS with Karpenter-managed node pools. (This is a Bedrock-adjacent disclosure; the 2025-10-07 post links to it rather than re-disclosing the internals.)

Why this page is a stub

The Bedrock architecture 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 substrate.
  • Anchor the lineage — Kubernetes → Slack Bedrock → Deploy Safety Program's first-automated-deploy substrate.
  • Leave room for a fuller canonicalisation once the Bedrock post is ingested (future work).

Caveats

  • Stub-level coverage. Bedrock's internals — control plane, tenancy model, service mesh, observability substrate, rollout mechanism, multi-tenancy, etc. — are not canonicalised on this page.
  • The relationship between Bedrock and the centralised orchestration system is directional. Bedrock is the first substrate where metrics-based-deploy-with-auto-rollback works end-to-end; the centralised orchestration system is being built to generalise that substrate's deploy-safety capabilities to other substrates. Whether the orchestrator runs on Bedrock, alongside Bedrock, or inside Bedrock is not disclosed.

Seen in

Last updated · 470 distilled / 1,213 read