> ## Documentation Index
> Fetch the complete documentation index at: https://site.aspect.build/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported build systems

> Which Aspect Workflows capabilities work with Bazel, Buck2, Pants and other build systems that speak the Remote Execution API.

The [remote cache](/docs/aspect-workflows/platform/features/remote-cache) and [remote execution](/docs/aspect-workflows/platform/features/remote-execution) implement the standard [Remote Execution API](https://github.com/bazelbuild/remote-apis) (REv2), so any build system that speaks it can use them, not only Bazel. [CI runners](/docs/aspect-workflows/platform/features/ci-runners) run any job, whatever builds it. Warming and the Build Results UI read Bazel's own output and work with Bazel only.

| Build system                                 | Remote cache | Remote execution | CI runners | Warming | Build Results UI |
| -------------------------------------------- | ------------ | ---------------- | ---------- | ------- | ---------------- |
| **Bazel**                                    | ✓            | ✓                | ✓          | ✓       | ✓                |
| **Buck2**                                    | ✓            | ✓                | ✓          | —       | —                |
| **Pants**                                    | ✓            | ✓                | ✓          | —       | —                |
| **AOSP** (Soong and ninja, through reclient) | ✓            | ✓                | ✓          | —       | —                |
| Other REv2 clients                           | ✓            | ✓                | ✓          | —       | —                |

Remote execution is available on [Aspect Enterprise](/docs/aspect-workflows/enterprise/overview) today and is coming soon to [Aspect Cloud](/docs/aspect-workflows/cloud/overview).

## What each column means

* **Remote cache and remote execution.** The client reads and writes action results and runs actions on the worker fleet over REv2. [The AOSP benchmark](/docs/aspect-workflows/platform/benchmarks/aosp-remote-execution) is a non-Bazel build on Aspect remote execution.
* **CI runners.** A Workflows runner is a persistent VM that takes jobs in sequence, so whatever a build leaves on the runner's disk is still there for the next job on it. That keeps any build system's local state warm between jobs.
* **Warming.** [Warming](/docs/aspect-workflows/enterprise/ci-runners/warming) archives a runner's Bazel repository cache and output base and restores it on new runners, so a runner's first job doesn't start cold. It works only with Bazel's on-disk layout.
* **Build Results UI.** The [Build Results UI](/docs/aspect-workflows/platform/features/webui), its [REST API](/docs/aspect-workflows/platform/guides/build-results-api) and its [MCP server](/docs/aspect-workflows/platform/guides/build-results-mcp) are built from Bazel's Build Event Protocol, which other build systems don't send.

[Selective delivery](/docs/aspect-workflows/platform/features/selective-delivery) and the [Aspect CLI](/docs/cli/overview) tasks also work with Bazel only.

## Connecting a build system other than Bazel

Point the build system's remote cache and remote execution settings at your deployment's endpoints. Each project documents its own settings:

* Buck2: [Remote execution](https://buck2.build/docs/users/remote_execution/)
* Pants: [Remote caching and execution](https://www.pantsbuild.org/stable/docs/using-pants/remote-caching-and-execution)

The Bazel-specific setup pages, [Aspect Cloud local setup](/docs/aspect-workflows/cloud/local-setup) and [Aspect Enterprise local setup](/docs/aspect-workflows/enterprise/connect/local-setup), don't apply to these clients. [Talk to us](/contact) for the endpoints and credentials to use from another build system.