---
title: "Redis cache for your app in 2026: added by your AI, over MCP"
url: https://while.sh/en/guides/add-redis-cache/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-19
---

# Add a Redis-compatible cache to your app with your AI (2026)

Is your app slowing down under load? Ask your AI for a cache: connected to while over MCP, it declares one in three lines, and your app finds it in REDIS_URL.

> **The short version.** Over MCP, your AI adds a Redis-compatible cache to your app, with no server to manage. Its address arrives in REDIS_URL, password included. What matters, like deleting a database, waits for a person's approval.

## Prerequisites

- A Node.js, Python or Go app.
- An AI that works in a terminal: Claude Code, Codex, Cursor or Gemini CLI.

## Step 1: Give your AI this message

Open your AI in your app's folder, and paste this message into it:

```text titre="The message to give your AI"
Connect to while with my account (while.sh/agents), then put my app on while.
```

Your AI adds while's MCP server itself. If it asks you to, restart it. On the first call to while, a page opens in your browser. In Claude Code, if it doesn't open, type /mcp, choose while, then Authenticate. On that page, choose "A new app", then click Authorize.

## Step 2: Open your app

Your AI gives you your app's address, for example `https://mon-appli.while.cloud`, over HTTPS.

## What your AI does

It adds three lines to while.yaml:

```yaml titre="while.yaml"
apiVersion: while/v1
project: mon-appli
services:
  - name: web
    port: 3000
    health:
      path: /health
caches:
  - name: cache
    memory: 256Mi
```

The last three lines declare a 256 MiB Redis-compatible cache. Its address, password included, reaches your app in `REDIS_URL` (source 1):

```js titre="server.js"
import { createClient } from 'redis';

const cache = createClient({ url: process.env.REDIS_URL });
await cache.connect();
```


<figure class="illus"><img src="/illustrations/guide-fonction-garde-1200.webp" srcset="/illustrations/guide-fonction-garde-768.webp 768w, /illustrations/guide-fonction-garde-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="A Redis-compatible cache with while: credentials kept out of the AI's reach, every call logged in the history, a person's approval for what matters and a daily backup, in France" /><figcaption>Around every app, while keeps the credentials, the history, the approvals and the backups.</figcaption></figure>

## Make the cache bigger

> You, to your AI: Increase the cache to 512 MiB.

Your AI changes `memory` in while.yaml. When the cache is full, the keys that have gone unused the longest make room for new ones.

## Keep the data after a restart

> You, to your AI: Turn the cache into a job queue that never loses anything.

Your AI makes the cache durable: its data is written to disk, and no key is evicted.

## Add a database

> You, to your AI: Add a PostgreSQL database.

Your AI declares the database in while.yaml, and its address reaches your code in `DATABASE_URL`. The database is backed up every day, with a way back to a precise moment over 14 days.

## Restrict your app to your colleagues

> You, to your AI: Restrict the app to people in the company.

Your AI makes the service internal:

```yaml titre="while.yaml"
    access: internal
```

Then it asks for the Access role for your domain, @acme.com, on this app, and a person in your organization approves it.

Once your Google Workspace or Microsoft 365 is linked to while, on the Pro plan, your colleagues sign in with their usual account, and your code receives their name and email address, with no sign-in page to write.

## Go back to the previous version

> You, to your AI: Go back to the previous version.

In the 30 minutes after a production release, the previous version comes back in a second. After that, it takes a few seconds. Once the previous version is back, your AI reads what broke in while's logs, fixes it and deploys again.

## Next steps

- [Deploy a Node.js API and its PostgreSQL database](/en/guides/deploy-node-api-postgresql/)
- [Run a scheduled job](/en/guides/run-cron-job/)
- [Compare the hosts that have an MCP server](/en/comparisons/mcp-hosting-claude-code/)

## Sources

1. [Redis, connecting a Node.js app with the redis package (createClient and its url option)](https://redis.io/docs/latest/develop/clients/nodejs/connect/), 2026-11-02

## Questions

### Is it really Redis?

It's Valkey, which is Redis-compatible: any Redis client connects to it as is.

### Is the cache protected?

Yes, by a password, included in REDIS_URL.

### Can I use it for a job queue?

Yes, with a durable cache: nothing is lost on restart, and no key is evicted.

### Where do my app and its data run?

In France, at Nextmap. The database is backed up every day, with a way back over 14 days, once a person approves.

### What happens if a version breaks something?

In the 30 minutes after a production release, the previous version comes back in a second, then in a few seconds.
