diff --git a/site/docs/remote-execution.md b/site/docs/remote-execution.md
index e334206399ac03..4c0dd35ff66cdd 100644
--- a/site/docs/remote-execution.md
+++ b/site/docs/remote-execution.md
@@ -23,26 +23,9 @@ Bazel uses an open-source
 [gRPC protocol](https://github.com/bazelbuild/remote-apis)
 to allow for remote execution and remote caching.
 
-## Remote execution services
-
-To run Bazel with remote execution, you can use one of the following:
-
-*   Manual
-    *   Use the
-        [gRPC protocol](https://github.com/bazelbuild/remote-apis)
-        directly to create your own remote execution service.
-*   Self-service
-    *   [Buildbarn](https://github.com/buildbarn)
-    *   [Buildfarm](https://github.com/bazelbuild/bazel-buildfarm)
-    *   [BuildGrid](https://gitlab.com/BuildGrid/buildgrid)
-    *   [Scoot](https://github.com/twitter/scoot)
-*   Commercial
-    *   [EngFlow Remote Execution](https://www.engflow.com) -- Remote execution
-        and remote caching service. Can be self-hosted or hosted.
-    *   [BuildBuddy](https://www.buildbuddy.io) -- Remote build execution,
-        caching, and results UI.
-    *   [Flare](https://www.flare.build) --  Providing a cache + CDN for Bazel
-        artifacts and Apple-focused remote builds in addition to build & test analytics.
+For a list of commercially supported remote execution services as well as
+self-service tools, see
+[Remote Execution Services](https://www.bazel.build/remote-execution-services.html)
 
 ## Requirements