ITAM / Servers

Server Types

Label hosts as Web, Database, API, or your own taxonomy so filters and dashboards match how your team talks about infrastructure.

Real-world scenario

Carlos Reyes · IT Admin at Bluewave Labs

Engineering keeps saying "the API boxes" but WorkVerge only had generic Cloud types. Carlos adds an API type and reclassifies api.workverge.ai hosts so Maya's dashboard counts make sense.

Before you begin

  • ITAM license enabled
  • Access to add or edit servers (types are chosen during create/edit)

Overview

Every server needs a type. Types group hosts in the ITAM dashboard ("5 API servers"), power list filters, and keep CSV imports consistent. Use built-in categories or add custom labels that match WorkVerge's vocabulary.

Built-in types

WorkVerge includes common categories:

  • Physical. On-premises or dedicated hardware
  • Cloud. Generic virtual machines
  • Database. Postgres, Redis, etc.
  • Network. Load balancers, firewalls, appliances

Many teams also use Web, API, and Cache as custom types. Carlos added API before importing production hosts.

Custom types

Create custom types from the server type selector when adding or editing a server, enter a new name and save. Custom types immediately appear in filters and import validation.

WorkVerge type map

  • API. api.workverge.ai, internal REST services
  • Web. Marketing site, status page
  • Database. Postgres primary and replicas
  • Queue. Background workers (custom type)

Where types matter

  • Add / edit server. Type is required on every record
  • Server list filter. "Show me all Database hosts in Maintenance"
  • CSV import. The type column must match an existing type name
  • Dashboard stats. Headline counts by type for Maya's reviews

Keep the list short

Five to eight types cover most SaaS orgs. Too many labels and filters become noise, align types with on-call runbooks, not every microservice name.

Related articles