Predictable Pricing
Pay per active time series and ingestion rates based on capacity tiers.
VictoriaMetrics Cloud:
More Observability,
Less to Manage,
Predictable Pricing
Simple. Reliable. Efficient. We run it, you use it.
Start Free Trial
No credit card required.
VictoriaMetrics Cloud
From $200/month. Free for 30 days
Get the fully managed observability solution built on open-source VictoriaMetrics, VictoriaLogs & VictoriaTraces with added enterprise features. Benefit from lower costs with pricing built around Capacity Tiers. Avoid surprise charges with transparent deployment limits and alerts.
A drop-in home for your Prometheus data
Schemaless full-text search over everything you log
A New Home for Your OpenTelemetry Distributed Tracing
Whichever backends you run, these are included
Managed VictoriaMetrics Managed VictoriaMetrics More data in less storage
2.5x compression vs Prometheus, downsampling & retention rules to keep what you’ll actually need.Managed VictoriaMetrics Ingest everything
OpenTelemetry, CloudWatch, InfluxDB, Datadog, New Relic, OpenTSDB and Graphite protocols.Managed VictoriaMetrics Managed Prometheus
VictoriaMetrics Cloud works as a managed Prometheus: send data via Prometheus or vmagent, then use its endpoint as a Grafana data source.Managed VictoriaMetrics Single-node or cluster
Start small and move to a cluster for HA & scale.Managed VictoriaMetrics Alerting
Define your rules & get immediate alerts as issues arise, enabling swift action & minimizing disruption to your users.Managed VictoriaLogs Predictable Pricing
Pay per log and data ingestion rate based on capacity tiers.Managed VictoriaLogs More data in less storage
Up to 15x less disk usage for the same stored logs.Managed VictoriaLogs Ship from your agents
Fluent Bit, Vector, Logstash, Filebeat, Promtail, Telegraf, syslog, journald, the Datadog agent, or OTLP straight from the OpenTelemetry Collector.Managed VictoriaLogs Full-text queries
Use LogsQL for fast, flexible log querying with autocomplete, query history, full-text search, and multiple result views including table, JSON, group, and live modes.Managed VictoriaLogs Schemaless
Send logs as they are and query them immediately. No schema to define upfront and nothing to migrate when the shape of your logs changes.Managed VictoriaLogs Find Patterns
Spot noisy or rare fields and streams in your logs, inspect top and bottom values, and quickly filter to the logs that matter.Managed VictoriaTraces Predictable Pricing
Pay per span and data ingestion rate based on capacity tiers.Managed VictoriaTraces More data in less storage
Up to 44% less storage needed for the same data.Managed VictoriaTraces OpenTelemetry native
Send spans over OTLP/HTTP from the OpenTelemetry Collector, Grafana Alloy, or vtagent.Managed VictoriaTraces One Language. Two Signals.
Spans are stored as structured data and queried with LogsQL.Managed VictoriaTraces Visualize your traces
Explore your traces in the built-in UI, Grafana, or Perses.Managed VictoriaTraces Works With Your Tools
Jaeger- and Tempo-compatible APIs for querying.With Every Deployment Predictable costs
Transparent deployment limits with alerts before you reach them, a usage dashboard for network traffic, per-hour metering, and the exact cost of compute and storage shown before you confirm any change.With Every Deployment Fully managed
Deployments fully managed by the team behind VictoriaMetrics. You don’t have to maintain or upgrade anything. Automated backups at no extra cost. Every deployment gets dedicated resources.With Every Deployment Hosted on AWS
Your deployments run on AWS, with the option for AWS PrivateLink, which enables even more secure communication with VictoriaMetrics Cloud deployments directly from your VPC.With Every Deployment Kubernetes ready
Use the VictoriaMetrics Helm charts and Operator to monitor your cluster end to end, and send container logs and spans to a managed VictoriaLogs endpoint using your existing collectorsWith Every Deployment Multitenancy
Easily serve multiple teams (tenants) with one Cluster deployment by having a dedicated namespace for each team.With Every Deployment Up to 99.95% SLA
Production SLAs, streamlined support (customer portal), access to proof-of-concept assistance to rapidly qualify new use cases.
Business Benefits
Resource and cost efficiencies with VictoriaMetrics Cloud.
Engineering Benefits
We handle upgrades, infrastructure, and automated backups so your team can focus on shipping features.
Managed Migration
Migrate from costly, less scalable metrics, logs & traces solutions.
Agentic observability
Connect any AI assistant to the hosted MCP server. Use VictoriaMetrics Skills to query metrics, log exploration, and trace analysis.Predictable billing
Choose a capacity tier and know the bill before the month starts. No surprise overages, per-host fees, or per-seat charges.Observability as a Service
Build observability as a service for your organization.Scale up or down.
Scale up or down in a few clicks. Switch to cluster deployments to handle more data, more tenants, and more concurrent queries.
Flexibility
Run only the backends you need: metrics, logs, or traces to build observability as a service for your organization.Automation-ready
Automate deployments with Terraform and use the dozens of integrations that ship with VictoriaMetrics Cloud.No vendor lock-in
Keep your collectors, dashboards, and query languages. Every deployment runs the same open-source software you could run yourself.Expert Setup & Maintenance
Have your configuration and maintenance set up and handled by the experts at VictoriaMetrics so that you can focus on monitoring.
Managed Prometheus
Managed Prometheus services from AWS, GCP, or AzureCloud Alternatives
InfluxDB Cloud or Grafana CloudLog and trace management
Elasticsearch, Loki, ClickHouse, Jaeger, or Grafana TempoOn-Premise
Your on-premise setup
Pricing
Pay for the capacity you plan: Clear tier structure and transparent limits make monthly costs easy to forecast.
VictoriaMetrics
From $200/month. Initial Tier.
- Active time series
- 500k
- datapoints/sec
- 16.6k
- Daily read volume
- 170 GB
- Business days & hours support
- Included
AWS Marketplace & credit card payment available (after your trial ends)
VictoriaLogs
From $200/month. Initial Tier.
- Logs/sec Ingested
- 800
- Data Ingestion Rate
- 0.8 MB/s
- New Streams/24hs
- 50
- Read rate
- 4.6 GB/sec
- Business days & hours support
- Included
AWS Marketplace & credit card payment available (after your trial ends)
VictoriaTraces
Our new database for storing & querying distributed tracing data
- Spans/sec Ingested
- 800
- Data Ingestion Rate
- 0.8 MB/s
- New Streams/24hs
- 50
- Read rate
- 4.6 GB/sec
- Business days & hours support
- Included
AWS Marketplace & credit card payment available (after your trial ends)
Pricing Calculator
see how much your setup would cost
Free · 1 Week Trial
Fully Managed Proof of Concept
For Large-Scale Setups
For Horizontal Scaling, Data Replication, and/or Multitenancy Needs
You have
- High volumes of data
- Integration complexity
- Expensive setup / growing costs
You need
- Offload observability maintenance
- Improve operability
- Have reasonable pricing
- Overcome performance issues
- Spend AWS commitments wisely
You get
- Expert help for the perfect setup
- Scope limitation: only what you need
- Business hours support
- Better understanding of your observability costs
PoC Process
Step 1
You reach out to us
Step 2
We assign a Solutions Engineer & Account Manager
Step 3
You get expert-led setup & migration
Step 4
You see the results, measure the value
Step 5
We optimize your setup further
Step 6
You decide: go or no-go
FAQs
- Deployment usage in VictoriaMetrics Cloud is metered per hour.
The following billing options are available in VictoriaMetrics Cloud:
- Monthly billing on a 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 (after your trial ends), 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, the charge will happen on the 5th of every subsequent month, independent of whether it is a weekday or weekend.
If you’re using AWS Marketplace, the bill for the previous month is finalized at the start of each new month. AWS usually charges the bill between the 1st and 5th 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 the 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 use for 30 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 Europe (Frankfurt, eu-central-1), Europe (Ireland, eu-west-1), US East (N. Virginia, us-east-1), US East (Ohio, us-east-2), and Asia Pacific (Singapore, 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 any Private Pricing spend commitments with AWS, you can apply them to 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; they are deployed to a separate account, and you interact with them from your environments via HTTPS.
- Transit: Only TLS, no 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 to write and query metrics. The only scenario where a call from the platform to your services can occur is when it sends an alert (if notifications are set up in your environment).
You don’t need public internet access; you can use AWS PrivateLink instead.
- There are no requirements from our side.
Yes, VictoriaMetrics Cloud supports private connectivity through AWS PrivateLink. Traffic to a deployment over PrivateLink stays on the AWS private network and never traverses the public internet.
In summary, PrivateLink can be set up manually on an individual basis and upon request. It also incurs additional AWS costs, which are not included in the VictoriaMetrics Cloud offering.
In any case, public access is secure because all connections use TLS.
- 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, alerting rules, and other integrations).
Every deployment gets automated backups at no extra cost and with no configuration, while the VictoriaMetrics team monitors deployment health 24/7.
Check out our open-source docs for more information.
- VictoriaMetrics Cloud deployments run in isolated environments so that scaling can be done freely. We have processes that ensure zero downtime in cluster setups and very low downtime in single setups.
We have not detected or 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 they are expected to perform well compared, for example, with heavily loaded on-prem setups.
- Users can choose between different AWS regions, and selecting the one closest helps.
- The latency from running in the cloud is not noticeable for dashboard queries or ingestion operations.
- 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, for deployment issues, we can notify you with alerts that include recommendations for possible fixes. You can also 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 mechanisms such as:
- Cardinality explorer
- Query tracing
- Top queries
- Active queries
- In addition to other tools, such as the Metric relabel debugger, Downsampling filters debugger, Retention filters debugger, Raw query view, etc.
Where issues arise, support is always available to help you.
- API calls: no additional costs
- Data transfers: $0.09 per GB for external traffic, which matches AWS’ rate
- Storage: price is $0.511 per GB per month
- Yes. You can subscribe via AWS Marketplace (see docs).
- Yes, VictoriaMetrics Cloud supports a fully managed VictoriaTraces service. You can ingest, store, and query distributed traces without operating VictoriaTraces yourself.
- VictoriaMetrics Cloud supports managed VictoriaMetrics (single-node and cluster), managed VictoriaLogs (single-node), and managed VictoriaTraces (single-node). A traces deployment is created and managed from the same console, using the same workflow as the others.
- Not automatically in this release. Cross-signal workflows are possible today by connecting Grafana to all three deployments and pivoting between them manually. We provide guides for manual correlation. Automatic correlation is on the roadmap and should be available late 2026.
- Single-node deployments only, with no High Availability
- Ingestion over OTLP/HTTP only (OTLP over gRPC is not supported)
- No user-defined alerting or recording rules for traces
- No automatic correlation between metrics, logs, and traces
- No support for trace deployments in the Terraform provider
- The Grafana Tempo API is experimental
- No automated migration process. We provide migration guides. Also, the cloud team can migrate your data on request.
Need Support?
Read More Info
Support From The Core Team
Get enhanced technical support, architectural and security guidance, help with adoption and integration, and performance analytics.
