diff --git a/docs/repo-docs/core-concepts/remote-caching.mdx b/docs/repo-docs/core-concepts/remote-caching.mdx
index c62818ab4b3b6..e0680f260c076 100644
--- a/docs/repo-docs/core-concepts/remote-caching.mdx
+++ b/docs/repo-docs/core-concepts/remote-caching.mdx
@@ -61,9 +61,9 @@ What if you could share a single Turborepo cache across your entire team (and ev
   }}
 />
 
-By working with providers like [Vercel](#vercel), Turborepo can securely communicate with a remote cache - a cloud server that stores the results of your tasks.
+Turborepo can securely communicate with a remote cache - a cloud server that stores the results of your tasks. This can save enormous amounts of time by **preventing duplicated work across your entire organization**.
 
-This can save enormous amounts of time by **preventing duplicated work across your entire organization**.
+Remote Caching is free and can be used with both [managed providers](https://turbo.build/repo/docs/core-concepts/remote-caching#managed-remote-cache-with-vercel) or as a [self-hosted cache](https://turbo.build/repo/docs/core-concepts/remote-caching#self-hosting).
 
 <Callout>
   Remote Caching is a powerful feature of Turborepo, but, with great power,
@@ -76,6 +76,8 @@ This can save enormous amounts of time by **preventing duplicated work across yo
 
 ## Vercel
 
+[Vercel Remote Cache](https://vercel.com/docs/monorepos/remote-caching) is free to use on all plans, even if you do not host your applications on Vercel. Follow the steps below to enable Remote Caching for your repository.
+
 ### For Local Development
 
 To link your local Turborepo to your Remote Cache, authenticate the Turborepo CLI with your Vercel account: