Skip to content

Resource Usage and Limits

Every service requires infrastructure resources. Hostly measures actual usage at the level of the associated workspace.

Billing and limit scope

An account can have multiple workspaces. Each workspace is its own monetization, plan, and usage unit. The account and individual users are not monetized separately.

This means:

  • A plan is assigned to a workspace
  • Resource usage and limits are calculated per workspace
  • Services consume the resource budget of their workspace
  • Multiple workspaces within the same account are treated separately

Plans

Hostly currently distinguishes:

  • Free Tier
  • Paid Tier

In the Free Tier, each workspace can have at most one created service. Compute, RAM, and egress traffic have usage-based limits. Volumes are available only in the Paid Tier.

SSL and high availability are available in both plans. High availability significantly increases resource usage because it runs two service instances.

Compute

Compute is measured in core hours. What matters is what share of a CPU core was actually used for how long.

Example:

text
0.5 CPU cores for 2 hours = 1 core hour

Hostly measures actual CPU usage with microsecond precision and does not round usage time up to full minutes or hours. This allows billing to be as fair as possible for both Hostly and the user.

The monetary amount is displayed or billed to two decimal places regardless of measurement precision.

A stopped or paused service does not consume compute resources.

RAM

RAM is measured in GiB-hours. Hostly measures the memory actually used over time.

Example:

text
2 GiB RAM for 3 hours = 6 GiB-hours

A stopped or paused service does not consume RAM.

Persistent storage

Volumes are billed based on the actually used storage size over time in GiB-days and are available only in the Paid Tier.

Example:

text
2 GiB reserved storage for 3 days = 6 GiB-days

The following applies:

  • While running, the reserved size of the volume is billed
  • During pause, the volume remains; its reserved size continues to be billed
  • During stop, it is deleted and is no longer billed afterward
  • When the service is deleted, it is also deleted and is no longer billed afterward

The minimum size of a created volume is 1 GB. Billing is based only on the configured size.

Egress traffic

Egress traffic is data traffic that leaves Hostly over the internet.

Currently not included:

  • internal Hostly administration traffic
  • HTTP headers

Display and billing happen within the billing period in the unit TiB.

Number of services

Every created and non-deleted service counts, regardless of whether it is running, paused, or stopped.

In the Free Tier, each workspace can have at most one service. If this service is deleted, another service can then be created in the same workspace.

Individual billing period

The Free Tier does not use a calendar month. Each workspace has its own 30-day billing period that starts with the beginning of its subscription.

All usage-based limits for this workspace are reset at the same time at the end of the period.

Limit almost reached

The dashboard warns when a limit will soon be reached.

Limit reached

As soon as compute, RAM, or egress traffic in the Free Tier reaches the respective workspace limit, Hostly immediately pauses the service.

text
Limit reached
    |
    v
Service is paused
    |
    v
Email notification
    |
    v
Limits are reset at the period boundary
    |
    v
Service starts automatically when resources are available again

During the pause, the Hostly configuration and the service domain fragment are retained. Volumes are not available in the Free Tier.

Switching to the Paid Tier is applied immediately. The service can then continue running immediately, provided all other requirements are met.

High availability and usage

High availability starts two instances of the same service. Base compute and RAM usage are roughly doubled as a result. In the Free Tier, limits can therefore be reached faster.