Automation & API

Jobs: how changes happen

Every mutation — creating a VM, applying a security group, attaching a volume — runs as an automation job with a full log. Jobs are visible in the console as they run, and their history is your audit trail: what changed, when, and by whom.

API tokens

Create API tokens from your account settings. Tokens are scoped by role — a token can never do more than the user who created it — and can be revoked at any time.

curl -H "Authorization: Bearer $CLOUDOPS_TOKEN" \
  https://<your-tenant>/api/v1/servers

Terraform provider

The official provider lets you manage CloudOps resources declaratively — servers, virtual machines, SSH keys, and security groups — with the same semantics as the console.

terraform {
  required_providers {
    cloudops = { source = "cloud-ops/cloudops" }
  }
}

resource "cloudops_virtual_machine" "web" {
  name     = "web-01"
  vcpus    = 4
  ram_mb   = 8192
  disk_gb  = 80
  os_image = "ubuntu-24.04"
}

Console, API, and Terraform are three doors into the same control plane — anything you build in one is visible in the others.