🌐 US-Proxy
class="">
Leaderless · Coherent · Redis-compatible

Database consistency at cache speeds.

Your backend doesn't have to be a pain in the rear. Swytch is a leaderless, Redis-compatible cache with database-level consistency. Every node accepts writes. Every node serves reads. Every node sees the same writes in the same order. Self-host it free under AGPL, or connect it to Swytch Cloud — the zero-knowledge control plane. Your existing Redis client connects unchanged.

Get it with €20 Free See pricing 
# macOS / Linux (Homebrew)
brew tap swytchdb/tap
brew install swytch

# macOS / Linux (curl)
curl -fsSL https://getswytch.com/scripts/install.sh | sh

# Windows (PowerShell)
iwr -useb https://getswytch.com/scripts/install.ps1 | iex

Docker: ghcr.io/swytchdb/swytch

What brought you here?

We solved problems we experienced. Your backend doesn't have to be a pain in the rear.

I need to be able to trust my cache

I have to know that what my cache serves is correct, every time.

A cache that never lies →

I need genuine multi-region capability

No shortcuts, no eventual consistency, no rolling back to a single node for truth: I need my cache to be a global mesh.

Active-active →

Some of my cache is a source of truth

Queues, streams, sessions, counters — data with no upstream to rebuild from. It deserves better than AOF.

Durability with Swytch Cloud →

I have four systems doing one job

Sessions, queues, leaderboards, and cache — each with its own upgrade cycle, monitoring, and line on the bill.

Consolidate →

I am way over-provisioned and need something that can auto-tune

My workload changed since starting, but the provisioning policy hasn't. I don't need more to manage; I need a system that can manage itself.

AI-powered caching →

I have remote networks that disconnect on purpose

I manage real-world remote work: ships, field sites, retail floors. A partition is a state my data is designed for, and I need a cache that can keep up.

A holographic cache →

My data stays in the EU

Sovereignty, security, and GDPR are critical. My cache has to comply.

EU sovereignty →

I want to know how you stack up

Tell me about you architectural properties, claim by claim, against Redis Cluster, CockroachDB, and Spanner.

Compare →
FAQ

The obvious questions

Short answers. Longer ones live in the docs.

No primary, no leader, no coordinator. Every node accepts writes and serves reads. No leader election ever happens, because there is no leader to elect — the failure mode is gone by construction. From the application’s perspective each region acts as a single writer, and the writers merge as their histories propagate.

Yes. Swytch speaks the Redis wire protocol (RESP) on port 6379 with Redis 8 semantics. Existing client libraries connect unchanged; existing application code runs unchanged. Joining is a hostname swap.

You choose, per prefix. The default blocks the minority for strict consistency — the behavior Raft users expect. Opt in per prefix and both sides keep writing, then reconcile deterministically when the link heals: not by wall clock, not last-writer-wins, but by the order the causal histories imply.

Because self-hosting should be free, forever, with no rug to pull. AGPL keeps the open-source version genuinely open — unlimited nodes, full engine — while companies that can’t ship AGPL buy a commercial license. That’s the whole business model, in one sentence.

Run the binary.

Two regions in fifteen minutes. AGPL forever, commercial when you ship.

Get it Now Pricing Details

Not deploying today? Drop your address and we’ll send launch notes.