Connections

Topologies

Varc treats all three Redis topologies as first-class. Routing lives in one shared layer, so every feature — browsing, debugging, undo, scripting, load testing — works the same way in each.

Standalone

The direct path: one host, one port. Ideal for local development and single node deployments.

Cluster

Point Varc at any node and it discovers the rest. Slot-aware routing sends each command to the right node, replica reads are supported, and a reshard mid-scan re-resolves instead of failing your session.

Sentinel

Give Varc your sentinel endpoints and the master name. It follows the current master and reconnects automatically on failover — mid-session, without losing your place.

Secure transport

All connection security options are first-class fields on the connection form, for every topology:

• TLS — enable server verification with a system or custom CA bundle.
• mTLS — add a client certificate and key for mutual authentication.
• SSH tunnel — connect through a bastion with host-key verification. Varc pins the host key and warns loudly if it changes.

Credentials are stored in your operating system’s keychain, never in plain text config files.

Connection profiles

Every connection is saved as a named profile. Profiles are shared between the desktop app and the CLI, so varc proxy --profile prod uses exactly the connection you configured in the window.