What is Swytch?

Swytch is a Kubernetes-native, Redis-compatible cache that runs beside your application. It is compatible with Redis clients and data structures your application already knows.

With a sidecar, your application connects over localhost or a Unix socket and cache state lives in the sidecar’s memory. If that state is rebuildable, losing it just means refilling the cache.

The operator attaches Swytch to Pods. Outside Kubernetes, run a local process or standalone server.

Each application instance can keep its own Swytch beside it. Each instance subscribes to keys through use, so a shared key can reach the workloads that need it without putting every key on every node.

Only distributed keys pay distributed latency. Local access still has memory and CPU costs. See local and distributed keys.

Atmos is the commercial local-disk option; Swytch Cloud is the network tier. Choose by the failure you need to survive, from a process restart to loss of an entire node. Tiering explains those boundaries.

The progression stays the same: one app, a sidecar, optional tiering, then more nodes, clusters, and regions. All with the standard Redis programming model.

Next: run Swytch on Kubernetes.