About Polysync

About Polysync

Polysync is a metadata-driven, multi-cloud orchestration platform that unifies pipeline scheduling, dependency management, and live monitoring across Azure and Google Cloud, from a single control plane. Delivered as a SaaS subscription on the Azure Marketplace, with no orchestration code to write and no infrastructure to operate.

Where Polysync sits in your stack

Polysync is a control plane. Your existing cloud services keep doing the work; Polysync decides when they run, in what order, and gives you one place to see what happened across every connected platform.

What Polysync gives you

  • A unified scheduler and DAG engine across every connected Azure, Google Cloud, and AWS service
  • Metadata-driven configuration: jobs and tasks are data, not code
  • Cross-platform dependency triggers and parameter mapping out of the box
  • One monitoring view for runs, queues, and schedules across the whole estate
  • Multi-tenant SaaS delivery through the Azure Marketplace, with nothing to install

How it fits with what you already have

  • Works with ADF, Databricks, Synapse, Fabric, Functions, Logic Apps, Vertex AI, Composer, AWS Glue, AWS Lambda, AWS Step Functions, Amazon SageMaker, AWS Batch, and more
  • Reuses your existing pipelines, notebooks, and workflows, with nothing to rebuild
  • Discovers resources from each connected platform and imports their parameters automatically
  • Honours your existing identity model via Microsoft Entra ID single sign-on
  • Reads credentials from your own secret vault, or holds them in a managed Azure Key Vault

How Polysync is delivered

Polysync is sold as a subscription on the Azure Marketplace. There is nothing to install. Sign in with your Microsoft 365 account and your tenant is provisioned automatically.

Sold through Azure Marketplace

One subscription, one invoice from Microsoft. Polysync runs as a SaaS application; you don't manage servers, databases, or runtimes.

Sign in with Entra ID

Authentication uses Microsoft Entra ID single sign-on. Polysync inherits your tenant's identity controls, conditional access policies, and group membership.

Schema-isolated tenancy

Each customer's configuration and run history lives in its own database schema. There is no shared table that mixes data between tenants.

Credentials stay in a vault

Link your own Azure Key Vault, AWS Secrets Manager, Google Cloud Secret Manager, or HashiCorp Vault. If you'd rather not, Polysync holds the credential in its managed Azure Key Vault.

Two roles, by design

Administrators configure platforms, connections, and users. Operators run, monitor, and reschedule jobs. Access is enforced server-side on every request.

Scales without rebuilding

The scheduler and dispatcher run as independent services with concurrency caps, leaky-bucket rate limits, and rolling-window throttles per platform connection. Add platforms and tasks without re-architecting orchestration.