Verified apps
Smoke-tested Redis drop-in compatibility with real applications.
Apps that speak Redis and expect Postgres can often point their Redis URL at PostRESP instead of a separate Redis/Valkey process. This page tracks application-level smoke tests — distinct from the Valkey suite on Compatibility.
Marketing may say “verified with …” only for rows marked Verified below.
What “verified” means
A row is verified when someone has:
- Run a realistic install of the app (version pinned) against PostRESP.
- Exercised the Redis-backed features the app actually uses (cache, sessions, queues, locks — whatever that release needs).
- Recorded storage mode (
unlogged/logged), date checked, and known gaps (missing commands, TTL quirks, etc.).
| Status | Meaning |
|---|---|
| Verified | Smoke-tested; notes list any caveats |
| Partial | Works for some paths; gaps documented |
| Untested | Candidate — not yet run against PostRESP |
Matrix
| App | Version | Status | Notes | Last checked |
|---|---|---|---|---|
| Immich | — | Untested | Postgres + Redis stack; strong self-hoster candidate | — |
| Outline | — | Untested | Wiki; typically Postgres + Redis | — |
| Plausible | — | Untested | Analytics; Redis used in some deployments | — |
| Ghost | — | Untested | May use Redis for cache/adapters depending on setup | — |
| BullMQ / job queues | — | Untested | Needs broader command surface (lists, sorted sets, …) | — |
Nothing here is verified yet — the table is the checklist. Contributions welcome: open a PR that fills a row after a real smoke test (include version, storage mode, what you exercised, and gaps).
Related
- Commands — what Redis commands PostRESP implements today
- Compatibility — Valkey test-suite progress
- Getting started — Docker and extension install