DocsHow it WorksIntegration with Cloud ProvidersIntegration with Cloud Providers Cadence.CI integrates directly with cloud providers so that Mélodium runners are deployed and execute entirely within your own cloud project, your data never transits through shared infrastructure. How It Works When you connect a cloud provider account, Cadence.CI uses the access credentials you supply to provision and manage runner instances on your behalf. The runners remain inside your project’s network and talk directly to each other, while Cadence.CI handles orchestration from the outside. Setup Steps Provide access credentials: give Cadence.CI the access keys or service account needed to provision compute in your cloud project. Required permissions vary by provider and are documented on each provider’s setup page. Infrastructure configuration: Cadence.CI automatically configures the required networking and instance parameters within your project. Runner deployment: when a pipeline runs, Mélodium runners are deployed directly inside your cloud environment. Direct execution: pipeline steps run inside your infrastructure, with direct access to co-located resources, no traffic routing through external networks. Benefits Performance: direct execution within your infrastructure eliminates unnecessary network hops between pipeline steps and your resources. Security: data remains within your cloud environment throughout execution. Cost efficiency: runners use your existing quota and billing, with no extra provisioning layer. Compliance: data residency and regulatory requirements are met because compute stays within your designated region and project. Supported Cloud Providers Cadence.CI supports integration with the following cloud providers: Scaleway Clever Cloud OVH Cloud Temple Outscale Oracle Cloud AWS Azure Google Cloud Provider-specific setup instructions, required permissions, and supported instance types are documented on each provider’s page.Programming LanguageIntegration with Kubernetes Clusters
