---
title: Remote cache
order: 17
description: "A CI-only backend that shares content-addressed artifacts across runners: a cold machine replays a build another runner already did instead of rebuilding. Every remote artifact must be signed by a trusted key."
tags: [glossary, execution-and-caching]
---

# Remote cache

A CI-only backend that shares content-addressed artifacts across runners: a cold
machine replays a build another runner already did instead of rebuilding. Every
remote artifact must be signed by a trusted key.

## Elsewhere

Bazel, Gradle and Turborepo remote caches share artifacts between every machine, laptops
included. A magus remote cache is for CI runners only, and it refuses any artifact a trusted
key did not sign.

## Example

`magus config cache` shows which cache backends this workspace reads and writes.

```sh
magus config cache
```

## Used in

<!-- BEGIN GLOSSARY USAGE (generated by glossary-usage-generate from the knowledge graph; edit the generator, not this list) -->

In the docs:

- [Connecting to the remote cache](../concepts/cache.md#connecting-to-the-remote-cache)
- [Remote cache](../concepts/telemetry.md#remote-cache)

<!-- END GLOSSARY USAGE -->

## See also

- [Cache](cache.md)
- [Remote caching](../concepts/cache/remote.md)