Redis Browser

Scan keys, inspect typed values and run bounded commands through your local runtime

Redis actions send data to your local runtime

Why: The browser uses the authenticated localhost runtime to connect to Redis.

Data sent:

Redis host, port, database index, ACL username, password and TLS setting
Scan pattern, cursor, key bytes, command arguments and mutation permission

Data handling: The authenticated localhost runtime forwards the operation to your service and returns its response. Saved connections use the encrypted project vault; query results remain in page memory.

Audit the source: src/app/api/local-connectors/route.ts

Audit the source: src/lib/redis-connector.ts

Learn More About This Tool

Desktop / localhost connector access

For a local web runtime, enable native connectors on localhost and enter its access key. The key stays in this app session’s memory. The desktop app supplies access automatically.

Local connector access key

Redis hostACL username (optional)Redis password (optional)Redis portDatabase index

Use TLS with certificate verification

Save or load an encrypted connection

Uses this project's Credential Vault. Loading copies credentials into the active client’s memory for requests; they are cleared when the page closes or the project switches.

Connection nameCredential vault passphrase

Key browser

Redis glob pattern

SCAN avoids a blocking KEYS request. COUNT 100 is a server hint; batches can be empty or contain duplicates while keys change. Cursor: 0 Up to 1,000 distinct keys are shown. Refine the pattern for more.

Command console

Command arguments (JSON array)

Command examples: ["GET","name"], ["LRANGE","jobs","0","99"], ["HSCAN","settings","0","COUNT","100"]. Use {"base64":"AAE="} for binary arguments. String GET is limited to 64 KiB; use nonnegative GETRANGE windows for larger values. Integer replies remain text to preserve 64-bit precision.

Enable mutations for this command

Mutation commands are blocked until enabled. Read-only server credentials provide an additional database-enforced boundary. Administrative, scripting, blocking and unbounded collection commands are unavailable.

Connections are opened for each operation and closed afterward. Data and command history stay in this page’s memory. Saved connection credentials use the encrypted project vault.

Related tools

SQL Database Workspace

Document Data Explorer

S3 Storage Browser

GraphQL Schema & Operation Explorer

Swagger / OpenAPI Viewer

AsyncAPI Explorer