Get early access
Features · Discovery & Mapping · Tagging & Custom Fields
Discovery & Mapping · Tagging & Custom Fields

Model the parts of your fleet
auto-discovery can't see.

Ownership, environment, contract end date, jump-host group — discovery finds the operational bits; tags carry the organisational ones. Free-form, structured when you want it, queryable everywhere.

web-prod-04 · metadata
tags env:prod · role:web · team:core owner platform@acme.io cost centre CC-4102 contract ends 2027-03-31 used by alert routing, reports, RBAC
— Why this matters

The fleet has structure. It just is not in the hostname.

01

key:value survives contact with reality.

Free-form labels rot. env:prod and team:core can be selected against, which is what makes them worth maintaining.

02

Tags are the routing layer.

Alert targets, report scopes and policy selectors all resolve through them. A tag is not decoration, it is how a rule finds its hosts.

03

Some facts have no field.

Contract end date, cost centre, the person to wake. Custom fields hold what the schema never anticipated.

— What's included

Where the metadata shows up.

key:value tags
Applied per host, selectable everywhere a scope is asked for.
Custom fields
Dynamic key-value metadata, edited on its own tab in the server form.
Alert targeting
Include and exclude by tag rather than by naming twenty-four hosts.
Report scope
A report defined for env:prod keeps working when prod grows.
Policy selectors
The policy engine targets by tag, so a new host inherits the rules the moment it is tagged.
Cost tracking
Per host, with an interval and currency, rolled up by whatever you tagged.
— Works with

Connected capabilities

Server Groups
Color-coded grouping built on top of a tag selector — a saved query, basically.
→
Smart Alerts
Scope alert rules to tag selectors instead of static host lists.
→
Custom Dashboards
Filter widgets by tag for per-team / per-env views without duplicating dashboards.
→
Reports
Schedule per-tag exports for owner teams.
→
— FAQ

Questions, answered honestly.

Is there a limit? +
No hard limit on tag count or custom-field count. Soft guideline: under 20 tags per host stays readable.
Can I sync tags from somewhere else? +
Yes — webhook or REST endpoint receives a tag manifest. Common sources: Terraform tags = {}, Ansible inventory vars, the cloud provider's own tags.
Do tags affect billing? +
No. Pricing is per-host; tags are metadata.

Make your fleet queryable.

Tagging is free on every plan. Custom-field schema unlocks at Starter.

Get early access Back to Discovery & Mapping