Skip to main content
Every Workflows deployment includes 24/7 monitoring and on-call coverage by Aspect’s infrastructure team. Critical alerts — runner pool saturation, cache outages, control-plane errors — are routed to Aspect automatically and acknowledged inside your standard SLA, so you don’t need a Bazel infrastructure expert on your own rotation. When Aspect needs to act on an incident, access is strictly scoped to resources that the Workflows Terraform module created; nothing outside those boundaries is reachable, and every action lands in your own cloud audit log. If you’d rather handle alerts entirely internally, the Aspect-directed routing can be turned off and your team takes the page directly.

​
What this gives you

  • No Bazel CI on-call. Aspect handles the pages so your engineers don’t have to.
  • Scoped access. Aspect’s on-call only sees Workflows-managed resources, never anything outside the module’s boundary.
  • Auditable in your own cloud. Every Aspect action is logged in your AWS CloudTrail or GCP audit log; the trail is yours.