engflow
Choose Tuist when you want an EngFlow alternative that puts Bazel's remote cache, build events, and test results on the same platform as your Xcode, Gradle, and Elixir builds. Optimize the project first, then its execution environment. Start with [Tuist Bazel
Claude Code
$ npx -y skills add tuist/tuist --agent claude-code
Cursor
Cursor also loads subagents from .claude/agents, so copy this file there to use it in Cursor.
Agent definition
engflow.mdEngFlow alternative: Tuist for Bazel caching, remote execution, and build insights
Choose Tuist when you want an EngFlow alternative that puts Bazel's remote cache, build events, and test results on the same platform as your Xcode, Gradle, and Elixir builds. Optimize the project first, then its execution environment. Start with [Tuist Bazel Cache](/en/docs-markdown/guides/features/cache/bazel-cache): `tuist bazel setup` points Bazel at Tuist's remote cache and Build Event Service through a credential helper, and your `BUILD` files and commands stay the same.
What overlaps
EngFlow describes four product lines: [Remote Execution, Remote Caching, CI Runners, and Build and Test Observability](https://blog.engflow.com/2026/10/12/cursor-origin-launch-partner). Its [remote execution](https://www.engflow.com/product/remoteExecution) supports clients of the open-source Remote Execution API, including Bazel, Pants, Please, Reclient, and Soong, with workers on Linux, macOS, and [Windows](https://docs.engflow.com/re/client/windows.html). Its [Gradle cache plugin](https://docs.engflow.com/remote-caching/engflow-gradle-cache-plugin.html) is in beta.
EngFlow [does not share infrastructure between customers](https://www.engflow.com/product/remoteExecution). Its [glossary](https://docs.engflow.com/glossary.html) defines fully managed clusters in an EngFlow-created AWS or GCP account, co-managed clusters in the customer's own cloud account, and self-managed clusters that customers operate themselves. The [Build and Test UI](https://www.engflow.com/product/buildDashboard) covers invocation results, profiles, critical paths, and flaky-test status, and EngFlow documents a beta [MCP server](https://docs.engflow.com/web_ui/integrations/mcp.html) with the same data. EngFlow publishes Apache-2.0 tools such as its [credential helper](https://github.com/EngFlow/auth) and the [Bazel Invocation Analyzer](https://github.com/EngFlow/bazel_invocation_analyzer); the cluster services run under a [contract license](https://docs.engflow.com/re/config/license-server.html), and self-managed customers receive binaries.
Both products reuse compatible Bazel action outputs through a remote cache and offer remote execution as a separate service. Cache reuse is not remote execution: an action missing from the cache still has to run somewhere.
Self-host software you can read
Tuist is source-available: the code behind the service you use is [public](https://github.com/tuist/tuist). The server is licensed under FCL-1.0-MIT, under which each version becomes MIT two years after release; the Kura cache nodes are AGPL-3.0, and the CLI is MIT. See [Openness](/marketing-markdown/openness) for what each license allows. A team that [self-hosts the Tuist server](/en/docs-markdown/guides/server/self-host/server) or [cache nodes](/en/docs-markdown/guides/features/cache/self-hosting) can read, audit, patch, and build the software it runs. Running a self-hosted server requires an Enterprise license.
EngFlow also supports self-hosting: its self-managed clusters and its Free tier run on the customer's own infrastructure. It provides them as binaries under its contract license, and its public repositories cover client tools such as the credential helper rather than the cluster services. If reading or modifying the infrastructure you operate matters to your team, that is the difference to weigh.
Compare the Bazel workflow
| Requirement | Tuist | EngFlow evidence to evaluate | | --- | --- | --- | | Reuse Bazel outputs | [Bazel Cache](/en/docs-markdown/guides/features/cache/bazel-cache) shares compatible action outputs between developer machines, CI, and agents, without requiring Tuist Runners. | EngFlow Remote Caching serves Bazel and other Remote Execution API clients from the customer's cluster. Compare locality, transfer, retention, and diagnostics. | | Execute actions on remote workers | `tuist bazel setup --remote-execution` sends Bazel actions to Tuist's Linux executors, which read from and write to the same remote cache. Actions need to run on the executors' Linux toolchain rather than local host tools. | EngFlow documents Linux, macOS, and Windows workers, with container images for Linux. Compare the platforms your actions need. | | Explain a Bazel build | [Build Insights](/en/docs-markdown/guides/features/build-insights/bazel) records invocations, profiles, critical paths, and cache behavior, with authorized [MCP access](/en/docs-markdown/guides/features/agentic-coding/mcp) for agents. | EngFlow's Build and Test UI shows invocations, critical paths, and flakiness; its MCP server is in beta and enabled per cluster. Compare tool coverage and permissions. | | Operate across several toolchains | Tuist also supports Xcode, Gradle, and Elixir insights; caching and test acceleration vary by integration. | EngFlow is centered on Remote Execution API build systems, with a beta Gradle cache plugin. Verify any other integration directly. | | Deployment | Hosted Tuist, or [self-hosted server](/en/docs-markdown/guides/server/self-host/server) on the Enterprise plan and self-hosted [cache nodes](/en/docs-markdown/guides/features/cache/self-hosting). | Fully managed, co-managed in the customer's cloud account, or self-managed. Compare who operates the cluster and who pays the cloud bill. | | Commercial terms | Feature usage is metered; see [pricing](/marketing-markdown/pricing). | EngFlow's [pricing page](https://www.engflow.com/product/pricing) lists a Free tier limited to one machine and 32 cores on Linux, and Enterprise by custom quote. |
A dashboard built for the whole team
We put particular care into the dashboard's design and interaction details, and we think it is where Tuist stands out most against EngFlow. That is our view as the vendor, not an independent review, so check it against your own builds. [Tuist's own dashboard](https://tuist.dev/tuist/tuist) is public. Specific things to look at:
- **Cache problems you can te
Read more
EngFlow alternative: Tuist for Bazel caching, remote execution, and build insights
Choose Tuist when you want an EngFlow alternative that puts Bazel's remote cache, build events, and test results on the same platform as your Xcode, Gradle, and Elixir builds. Optimize the project first, then its execution environment. Start with [Tuist Bazel Cache](/en/docs-markdown/guides/features/cache/bazel-cache): `tuist bazel setup` points Bazel at Tuist's remote cache and Build Event Service through a credential helper, and your `BUILD` files and commands stay the same.
What overlaps
EngFlow describes four product lines: [Remote Execution, Remote Caching, CI Runners, and Build and Test Observability](https://blog.engflow.com/2026/10/12/cursor-origin-launch-partner). Its [remote execution](https://www.engflow.com/product/remoteExecution) supports clients of the open-source Remote Execution API, including Bazel, Pants, Please, Reclient, and Soong, with workers on Linux, macOS, and [Windows](https://docs.engflow.com/re/client/windows.html). Its [Gradle cache plugin](https://docs.engflow.com/remote-caching/engflow-gradle-cache-plugin.html) is in beta.
EngFlow [does not share infrastructure between customers](https://www.engflow.com/product/remoteExecution). Its [glossary](https://docs.engflow.com/glossary.html) defines fully managed clusters in an EngFlow-created AWS or GCP account, co-managed clusters in the customer's own cloud account, and self-managed clusters that customers operate themselves. The [Build and Test UI](https://www.engflow.com/product/buildDashboard) covers invocation results, profiles, critical paths, and flaky-test status, and EngFlow documents a beta [MCP server](https://docs.engflow.com/web_ui/integrations/mcp.html) with the same data. EngFlow publishes Apache-2.0 tools such as its [credential helper](https://github.com/EngFlow/auth) and the [Bazel Invocation Analyzer](https://github.com/EngFlow/bazel_invocation_analyzer); the cluster services run under a [contract license](https://docs.engflow.com/re/config/license-server.html), and self-managed customers receive binaries.
Both products reuse compatible Bazel action outputs through a remote cache and offer remote execution as a separate service. Cache reuse is not remote execution: an action missing from the cache still has to run somewhere.
Self-host software you can read
Tuist is source-available: the code behind the service you use is [public](https://github.com/tuist/tuist). The server is licensed under FCL-1.0-MIT, under which each version becomes MIT two years after release; the Kura cache nodes are AGPL-3.0, and the CLI is MIT. See [Openness](/marketing-markdown/openness) for what each license allows. A team that [self-hosts the Tuist server](/en/docs-markdown/guides/server/self-host/server) or [cache nodes](/en/docs-markdown/guides/features/cache/self-hosting) can read, audit, patch, and build the software it runs. Running a self-hosted server requires an Enterprise license.
EngFlow also supports self-hosting: its self-managed clusters and its Free tier run on the customer's own infrastructure. It provides them as binaries under its contract license, and its public repositories cover client tools such as the credential helper rather than the cluster services. If reading or modifying the infrastructure you operate matters to your team, that is the difference to weigh.
Compare the Bazel workflow
| Requirement | Tuist | EngFlow evidence to evaluate | | --- | --- | --- | | Reuse Bazel outputs | [Bazel Cache](/en/docs-markdown/guides/features/cache/bazel-cache) shares compatible action outputs between developer machines, CI, and agents, without requiring Tuist Runners. | EngFlow Remote Caching serves Bazel and other Remote Execution API clients from the customer's cluster. Compare locality, transfer, retention, and diagnostics. | | Execute actions on remote workers | `tuist bazel setup --remote-execution` sends Bazel actions to Tuist's Linux executors, which read from and write to the same remote cache. Actions need to run on the executors' Linux toolchain rather than local host tools. | EngFlow documents Linux, macOS, and Windows workers, with container images for Linux. Compare the platforms your actions need. | | Explain a Bazel build | [Build Insights](/en/docs-markdown/guides/features/build-insights/bazel) records invocations, profiles, critical paths, and cache behavior, with authorized [MCP access](/en/docs-markdown/guides/features/agentic-coding/mcp) for agents. | EngFlow's Build and Test UI shows invocations, critical paths, and flakiness; its MCP server is in beta and enabled per cluster. Compare tool coverage and permissions. | | Operate across several toolchains | Tuist also supports Xcode, Gradle, and Elixir insights; caching and test acceleration vary by integration. | EngFlow is centered on Remote Execution API build systems, with a beta Gradle cache plugin. Verify any other integration directly. | | Deployment | Hosted Tuist, or [self-hosted server](/en/docs-markdown/guides/server/self-host/server) on the Enterprise plan and self-hosted [cache nodes](/en/docs-markdown/guides/features/cache/self-hosting). | Fully managed, co-managed in the customer's cloud account, or self-managed. Compare who operates the cluster and who pays the cloud bill. | | Commercial terms | Feature usage is metered; see [pricing](/marketing-markdown/pricing). | EngFlow's [pricing page](https://www.engflow.com/product/pricing) lists a Free tier limited to one machine and 32 cores on Linux, and Enterprise by custom quote. |
A dashboard built for the whole team
We put particular care into the dashboard's design and interaction details, and we think it is where Tuist stands out most against EngFlow. That is our view as the vendor, not an independent review, so check it against your own builds. [Tuist's own dashboard](https://tuist.dev/tuist/tuist) is public. Specific things to look at:
- **Cache problems you can te
Tuist is a build platform for engineering teams and their coding agents. It works with Xcode, Gradle, Bazel, Elixir, and Rust builds. Features vary by toolchain: Rust compilation caching is experimental, and Once support is in canary.
Other agents on tuist.
More agents from other plugins.
cavecrew-builder
AgentSurgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard…
Questions about engflow.
- Which coding agents can use engflow?
- engflow installs in Claude Code and Cursor: each loads subagents from .claude/agents, so copy the file there. Flowy's auto-invocation runs in Claude Code only.

