Scale to Billions of Metrics & Logs
VictoriaMetrics Cloud: Managed Observability

The following billing options are available in VictoriaMetrics Cloud:

• Monthly billing on pay-as-you-go basis
• Annual / multi-year contract

Contact sales@victoriametrics.com for more information.

If you’re paying for the service via card then charges will occur monthly at the end of the billing period, which begins on the day you added your card. For example, if you added the card on December 5th, charge will happen on the 5th day of every subsequent month.

In case you’re using AWS Marketplace - the bill for the previous month is finalized at the beginning of each new month. The bill is charged usually between the 3rd and the 5th day of the month. Learn more at AWS Knowledge Center.

When you’re creating or making changes (up or down-scaling compute resources and changing a disk size) to your deployment you’ll see an exact cost of your compute and storage resources. The variable part of the total cost is network traffic which you can control using the Usage dashboard.

Upon registering your account with VictoriaMetrics Cloud, you will receive $200 in credits automatically. These credits are valid for utilization over the following 7 days. As the trial period concludes, you will receive a notification prompting you to set up a payment method if you intend to continue using the service.

Currently we run all deployments on AWS in eu-central-1, eu-west-1, us-east-2, and ap-southeast-1. If you have a preference for another AWS region, please contact us at support@victoriametrics.com

The VictoriaMetrics Cloud control plane is hosted and 100% built on AWS.

If you have some Private Pricing spend commitments with AWS, you can use them for VictoriaMetrics Cloud. This is because VictoriaMetrics Cloud is included in the AWS SaaS Marketplace catalog with the "Deployed on AWS" badge (validated as 100% built on AWS).

Being built on AWS also allows VictoriaMetrics Cloud to deploy quickly in new regions.

• For console (UI): Google SSO and/or email + password
• For working with deployments (API of VictoriaMetrics instances): Bearer tokens
• For console API (automated actions with deployments, access tokens, alerting/recording rules): API keys

It doesn’t require any permissions. VictoriaMetrics Cloud instances are not deployed to your account, but to a separate one: you just interact with them from your environments via https.

• Transit: Only TLS, no any additional encryption
• At rest: We use encrypted EBS volumes

VictoriaMetrics Cloud doesn’t require access to AWS services; your services need access to the platform for writing metrics and querying. The only scenario where a call from the platform to your services can occur is when it sends a notification about alert (if notifications are set up in your environment).

You don’t have to use public internet access; the option to use AWS Private Link is available.

There are no requirements from our side.

A VPC endpoint enables customers to privately connect to supported AWS services and VPC endpoint services powered by AWS PrivateLink.

In summary, PrivateLink can be set up manually on an individual basis, upon request. It also implies extra cost because there is a cost associated with it in AWS, and it’s not included in the VictoriaMetrics Cloud offering.

In any case, it’s important to note that connecting via public access is secure because connection is done via TLS with all endpoints.

We charge $0.09 per GB for external traffic, which matches AWS’ rate. Estimated traffic costs typically range from $1 to $30 per month, depending on deployment size and regular usage (such as data visualization, evaluation recording, and alerting rules and other integrations).

We would need more information, but we are not that different from Open Source. Check out our open source docs for more information

VictoriaMetrics Cloud deployments run in isolated environments, so scaling can be done freely. We have processes that ensure zero-downtime in cluster setups and very low downtime for single setups.

We have not detected nor been notified by users of latency or performance problems in VictoriaMetrics Cloud. This is probably due to the following reasons:

• VictoriaMetrics Cloud deployments run in isolated environments, so there’s no interference and is expected to run at good performance when compared, for example, with heavy-loaded on-prem setups.
• Users can choose between different AWS regions, and selecting one that is closer helps.
• The latency induced from running in the cloud is not noticeable for querying in dashboards or ingestion operation.

See our SLAs

Yes, logs and some of the metrics for your instances are available in the VictoriaMetrics Console. We also provide alert notifications about issues with your instances.

We have integration with CloudWatch, you can find it in Console -> Integrations. We don’t have X-Ray or AWS Config integrations at present.

Yes, in case of deployment issues, we can notify you with alerts, which have recommendations for possible fixes. You also can use instance logs available on the Logs tab (log messages also usually contain recommendations) and instance metrics are available on the Monitoring tab.

We also have such mechanisms like:

• Cardinality explorer
• Query tracing
• Top queries
• Active queries
• In addition to other tools, like Metric relabel debugger, Downsampling filters debugger, Retention filters debugger, Raw query view, etc.

Where issues arise, support is always available to help you.

Pricing is based in tiers

• API calls: no additional costs
• Data transfers: see here
• Storage: price is $1.46 for 10 GB/month

Yes. You can subscribe via AWS marketplace (see docs).