Overview

This section introduces how to manage Verda resources declaratively using infrastructure‑as‑code tools. You can leverage the Verda provider from both Terraform and OpenTofu to provision and configure.

This section introduces how to manage Verda resources declaratively using infrastructure‑as‑code tools. You can leverage the Verda provider from both Terraform and OpenTofu to provision and configure compute, storage, and container services in a reproducible manner.

Supported Provisioners

• Terraform: Officially supported via the Verda Cloud registry. The provider is compatible with Terraform 1.x.

• OpenTofu: An open‑source fork of Terraform. The Verda provider works seamlessly with OpenTofu; you can source it directly from the OpenTofu registry if you prefer.

To use the provider, specify one of these sources in your configuration:

# From Terraform Registry (works in OpenTofu as well)
terraform {
  required_providers {
    verda = {
      source  = "verda-cloud/verda"
      version = "~> 1.0"
    }
  }
}

# Or, explicitly from OpenTofu Registry
terraform {
  required_providers {
    verda = {
      source  = "registry.opentofu.org/verda-cloud/verda"
      version = "~> 1.0"
    }
  }
}

Replace the version constraint with the latest provider version available in the registry.

What You’ll Find Here

• Terraform – guidance on installing the provider, authenticating with your Verda account, configuring providers, and using modules. Subsections cover compute resources (instances, SSH keys, startup scripts), storage (volumes), container workloads (deployments, serverless jobs, registry credentials), and how to import existing resources.

• OpenTofu – a brief overview of OpenTofu, instructions on using the Verda provider via the OpenTofu registry, and notes on migrating existing Terraform configurations to OpenTofu if desired.

Prerequisites

• A Verda account with API access and an API token.

• Terraform 1.0 or newer, or OpenTofu 1.6 or newer installed on your local machine.

• Basic familiarity with HCL (HashiCorp Configuration Language).

This overview acts as the landing page for the infrastructure‑as‑code documentation. Use the navigation sidebar to dive into the specific topics that matter to you, such as provisioning GPU instances, managing volumes, or deploying containers.