ITAM / Servers

How to Add a Server

Register a host in your CMDB so Carlos can track cost, status, and uptime before the next api.workverge.ai maintenance window.

Real-world scenario

Carlos Reyes · IT Admin at Bluewave Labs

Engineering just spun up a new Hetzner box for api.workverge.ai. Carlos needs it in WorkVerge today, with the right type and IP, so uptime monitoring is live before Friday's release.

Before you begin

  • ITAM license enabled for your organization
  • Admin or asset manager role with create permission
  • At least one server type available (built-in or custom)

Overview

Servers sit alongside domains and SSL certificates under Digital Assets. Each record is a CMDB node you can link to apps, attach tickets to, and monitor for downtime. Manual entry is best when you have one new host; use CSV import or cloud sync for larger batches.

Step-by-step

  1. 1

    Open ITAM → Digital Assets → Servers

    You will see every server your org already tracks. If the list is empty, this is your first record.

  2. 2

    Click New Server

    The create form opens in the detail drawer. Fill it in before the next maintenance window.

  3. 3

    Enter a unique server name

    Use a name your team recognizes, e.g. api-WorkVerge-prod, not "Server 3". WorkVerge rejects duplicate names in the same org.

  4. 4

    Select server type

    Pick Web, Database, API, or a custom type from Server Types. This drives filters and dashboard counts.

  5. 5

    Enter IP address and username

    IPv4 and IPv6 are supported. The username is the login or service account label for this asset record.

  6. 6

    Set price, currency, and purchase date

    WorkVerge converts cost to your org currency using the purchase date, handy when finance reports in USD but Hetzner bills in EUR.

  7. 7

    Choose status and optional provider/region

    Active for production, Maintenance during patches, Inactive for decommissioned hosts. Provider and region help when you filter by cloud.

  8. 8

    Click Add Server

    WorkVerge validates the form and adds the server to the list immediately. No page refresh needed.

Required fields

  • Server name. Unique per organization; pick something operators will search for
  • Server type. Web, Database, API, or custom
  • IP address. IPv4 or IPv6
  • Username. Login or service account label on the asset record
  • Price and currency. Converted to org currency on save
  • Purchase date. Used for currency conversion
  • Status. Active, Inactive, or Maintenance

Optional: provider (AWS, Hetzner, GCP, Azure, Digital Ocean), region, tags, description.

Example

Carlos adds api.workverge.ai production

  • Name: api-WorkVerge-prod
  • Type: API
  • IP: 52.58.14.22
  • Username: deploy
  • Provider: Hetzner · Region: fsn1
  • Price: €24.00/mo · Purchase date: 2026-03-01 · Status: Active

Duplicate name?

If you see an error that the name already exists, search the server list, you may have imported it via a cloud integration under a different label. Edit the existing record instead of creating a second one.

Next steps

  • Enable uptime monitoring from the server detail drawer, use 5 minutes for production API hosts
  • Run Ping from server detail to confirm the IP is reachable from WorkVerge
  • Link the server to api.workverge.ai in the relationship graph

Related articles