Key-value and cache
Valkey
Valkey uses the Redis-compatible core workflow while hiding Redis Stack/vector-only surfaces unless compatible metadata proves support.
Prerequisites
- Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
- Have the endpoint, database file, or cloud account details for a Valkey datastore you are authorized to use. Start with least-privileged, read-only access.
- Keep an independent backup before enabling edits, administration, restore, or transfer execution.
Connect and run a safe query
- 1
Create the connection
Open Library, choose Create connection, and select Valkey and a supported Connection method tab.
- 2
Test and save
Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.

Valkey connection setup. The Valkey connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size - 3
Open the native explorer
Use Save Connection, or Create Database and Save Connection for a new local file, then open the Valkey Explorer where supported.
- 4
Select a scope
Select the database / namespace scope that should be attached to the new tab.
- 5
Run a bounded read
Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.

Valkey native workflow. A representative Valkey explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size - 6
Inspect the result
Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.
- 7
Export when needed
Export only the required rows after reviewing format, destination, and redaction options.
- 8
Open diagnostics or transfers
Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.
Connection fields
| Field | Required | Purpose | Safe example |
|---|---|---|---|
| Name | Yes | A clear profile name, without credentials. | Valkey development |
| Connection method | Yes | Choose a supported tab. The fields below apply only to the selected method and deployment. | Connection fields / Connection string |
| Environment | No | Attach the intended variable and safety context. | Local development |
| Read-only connection | No | Enable for initial exploration. This does not make pre-release software safe for production workloads. | Enabled |
| Host / Port | No | Endpoint for a fields-based connection. Follow the selected deployment and runtime limitations; MongoDB SRV does not use an explicit port. | localhost / engine default |
| Database / default scope | No | Initial scope for browsing, where supported. | catalog |
| Complete connection string | Yes | Required in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value. | Paste your complete provider string; do not share it |
| Username | No | Authentication identity for the selected method. | catalog_reader |
| Password | No | Required only when the chosen authentication needs it. Save Connection stores changes; blank preserves an existing value, and Reveal… explicitly discloses it. | Stored in the desktop OS vault |
| Deployment | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | standalone / tls / sentinel / unix-socket |
| Database index | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Protocol | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | resp2 / resp3 |
| Client name | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Sentinel master | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Sentinel hosts | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Sentinel username | No | Authentication. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Sentinel password | No | Authentication. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Saved with the connection |
| Sentinel TLS | No | TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Unix socket | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Use TLS | No | TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Connect timeout (ms) | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Command timeout (ms) | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
Run the sample query
SCAN 0 MATCH sample:* COUNT 100Explore and inspect
- Browse logical databases, type folders, keys, TTL, memory, encoding, streams, ACL/security, Pub/Sub, cluster/Sentinel-like topology where compatible, INFO, persistence, replication, and diagnostics.
- Inspect strings, hashes, lists, sets, sorted sets, streams, TTL, memory, encoding, length, raw values, and before/after key metadata for guarded changes.
Diagnose, administer, and transfer
- Review INFO, command stats, memory, latency, clients, slowlog, ACLs, persistence, replication, and Valkey-specific disabled reasons.
- Use guarded core key/member edits, stream entry actions, TTL changes, delete/rename workflows, ACL reviews, slowlog, INFO, persistence, and replication panels.
- Import — Live. Valkey exports and restores explicit keys with protocol-native serialized values and TTL evidence. Formats: JSON (portable), NDJSON (portable). Destinations: local file.
- Export — Live. Valkey exports and restores explicit keys with protocol-native serialized values and TTL evidence. Formats: JSON (portable), NDJSON (portable). Destinations: local file.
- Backup — Unavailable. This datastore has no supported in-process or server API for a full native backup artifact. Formats: Native managed backup (native). Destinations: cloud uri, server path. Full Valkey backup and restore require excluded vendor tooling or storage-backend access.
- Restore — Unavailable. This datastore has no supported in-process or server API for a full native backup artifact. Formats: Native managed backup (native). Destinations: cloud uri, server path. Full Valkey backup and restore require excluded vendor tooling or storage-backend access.

Capabilities and availability
| Capability | Status | Notes |
|---|---|---|
| Native explorer | Available | Browse logical databases, type folders, keys, TTL, memory, encoding, streams, ACL/security, Pub/Sub, cluster/Sentinel-like topology where compatible, INFO, persistence, replication, and diagnostics. |
| Read queries | Available | Use key browser mode first, filter by pattern/type, scan incrementally, and switch to console mode for Redis-compatible commands. |
| Inline editing | Unavailable | Use a reviewed statement or the engine-native tool instead. |
| Diagnostics / administration | Guarded | Use guarded core key/member edits, stream entry actions, TTL changes, delete/rename workflows, ACL reviews, slowlog, INFO, persistence, and replication panels. |
| Import / export / transfer | Guarded | Availability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented. |
Safety and limitations
Troubleshooting
| Symptom | Resolution |
|---|---|
| Test connection fails or times out | Verify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure. |
| Explorer branches are empty or disabled | Confirm the selected database / namespace, refresh the branch, and grant the minimum metadata permissions described in the connection warning. |
| Run, edit, admin, or transfer is disabled | Read the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback. |
| The sample query fails or returns different columns | Replace the example names with objects from your Valkey datastore, confirm the selected database / namespace, and keep the query bounded while you validate the result. |