DriftSync
Get Pro

Multi-site fan-out

Fan-out applies one release across a group of connected sites in a single action. Each site still runs the full core loop independently — its own dry-run diff, its own snapshot, its own result — so promoting a change to a fleet is as safe as promoting it to one site, just faster.

Pro

Multi-site fan-out is a DriftSync Pro feature and builds on direct connections — every target must be a paired site.

Target groups

Rather than pick sites one by one every time, you organise connected sites into groups — for example "all production stores" or "EU staging". A fan-out targets a group, so the same release reaches a consistent, named set of sites and your intent is auditable.

Running a fan-out

  1. Select or export the release you want to promote.
  2. Choose Fan out and pick a target group (or an ad-hoc set of connected sites).
  3. DriftSync sends the bundle to each site. Every site computes its own dry-run diff against its current state — because the same bundle can mean different changes on different targets.
  4. Approve and apply. Each site snapshots and writes independently, and reports back its outcome.

The status board

A fan-out is tracked on a status board that shows, per site, where each one is in the loop:

  • Pending — the bundle is queued or in transit.
  • Diffed — the dry-run diff is ready for review.
  • Applied — the release was written and snapshotted successfully.
  • Failed / skipped — the site could not apply, with the reason attached.

One site failing does not roll back the others — each is independent. You can retry a failed site, or roll just that one back from its own History.

Important

Because each target diffs against its own state, review the per-site diffs before a broad apply. A value that is a clean add on one site may be an overwrite on another that already has it.

Independent snapshots and rollback

Every site in a fan-out takes its own snapshot before applying, so each remains one click from its previous state. There is no fleet-wide "undo" — you roll back per site, which keeps the audit trail on each site accurate.

Scaling it up

For scheduled, hands-off fan-outs, combine this with scheduled syncs. For approvals and a shared audit across a team, see the team library and DriftSync Cloud, which hosts the fan-out status board for the whole fleet.