In StatusCast your overall account is centered around the service components that you create; all components have a status that you will manipulate by creating incidents. Components can be just about anything, a few examples of components may include:

Geographic regions, such as West Coast and East Coast
Service systems such as Live Chat, Phone, and Email support
Hardware clusters
Servers(for private and internal application use)

Set the status of a component by creating an incident that affects it or by setting the status directly.

Create up to 5-levels* of sub-components to help organize your services. Note that by default a root component will inherit its sub-component status if an incident affects the sub-component. Root components will inherit the most severe status if multiple sub-components have different incidents raised at the same time.

*Service component level depth is based on your StatusCast subscription.