---
title: "Deploy Turborepo Remote Cache"
description: "Open source implementation of the Turborepo custom remote cache server."
category: "Other"
url: https://railway.com/deploy/tRFTHR
---

# Deploy Turborepo Remote Cache

Open source implementation of the Turborepo custom remote cache server.

**[Deploy Turborepo Remote Cache on Railway](https://railway.com/template/tRFTHR)**

- **Creator:** Thalles Passos's Projects
- **Category:** Other
- **Total deploys:** 66

## Template content

### Turborepo Remote Cache https://pub-be57d7e4de8e43cbb04106b33b260bf4.r2.dev/turborepo.svg

- **Image:** ducktors/turborepo-remote-cache
- **Public domain:** Yes

## Documentation

# 🚂 Self-Hosted Turborepo Remote Cache on Railway

Deploy a secure, self-hosted Turborepo remote cache on Railway with just a few clicks. This alternative provides you full control over your build cache infrastructure. 🔒

## Setup Guide 

### 1. Deploy to Railway with One Click 🎯  
Deploy to Railway by clicking the big purple `Deploy Now` button 

### 2. Configure Turborepo Project 🛠️

After deploying, you'll need to configure your Turborepo project to use the new remote cache:

1. Open your Railway project we just deployed
2. Select the service with the Turborepo logo
3. Navigate to the "Variables" tab
4. Copy these required environment variables:
  - `TURBO_TOKEN`: Authentication token
  - `TURBO_API_URL`: Remote cache endpoint

### 3. Update Turborepo Configuration 📝

Time to modify your code to use the remote cache, but trust me, it's easy.  
Set the following environment variables that you copied from the Railway project we just deployed:

```properties
# When deploying your code on the same Railway project as this template, you can use ${{"Turborepo Remote Cache".TURBO_TOKEN}}
TURBO_TOKEN={TURBO_TOKEN}
# When deploying your code on the same Railway project as this template, you can use ${{"Turborepo Remote Cache".TURBO_API_URL}}
TURBO_API={TURBO_API_URL}
# Leave this as is
TURBO_TEAM=railway-remote-cache
```

And in case you prefer `.env` file instead of filling out those env variables in your shell everytime, you can use the `dotenv-cli` package.  
Modify the `build` script in your `package.json` root to include the following:

```bash
dotenv -e .env -- turbo build
```

### 4. Use Remote Cache 🎉

Run your Turborepo commands as normal. The remote cache will be automatically utilized:

```bash
turbo build
```
You can verify the remote cache is working by checking your Turborepo build logs. When successful, you'll see:

```
Remote caching enabled
```

## Troubleshooting 🔍

### Common Issues
- Verify Railway deployment is running and accessible
- Double-check that your token and API URL are correctly configured
- Test the setup using the [example reference project](https://github.com/ThallesP/remote-cache-railway) to validate configuration and rule out any potential template-specific issues

### Need More Help?
Join Railway's [Discord community](https://discord.gg/railway) for additional support and troubleshooting. 

## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — [Jul'26] Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/tRFTHR