Launching today
Spedo
Single-node RESP runtime for hot, rebuildable KV/JSON state
1 follower
Single-node RESP runtime for hot, rebuildable KV/JSON state
1 follower
Backend developers and SREs need fast, temporary state—such as rate-limit counters, ephemeral sessions, and precomputed JSON—without treating it as their durable source of truth. Spedo runs these rebuildable workloads on a single RESP-compatible node. Its JSON MODEL feature reuses schemas across similar values, with optional LZ4 compression; GET returns ordinary JSON. Keep durable records in SQL and test the setup with the Docker quickstart.
Free Options
Launch Team
CloudflareYour next app belongs on Cloudflare Workers. Deploy for free
Promoted
Backend services often need hot state they can rebuild—rate-limit counters, short-lived sessions, or repeated JSON payloads—without treating it as the durable source of truth. Spedo provides a focused, single-node RESP runtime for that KV/JSON workload, with JSON MODEL and optional LZ4.
The most useful feedback would be specific: Which commands does your workload need? Does the Docker quickstart work in your environment? Does Spedo’s documented single-node recovery behavior fit your use case? If you try MODEL on your own JSON, what works or gets in the way? A reproducible example is especially helpful.