On your own server

Run everything on your own server.

Files never pass through our infrastructure. Install a small program, connect your clouds to it, and the transfer runs inside your network. Free during early access.

Join the waitlist

For homelab operators, privacy-conscious users, and businesses that want their file transfers running on infrastructure they control.

How it works for you

You run the transfer on your own server. We coordinate the job; the bytes never reach us. We call this setup a Private Runner.

Files never park on our servers

Bytes travel from the source cloud, through your server, to the destination cloud. Our infrastructure never sees the files.

Your credentials stay with you

Provider tokens live where your runner runs. We never receive them.

No incoming connections to open

Your server reaches out to us. No firewall holes, no exposed services, no port-forwarding.

How it works under the hood

Architecture, the self-host levels, and why core code stays public — for the technical user.

Control plane vs data plane

Two layers. The control plane (auth, jobs, schedules, reports) stores metadata about your transfers. The data plane (the runner) is where bytes flow from source → destination.

We host the control plane at launch; you host the data plane on day one. The Private Runner is the full data-plane runtime.

Self-host levels

  1. 01

    Private Runner

    First to land

    Hosted control plane, your data path. For users who want our convenience and your bandwidth.

  2. 02

    Full self-host

    Planned

    Bring your own control plane. Your auth, your database, your runners. Same product, your infrastructure.

Plus an air-gapped variant for high-compliance environments that can't reach the public internet.

Why core code stays public

Every runner — Cloud Runner, Browser Runner, Local Helper, Private Runner — ships source-visible, alongside the transfer logic and provider adapters. You can audit how files move before trusting the system.

Move the control plane to your server when you're ready

Today, self-hosting means running the Private Runner on your hardware while Syncologic hosts the control plane (free during early access). When the self-host control plane ships, you'll be able to export your jobs, schedules, run history, and connections from our control plane and import them into your own. Control-plane data is yours to move.

Join the waitlist

Help us build the right tool. Drop your email, then tell us what you need — it takes about a minute.

By joining, you agree to our Privacy notice.