Skip to content

Providers

cdkx providers bridge the gap between your TypeScript construct tree and a target platform's API. Each provider ships as a separate npm package and adds its own set of L1 constructs and a runtime deployment adapter.

  • Hetzner Cloud


    Manage Hetzner Cloud infrastructure — networks, servers, load balancers, volumes, floating IPs, and more. Deploys via the Hetzner Cloud API.

    Status: Alpha  ·  Resources: 15

    Hetzner Cloud

  • Multipass


    Provision and manage local Ubuntu VMs using Canonical Multipass. Ideal for local development environments. No cloud account required.

    Status: Alpha  ·  Resources: 1

    Multipass

How providers work

Each provider is split into two packages:

Package Role
@cdk-x/<provider> L1 constructs — TypeScript classes you use in your App
@cdk-x/<provider>-runtime Deployment adapter — called by the engine at cdkx deploy time

At synthesis, constructs emit a JSON manifest. At deploy time, the engine loads the runtime adapter, resolves cross-resource tokens, and calls the provider API in dependency order.