Overview

Aspect Workflows is built from a set of independent features. Some target build performance, some target developer experience around code review and delivery, and some make day-to-day operation easier. Each feature has its own page in this section — this overview is a roadmap.

​

Build and CI performance

• CI runners — Self-hosted, NVMe-backed runners that keep Bazel’s output base warm across jobs. Pre-warmed via a runner-image build pipeline so cold-start overhead is eliminated. Pool scales to zero when idle.
• Remote cache — A content-addressable Bazel cache co-located with your runners in the same VPC.
• Remote execution — An optional worker pool that executes Bazel actions in parallel across many machines on a cache miss.
• External remote cache and execution — Expose the same cache and execution clusters to developer workstations and external build clients over the internet.

​

Selective delivery, Code review, and insights

• Selective delivery — Re-deploys only the services whose Bazel-built outputs actually changed, driven by the same build graph you already trust.
• Code review integration — Streams build, test, and lint results to your pull requests as the job runs, with inline annotations and one-click suggested fixes.
• Web UI — A dashboard showing cache hit rate, test failure trends, runner performance, and deployment history.

​

Operations

• Workflows support and alerting — 24/7 monitoring of the deployment by Aspect, with proactive alerts and incident response.

​

Browse live examples

The aspect-build/bazel-examples repo runs on Aspect Workflows across all four supported CI providers. Source lives in two places: GitHub (used by the GitHub Actions, Buildkite, and CircleCI pipelines) and GitLab (used by the GitLab CI pipeline). For per-task examples of what aspect <task> posts back to a PR — Buildkite annotations, GitHub Status Checks, and a sample PR task summary comment — see Running tasks in CI → Live examples.