Direct connections

A direct connection is a trusted link between two DriftSync Pro sites. Once paired, you can push or pull a release straight between them — no bundle file to download, upload, or email. The core loop is unchanged: the receiving site still previews a dry-run diff and snapshots before it applies.

How pairing works#

Pairing is a one-time handshake secured by two things: a short-lived pairing code to establish the link, and a long-lived per-connection token that authenticates every transfer afterwards. Each connection has its own token, so you can revoke one link without affecting any other.

1. On the first site, open DriftSync → Connections and choose Add connection. DriftSync generates a pairing code that expires after a few minutes.
2. On the second site, open Connections, choose Pair with a site, enter the other site's URL, and paste the pairing code.
3. The sites exchange a per-connection token and confirm the link. From then on, each recognises the other by that token — the pairing code is spent and no longer valid.

Push and pull#

• Push — send a release from this site to a connected one. The remote site receives the bundle, runs its own dry-run diff, snapshots, and applies.
• Pull — request a release from a connected site and apply it here. Useful when a central "source of truth" site holds the canonical configuration.

Either way, the same redaction rules apply before the bundle leaves the source, so secrets are held back over a connection exactly as they are in a file.

Managing connections#

The Connections screen lists every paired site with its status and last transfer. Revoke a connection to invalidate its token immediately; the other side can no longer push or pull until you pair again. Revoking one connection leaves all your other links intact.

Next steps#

To apply one release across many connected sites at once, see multi-site fan-out. To keep connected sites in step automatically, see scheduled syncs.