Deployments #

VictoriaMetrics Cloud is a DBaaS (Database as a Service) product for VictoriaMetrics. This means that you need to create a deployment before sending data to it. It is a fully managed service that allows you to deploy and manage your own instances of VictoriaMetrics and VictoriaLogs in the cloud.

Tip

Regular use cases of VictoriaMetrics Cloud are monitoring applications, infrastructure, or services, running in different setups like on-prem, Private, Public or Hybrid Cloud, Edge devices or IoT.

Deployment types #

At the moment, the following Deployment types are available in VictoriaMetrics Cloud:

  • VictoriaMetrics single-node and cluster instances
  • VictoriaLogs single-node instances
  • Coming soon: VictoriaTraces instances

Capacity Tiers #

When deploying a new VictoriaMetrics Cloud instance, users need to choose from a set of configurations, called Capacity Tiers, that are tested to serve a certain load and conditions, with a fixed CPU and Memory allocation.

DBaaS means Flexibility

This approach ensures that pay-as-you-go users can rely on transparent and predictable pricing, without fearing unexpected cost increases overnight.

  • While VictoriaMetrics Capacity Tiers for single-node instances, provide benchmarking capacities across various magnitudes, such as Active Time Series, Churn Rate or Ingestion Rate, cluster instances are normally tailored for each use case, to ensure cost savings and performance.
  • VictoriaLogs Capacity Tiers for single-node instances are presented in a simpler way, based on CPU and RAM capacities. The Cluster version is not available at the moment.

You can also read more about the differences between single and cluster instances .

Limits #

Apart from the capacities per tier described in the corresponding pages for VictoriaMetrics and VictoriaLogs , VictoriaMetrics Cloud also enforces hard limits in order to ensure operations. Users can expect receiving alerts when these thresholds are surpassed, and new data eventually being rejected. The majority of these limits are available under the Monitor tab of the deployments section for each of your instances.

More information about deployments #