Hosting Types

What Hosting Types do

Hosting Types help you group infrastructure and platform environments into reporting-friendly categories.

In Settings, this is where administrators define a named hosting classification, connect it to one or more hosting platforms, and align it to the asset types that should roll into that classification.

This matters because Yarken does not only need to know the raw source platform name. It also needs a consistent business-facing grouping that can be reused across reporting, asset analysis, and technology finance views.

How Hosting Types work in Settings

The current Settings screen shows Hosting Types as a managed list with three key columns:

Field

What it means

Hosting Type

The reporting category used in Yarken, such as Cloud, Mainframes, On-Prem, Servers, or Platform.

Hosting Platform

The specific platforms that should be treated as part of that hosting type.

Asset Type

The asset type or types that align to that hosting type.

This means a Hosting Type acts as a classification layer between low-level platform labels and the broader infrastructure view used in Yarken.

Why this setting matters

Hosting platforms often arrive in many different names and source-specific labels.

Hosting Types give administrators a way to normalise that detail into a smaller set of categories that are easier to analyse and explain.

For example, multiple cloud or infrastructure platform names can be grouped under one Hosting Type so dashboards and reporting stay consistent.

This makes it easier to:

  1. Review infrastructure spend by hosting model.

  2. Keep platform naming consistent across the environment.

  3. Align asset analysis to broader technology finance reporting.

  4. Support hosting-oriented views such as Cloud TCO, Mainframe TCO, On-Prem TCO, and Server TCO.

What admins can do here

From the Hosting Types setting, administrators can:

  1. Review the existing hosting classifications.

  2. Search the current list.

  3. Add a new Hosting Type.

  4. Edit an existing Hosting Type and its mappings.

  5. Delete a Hosting Type that is no longer needed.

Use + ADD NEW when a new hosting model, platform grouping, or reporting classification needs to be introduced.

How to think about the structure

A good Hosting Type should represent a category that makes sense to the people who review infrastructure cost and asset ownership.

The Hosting Platform field should capture the underlying platforms that belong to that category.

The Asset Type field should reflect the asset classes that should be analysed under that hosting view.

Keep the structure stable and meaningful. If different platform names really belong to the same reporting concept, group them under one Hosting Type instead of creating unnecessary categories.

Common examples

The current Settings guidance and screen example show common hosting classifications such as:

  1. Cloud

  2. Mainframes

  3. On-Prem

  4. Servers

  5. Platform

These are useful because they describe the infrastructure model in a way that business and technology stakeholders can both understand.


Related content

Settings

Admin, Users, and Settings