Flux

Ultra-fast file sync and streaming between on-premises, private and public clouds over HTTP(S).

What you will do: understand what Flux moves, where it runs and how to set up a first sync.

Flux moves files and streams between places that are usually hard to connect: an on-premises data centre, a private cloud and one or more public clouds. It runs over HTTP(S), so it crosses firewalls and proxies with the ports you already allow, and it is built for speed on large volumes and long distances.

What Flux does

  • File sync — keep directories in step between two or more locations, one-way or two-way.
  • Streaming — move data continuously as it is written, rather than in batches.
  • Over HTTP(S) — no special ports or VPNs; HTTPS gives encryption in transit.

Typical uses

  • Ship logs and telemetry from sites with no direct network path to the central deployment.
  • Replicate archives from on-premises to object storage in a public cloud.
  • Feed a cloud analytics platform from an on-premises source without opening inbound access.

Steps: a first sync

  1. Deploy a Flux node at each end — see Deploy — and register them.
  2. On the receiving side, create an endpoint and note its URL:
https://<placeholder-host>:<placeholder-port>/<placeholder-endpoint>
  1. On the sending side, create a sync job: source directory, destination endpoint, direction and schedule or continuous mode.
  2. Set bandwidth limits if the link is shared.
  3. Start the job and watch the transfer view: files queued, in flight, done, and throughput.

How it fits

Flux is licensed per organization and deployment; the units are listed under How licensing works. It pairs with PortX when data must be both moved between sites and routed by policy once it arrives.

Next: Integrations overview

Verify with XPLG engineering before publishing.