Recached — Rust Cache for Backend and Browser

⚡

Zero-latency local reads

The browser WASM module holds a live copy of the cache in local memory. Reads never leave the browser — no network hop, no round-trip.

🔄

Automatic WebSocket sync

Any mutation on the server is pushed to all connected browser instances instantly. Any write from the browser is pushed to the server and fanned out to other tabs.

🦀

Redis-compatible server

Speaks RESP on port 6379. Drop it in front of any Redis client — ioredis, node-redis, redis-py — with no code changes.

🌐

Offline-first browser cache

IndexedDB persistence means the cache survives page refreshes. Users see their data immediately, before any network request completes.

📡

Cross-tab sync

BroadcastChannel support means all tabs in the same browser share mutations automatically, with no server connection required.

🔒

Production-ready server

TLS, Prometheus metrics, password auth, IP allowlists, connection limits, eviction policies, and observable keys out of the box.

What is Recached?

Recached is an in-memory cache written in Rust that solves a problem no other cache tool addresses: the same engine runs natively on your server and as WebAssembly inside the browser, with both sides kept in sync over WebSockets.

On the backend, it speaks RESP on port 6379 — any Redis client works against it today without code changes. In the browser, you import it as a .wasm module and get zero-latency local reads with automatic background sync to the server.

typescript

import init, { RecachedCache } from 'recached-edge'

await init()
const cache = new RecachedCache()

// Connect to the server — mutations sync both ways automatically
cache.connect('ws://localhost:6380')

cache.set('user:theme', 'dark')
console.log(cache.get('user:theme')) // 'dark' — read from local WASM memory, 0 ms

// When your backend does SET user:theme light over RESP,
// this browser instance receives the update automatically.
cache.watch('user:theme', (newValue) => {
  document.body.dataset.theme = newValue ?? 'light'
})

No polling. No extra state management library. No round-trips for reads. The server is your backend's cache; the WASM module is your frontend's cache; the WebSocket is the invisible sync layer between them.

Recached ⚡Cache that runs everywhere.