django-cachex
Valkey and Redis cache backend for Django, with a Django admin UI for cache inspection.
Installation
pip install django-cachex[valkey-py]
Quick Start
CACHES = {
"default": {
"BACKEND": "django_cachex.cache.ValkeyCache",
"LOCATION": "valkey://127.0.0.1:6379/1",
}
}
What's in the box
- One package for both Valkey and Redis, default and Sentinel and Cluster.
- Sync and async are first-class. The async cache also works from sync code.
- Hash, list, set, sorted set, and stream operations on the cache object.
- TTL and pattern helpers (
ttl(),expire(),keys(),delete_pattern()). - Distributed locks:
cache.lock(). - Weighted semaphores:
cache.semaphore()for budget-based concurrency gating (counting and weighted, in-process and distributed). - Lua scripting with automatic key prefixing and value encoding/decoding.
- Pluggable serializers (Pickle, JSON, MsgPack, ormsgpack, orjson) and compressors (Zlib, Gzip, LZ4, LZMA, Zstandard), each with fallback chains for safe migrations.
- Cache stampede prevention (TTL-based XFetch).
- Two composite backends:
StreamCache(cross-pod stream-synchronized in-memory cache) andTieredCache(L1/L2 with TTL propagation). - Django
LocMemCacheandDatabaseCacheextensions with the same data-structure ops and admin support. - Optional Rust I/O driver (PyO3 + tokio + redis-rs) under the same
RespCacheAPI. Free-threaded CPython (3.14t) supported. Experimental. - Optional
valkey-glideadapter: Valkey's official Rust-cored client, exposed asValkeyGlideCache. Experimental. - Django admin UI for browsing keys, inspecting values, editing, and flushing. See below.
Cache Admin
Add django_cachex.admin to your INSTALLED_APPS to enable the cache admin interface:
INSTALLED_APPS = [
# ...
"django_cachex.admin",
]
Browse all configured caches, search and filter keys by type, and manage values directly:
Features:
- Browse all configured cache backends (Valkey, Redis, LocMemCache, DatabaseCache, and more)
- Search keys with wildcard patterns (
user:*,*:session) - Filter by key type (string, list, set, hash, zset, stream)
- View and edit values with type-specific operations
- Inspect and modify TTL
- View server info and memory statistics
- Flush caches
Documentation
Full documentation at oliverhaas.github.io/django-cachex
Requirements
- Python 3.14+ (free-threaded supported)
- Django 6.0+
- valkey-py 6.1+ or redis-py 6.0+
- Valkey 7.0+ or Redis 6.0+ on the server (the admin's compare-and-swap
edits use
SET ... KEEPTTL, which lands in Redis 6.0)
The Rust I/O driver is optional and experimental: interfaces and
behavior may still change, and it has seen less production testing than
the redis-py/valkey-py paths. To opt in, install with the redis-rs
extra (pip install django-cachex[redis-rs]); this pulls in the
django-cachex-redis-rs companion package. Prebuilt wheels are published
for Linux x86_64, Linux aarch64, macOS arm64, and Windows amd64, on
both cp314 and cp314t (free-threaded). Without the extra, the
RedisRsCache backends are unavailable but everything else works.
The valkey-glide adapter is also optional and experimental, with the
same caveats. Install with the valkey-glide extra
(pip install django-cachex[valkey-glide]) to enable
ValkeyGlideCache; it pulls in valkey-glide-sync and valkey-glide,
the official Rust-cored Valkey client. cp314 GIL only; no free-threaded
wheels yet. Cluster is supported via ValkeyGlideClusterCache; Sentinel
is not currently exposed (valkey-glide itself does not ship a Sentinel
client).
Acknowledgments
This project started from django-redis and Django's official Redis cache backend. Some serializer and compressor utility code is derived from django-redis, licensed under BSD-3-Clause. The admin UI was inspired by django-redisboard.
The Rust I/O driver and async bridge are heavily inspired by, and in places directly adapted from, django-vcache (MIT, by David Burke / GlitchTip). The fork-safe tokio runtime, the RedisRsAwaitable deferred-loop-binding pattern, and the multiplexed-connection design all originate there.
I also want to mention django-valkey and dj-cache-panel, which I never really used, but are newer and interesting efforts of similar goals as this package has.
License
MIT
Metadata
Release files for django-cachex 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_cachex-0.4.1.tar.gz | 190.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_cachex-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 402.4 kB
Release files / django_cachex-0.4.1.tar.gz
| Download URL | django_cachex-0.4.1.tar.gz |
|---|---|
| Size | 190.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d5ee1473c2fe9754045c07d7d7ccd2ecad5a512e9b08c301b72a04aa4be8ad0
|
|
BLAKE2b-256 checksum How to use checksums |
9a5463ec00be839c6f428d1e93479a9f2a432d04477d1d94472b42b6de524787
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 21, 2026.
Transparency logRelease files / django_cachex-0.4.1-py3-none-any.whl
| Download URL | django_cachex-0.4.1-py3-none-any.whl |
|---|---|
| Size | 212.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a01ba249e3880cd3430970f8ea4009efc8646901438eb1aa1091e134dde0c1d
|
|
BLAKE2b-256 checksum How to use checksums |
27f2fd21d5c11a2909805d4b78c03318b356fe767f84679ee8f74ee2a454ca53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 21, 2026.
Transparency log