ITAM / Servers

Server Integrations

Pull EC2, Hetzner Cloud, Droplets, GCP VMs, and Azure VMs into WorkVerge automatically, no retyping IPs after every scale-up.

Real-world scenario

Carlos Reyes · IT Admin at Bluewave Labs

Bluewave Labs runs api.workverge.ai on Hetzner and analytics workers on AWS. Carlos connects both integrations so new VMs appear in WorkVerge within minutes of provisioning, without a spreadsheet.

Before you begin

  • ITAM license enabled
  • Org admin access to My Organization → Integrations
  • Cloud provider API credentials with read access to compute instances

Overview

Cloud integrations keep your CMDB aligned with reality. When engineering spins up a new Hetzner box for api.workverge.ai, sync adds it to the servers list with provider and region filled in. Manual records and synced records live in the same table, you can still edit descriptions, enable monitoring, and link dependencies either way.

Supported providers

  • AWS. EC2 instances
  • Hetzner. Hetzner Cloud servers
  • Digital Ocean. Droplets
  • Google Cloud. Compute Engine VMs
  • Azure. Virtual machines

Setup steps

  1. 1

    Go to My Organization → Integrations

    Integrations are org-wide, not per user. You need admin access.

  2. 2

    Open the Servers section

    You will see cards for each supported cloud provider.

  3. 3

    Choose a provider and enter credentials

    AWS needs access keys; Hetzner needs an API token; GCP and Azure use service accounts or app registrations as documented in each card.

  4. 4

    Save and run the first sync

    WorkVerge pulls VM metadata, name, IP, region, and creates or updates server records.

  5. 5

    Review ITAM → Digital Assets → Servers

    Synced hosts appear alongside manually added ones. Enable uptime monitoring on production rows.

Hetzner at Bluewave Labs

Carlos creates a read-only API token in Hetzner Cloud, pastes it into WorkVerge under Integrations → Servers → Hetzner, and saves. Within the first sync, api-WorkVerge-prod and staging-api appear with fsn1 region tags.

Sync behavior

Each sync creates new VMs and updates metadata on existing ones matched by provider identity. Fields you edit manually, like custom descriptions, may be overwritten on fields that sync owns (name, IP, region). Use description for notes sync should not replace.

After sync

Filter by provider, then bulk-set Maintenance on staging hosts and enable 5-minute monitoring on production API servers. Sync gets inventory in; you still own operational policy.

Related articles