burner-redis
Experimental: This library is under active development and not yet ready for production use. APIs may change without notice.
An embedded, in-process Redis-compatible database written in Rust with Python bindings. Drop-in replacement for redis.asyncio.Redis that runs inside the host process with no external server needed.
Built to back docket and self-hosted Prefect servers without requiring a separate Redis deployment.
Installation
pip install burner-redis
Requires Python 3.10+. Pre-built wheels available for Linux (x86_64, aarch64), macOS (x86_64, arm64), and Windows (x86_64, arm64).
Quick start
from burner_redis import BurnerRedis
db = BurnerRedis()
# Use like redis.asyncio.Redis
await db.set("key", "value")
value = await db.get("key")
# Persistence across restarts
db = BurnerRedis(persistence_path="data.dat")
await db.set("key", "value")
# Data is saved on process exit and reloaded on next start
Supported commands
Strings
SET (with NX/EX/PX), GET, MGET, DELETE, EXISTS, KEYS, TTL, EXPIRE
Hashes
HSET, HGET, HDEL, HGETALL, HVALS, HEXISTS, HINCRBY
Sets
SADD, SMEMBERS, SISMEMBER, SREM
Sorted sets
ZADD, ZREM, ZRANGE (with WITHSCORES), ZRANGEBYSCORE (with WITHSCORES/LIMIT), ZRANGESTORE, ZREMRANGEBYSCORE, ZCARD, ZSCORE, ZCOUNT
Streams
XADD, XREAD, XLEN, XRANGE, XDEL, XTRIM, XGROUP CREATE, XGROUP DESTROY, XREADGROUP, XACK, XAUTOCLAIM, XCLAIM, XINFO GROUPS, XINFO CONSUMERS, XPENDING, XPENDING RANGE
Pub/Sub
PUBLISH, SUBSCRIBE, UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBSUB CHANNELS, PUBSUB NUMSUB, PUBSUB NUMPAT
Scripting
EVAL, EVALSHA, SCRIPT LOAD, SCRIPT EXISTS
Python-layer features
- Pipeline — buffer commands and execute in batch, matching
redis.asyncio.Redis.pipeline()semantics - Lock — distributed-style locking with atomic Lua-based release, matching
redis.asyncio.Redis.lock()semantics - PubSub — async message listener with channel and pattern subscriptions
- Script — register and call Lua scripts, matching
redis.asyncio.Redis.register_script()
Persistence
Pass persistence_path to save state to disk on shutdown and restore on startup:
db = BurnerRedis(persistence_path="burner-redis.dat")
- Crash-safe writes (atomic temp file + rename)
- Expired keys excluded from snapshots
- Manual save available via
await db.save()orawait db.save(path="custom.dat") - MessagePack binary format
redis-py compatibility
burner-redis implements a subset of the redis.asyncio.Redis interface — enough to back docket and common Prefect server workflows, but not the full redis-py API. Commands not yet implemented will raise NotImplementedError.
When the redis package is installed, exceptions subclass redis.exceptions.ResponseError and redis.exceptions.NoScriptError so existing error handling works unchanged.
Development
# Prerequisites: Rust 1.85+, Python 3.10+, uv
# Development build
uv run maturin develop
# Run tests
uv run pytest
# Run Rust tests
cargo test
Packaging notes
Wheel builds use a vendored Lua 5.4 by default so pip install burner-redis does not require a
system Lua.
Packaging systems that already provide Lua can opt out of vendoring and link against that copy instead:
maturin build --release --no-default-features
If auto-detection is not available, point Cargo at the packaged Lua library explicitly:
LUA_LIB_NAME=lua
LUA_LIB=/path/to/lib
License
MIT
Metadata
Release files for burner-redis 0.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| burner_redis-0.1.7.tar.gz | 638.6 kB | With provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| burner_redis-0.1.7-cp310-abi3-win_arm64.whl | CPython 3.10 | abi3 | Windows ARM64 | Details |
| burner_redis-0.1.7-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details |
| burner_redis-0.1.7-cp310-abi3-musllinux_1_2_x86_64.whl | CPython 3.10 | abi3 | Linux musl 1.2+ x86-64 | Details |
| burner_redis-0.1.7-cp310-abi3-musllinux_1_2_aarch64.whl | CPython 3.10 | abi3 | Linux musl 1.2+ ARM64 | Details |
| burner_redis-0.1.7-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| burner_redis-0.1.7-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| burner_redis-0.1.7-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details |
| burner_redis-0.1.7-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 11.2 MB
Release files / burner_redis-0.1.7.tar.gz
| Download URL | burner_redis-0.1.7.tar.gz |
|---|---|
| Size | 638.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7474ff092669fd11ef765411572cdafcc3d89b8054aef4ca0617be6d6be4c680
|
|
BLAKE2b-256 checksum How to use checksums |
528954706febafc135095b2a9d797cfbd4eed2ab1ad7819808b99b587020471b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logRelease files / burner_redis-0.1.7-cp310-abi3-win_arm64.whl
| Download URL | burner_redis-0.1.7-cp310-abi3-win_arm64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.10 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
458f88feeddfb40a586cc3fcbd8e9384bbdfd2a4512a695af4900e06052570d4
|
|
BLAKE2b-256 checksum How to use checksums |
766fe9beaf46c5e9fd10dfcdb889ebf7d3aa85142c650c0ab17ab284194f58e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logRelease files / burner_redis-0.1.7-cp310-abi3-win_amd64.whl
| Download URL | burner_redis-0.1.7-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
f6cf4ac666766b32fd63940aad0c120847905fd3102c17e5b6b305f91a21d079
|
|
BLAKE2b-256 checksum How to use checksums |
f530207f47f406619a5b564355d2946c3171f84231a28b800709b5645b06a5ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logRelease files / burner_redis-0.1.7-cp310-abi3-musllinux_1_2_x86_64.whl
| Download URL | burner_redis-0.1.7-cp310-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
591a9d20685f9d6d22bf0c863b50b12dfcf328b06111b3f62c33cd3185d48ce0
|
|
BLAKE2b-256 checksum How to use checksums |
5cb919bae42cb124932d71168bc8e5bcb1da33aa62b908e5e632b3d298d7cb15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logRelease files / burner_redis-0.1.7-cp310-abi3-musllinux_1_2_aarch64.whl
| Download URL | burner_redis-0.1.7-cp310-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
9b5adfe99aeb8407f468078f3769b2a63e9168fea12f7709df5d2a3b152706e4
|
|
BLAKE2b-256 checksum How to use checksums |
34ad93c3916f053f89b7b5760da5bf855cd78b7885d480f9cfcc64f3732c1dc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logRelease files / burner_redis-0.1.7-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | burner_redis-0.1.7-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
39111467059b8a28f15ea061d2414ec25c3e57c65759983f90f4d358e7d6a72d
|
|
BLAKE2b-256 checksum How to use checksums |
e13295cfa1833316ca2b6b2e58150a4900bc1ad256043cdd36198f1887618ccc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logRelease files / burner_redis-0.1.7-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | burner_redis-0.1.7-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
20eba1917e3bca9eea5957d5700ff8defcb5a209e57a7841d005549aa0151f44
|
|
BLAKE2b-256 checksum How to use checksums |
6fc031c25cc88143eac2dddcc394151a0db627923d44c94376a83768552c9f13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logRelease files / burner_redis-0.1.7-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | burner_redis-0.1.7-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a3d9569a376b690fb5876d454e4904443332dc3ad5c0057e149fc2ad220bf599
|
|
BLAKE2b-256 checksum How to use checksums |
2f4ece5c91b884ac37fcd380756402536f8810964014097950900517ce8bd30c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logRelease files / burner_redis-0.1.7-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | burner_redis-0.1.7-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
f80c866996e0455d584eb3c0f3b067e411c632fb0519eab454e0968edf01e62c
|
|
BLAKE2b-256 checksum How to use checksums |
6c5d198bd1d22e504b3034353430703afbdb3efe6e25cb90bf52d896e1d266a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logSecurity for burner-redis 0.1.7
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.
Full provenance
All 9 files in this release have been uploaded with provenance metadata.
Attestation for burner_redis-0.1.7.tar.gz
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 May 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.