DigitalOcean
DigitalOcean is the developer cloud, offering droplets, managed databases, and Kubernetes. With Kestra's dedicated plugin, teams orchestrate the whole account with event-driven flows.
HashiCorp
Terraform declares infrastructure as code and Vault keeps the secrets. Kestra brings the same model to orchestration: flows, namespaces and permissions live in Terraform, Terraform runs become governed steps in a flow, and credentials stay in Vault.
About
Kestra's Terraform provider is a partner-tier provider on the Terraform Registry. It manages Kestra resources from flows and namespaces to users, roles and worker groups, so a Kestra instance is versioned and promoted like the rest of the infrastructure.
“Kestra's declarative model and Terraform integration gave us exactly what we needed to build customer-specific pipelines, automate deployment, and monitor everything reliably.”
HashiCorp + Kestra: everything as code, from infrastructure to workflows
Kestra itself, declared in Terraform
The official provider manages flows, namespaces, namespace files, KV pairs, secrets, users, groups, roles, service accounts, apps and worker groups. Foundation Data declares its entire Kestra Cloud environment this way and deploys it from Git.
One git push for infrastructure and flows
Leroy Merlin France deploys its warehouse resources and its Kestra flows through the same Terraform pipeline. Shipping a new pipeline went from days of coordination across four teams to a single push, the same day.
Terraform runs with an approval gate
The TerraformCLI task runs plan and apply as steps in a flow. Kestra schedules drift checks, pauses between plan and apply for a named reviewer, and chains Ansible or Argo CD after the apply.
Secrets stay in HashiCorp Vault
Kestra Enterprise reads secrets directly from Vault, including read-only secrets that teams keep managing in Vault. Crédit Agricole runs Kestra with Vault handling secret rotation at scale.
