Redis

Lightweight in-memory Redis implementation speaking the real RESP protocol.

Default Connection

redis://parlel-bridge:6379

(Use localhost instead of parlel-bridge if you run the bridge outside Docker and publish its ports.)

No auth required. All commands accepted. AUTH is accepted as a no-op (the dev pool does not enforce credentials).

Replies are framed in the real RESP protocol: nested arrays (SCAN, SSCAN/HSCAN/ZSCAN, MGET, HMGET, GEOPOS, XRANGE) are encoded as RESP arrays, missing entries come back as nil bulk ($-1), and typed errors use the real error code (-WRONGTYPE …, -ERR value is not an integer or out of range, -ERR no such key, -ERR unknown command …), so ioredis, node-redis, and redis-py parse them unmodified.

Supported Commands

Connection

Strings

Counters

Lists

Sets

Hashes

Sorted Sets

HyperLogLog

Streams

Geo

Pub/Sub

Transactions

Server

Surface coverage

Legend: ✅ supported · ◐ accepted-not-enforced · ✓ by design · ⟳ roadmap

Error codes & shapes

RESP errors carry the real error code as the first token, so client libraries that branch on it behave the same as against production Redis:

Usage

Add the parlel/bridge sidecar to your test compose file. Your app connects to the plain parlel-bridge hostname with unmodified real drivers — no Parlel code in your app.

include:
  - path: parlel-bridge.yml          # image: parlel/bridge
services:
  app:
    build: .
    env_file: test.env
    depends_on:
      parlel-bridge: { condition: service_healthy }

Run it:

PARLEL_API_KEY=pk_... docker compose -f docker-compose.test.yml up

Then connect with your normal client. Python:

import redis

r = redis.Redis(host="parlel-bridge", port=6379)
r.set("user:1", "alice")
print(r.get("user:1"))
r.incr("counter")
r.expire("counter", 3600)

Node:

import Redis from "ioredis";

const redis = new Redis({ host: "parlel-bridge", port: 6379 });
await redis.set("key", "value");
await redis.get("key");

Via MCP (Parlel Sandbox)

When Redis runs inside a Parlel sandbox, drive it through the sandbox's MCP endpoint with parlel_execute. Pass a raw Redis command string as command:

{
  "jsonrpc": "2.0", "id": 1, "method": "tools/call",
  "params": {
    "name": "parlel_execute",
    "arguments": { "service": "redis", "command": "SET hello world" }
  }
}

The decoded RESP reply is returned as { reply: ... }.

Seed Data

# cache-seed.txt
SET user:1 '{"id":1,"name":"Alice","email":"alice@test.com"}'
SET user:2 '{"id":2,"name":"Bob","email":"bob@test.com"}'
SET session:abc '{"userId":1,"role":"admin"}'
EXPIRE session:abc 3600
SET config:theme "dark"
SET config:lang "en"

Seed via MCP parlel_execute, or run these against the bridge with your normal client.

Access via Parlel Sandbox

The parlel/bridge sidecar (image: parlel/bridge) exposes Redis on parlel-bridge:6379. It tunnels the raw RESP protocol as TCP over the sandbox's HTTPS preview proxy via WebSocket, so redis-py, ioredis, or any client connects to redis://parlel-bridge:6379 unmodified — with just an API key. No SSH tunnel, no daytona CLI. (Use localhost instead of parlel-bridge if you run the bridge outside Docker and publish its ports.) Postgres and Redis start by default in a new sandbox.