For developers and platform teams

Move files between clouds with one API.

For agencies, SaaS teams, and internal tools that move files between cloud providers without writing the glue.

Join the waitlist

Built for agencies, SaaS engineering teams, platform groups, and internal tooling.

A typed HTTP API

Create a job with a source, destination, runner, and optional schedule. The control plane validates, dispatches, and emits progress events.

Sketch — final shape will land with the v1 API.

POST /v1/jobs
Authorization: Bearer sk_live_…
Content-Type: application/json

{
  "source":      { "provider": "google_drive", "path": "/Marketing" },
  "destination": { "provider": "s3", "bucket": "acme-archive", "prefix": "marketing/" },
  "runner":      "cloud",
  "schedule":    "0 2 * * *",
  "on_conflict": "skip"
}

OAuth lives on our side

Your users connect their cloud accounts to Syncologic, not to your app. You never store provider credentials. The control plane manages the OAuth lifecycle and hands out scoped, short-lived tokens to runners — your app authenticates with Syncologic via your API key and never sees a provider token.

Your app integrates the API; the OAuth boundary stays on our side.

A CLI for scripts and CI

Same jobs, driven from a terminal or a CI runner. Useful for one-shot migrations and for backups owned by a script you can read in a code review.

Planned. Behavior mirrors the API one-to-one.

syncologic jobs create \
  --source google_drive:/Marketing \
  --destination s3://acme-archive/marketing/ \
  --runner cloud \
  --schedule "0 2 * * *" \
  --on-conflict skip

Webhooks for the events you care about

Subscribe to job lifecycle events and stream them into your queue, your dashboard, or your audit log. Payloads will be HMAC-signed.

Planned events

  • job.created
  • job.run.started
  • job.run.progress
  • job.run.completed
  • job.run.failed
  • job.schedule.fired

No SDK promises yet

We will not ship an official SDK before the API is stable. The OpenAPI spec will be public, so you can generate a typed client in any language you already use.

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.

Developer FAQ

  • When can I start using the API?
    With early access. Syncologic is API-first — our browser frontend uses the same API you would. Every plan (Free, Pro, Business) includes API access from day one.
  • Will there be a free tier for developers?
    There's no special developer offer — everything you'd pay (or not pay) is in the current plans. See plans →
  • Do you handle OAuth on behalf of my users?
    Yes — your app never holds a provider token. How OAuth works →
  • Can I run jobs entirely on my own infrastructure?
    Yes for the data path — Private Runner runs on any server you control, and file bytes never reach Syncologic. Architecture and roadmap →
  • Are webhook payloads signed?
    Webhook payloads will be HMAC-signed with a per-workspace secret you control.