VictoriaStack is Apache-2.0 licensed and complete on its own: the open source version runs in production at any scale described in these docs. The Enterprise offering adds two things: technical support from the engineers who build the stack, and a set of features for Enterprise-level installations.

Enterprise components include all the features of the community edition - start with the community edition today and add Enterprise later without re-architecting, re-ingesting, or rewriting anything.

Technical support #

The main value of Enterprise is support from the people who develop VictoriaMetrics, VictoriaLogs, and VictoriaTraces. An Enterprise contract includes:

  • A strict SLA on response times, with online support and dedicated chat rooms, so questions go straight to the engineering team instead of a ticket queue.
  • Priority bug fixing and prioritized feature requests for issues that affect your installation.
  • CVE fixes in the Enterprise version within 3 business days.
  • Architectural guidance: regular audits of the setup and its capacity, plus verification of the security of the installation and of data access.

This is also the reason many teams move to Enterprise without needing any of the extra features: the software already works for them, and what they buy is the guarantee that somebody who knows it is reachable when it doesn’t.

Long-term support releases #

VictoriaStack releases often, and following the latest release is the recommended way to stay current. LTS lines for VictoriaMetrics and VictoriaLogs are for teams that prefer rare, low-risk updates instead: every LTS line receives bugfixes and security fixes for 12 months, a new LTS line appears every 6 months, and two lines are supported at any moment. That leaves up to 6 months to migrate between lines.

Every fix that lands in an LTS release also lands in the latest release, so users of the community edition get the same fixes by upgrading to the latest version.

Additional features #

Enterprise adds the following capabilities, most of them to VictoriaMetrics:

FeatureWhat it gives you
Downsamplingkeeps long retention affordable by storing older data at lower resolution
Retention filtersdifferent retention per team, environment, or tenant
Anomaly detectionvmanomaly learns expected data behavior and writes a unified anomaly score to VictoriaMetrics for contextual alerting and investigation.
vmbackupmanagerscheduled backups with their own retention, to S3, GCS, or Azure Blob Storage
mTLS and automatic TLS certificatesmutual TLS between components and clients, including mTLS-based routing and IP filters in vmauth
Kafka and Google PubSubingestion from and to message queues

See the full list of Enterprise features in the product docs, and the Enterprise page for the offering itself.

Community and Enterprise are compatible #

Nothing has to be planned in advance to keep the Enterprise path open:

  • The features overlap, they don’t diverge. Enterprise includes everything the community edition has, so no configuration, query, dashboard, or alerting rule stops working.
  • Switching is a change of image and a license key. Enterprise executables and Docker images carry the enterprise suffix in their names and tags, and the license is passed via the -license or -licenseFile flag. The data stays where it is: no migration, no re-ingestion.
  • Editions mix per component. Only the components that use Enterprise features need an Enterprise license. For example, vmanomaly requires a license itself, while it can read from Community or Enterprise single-node or clustered VictoriaMetrics, VictoriaLogs, or VictoriaTraces and write results to VictoriaMetrics.
  • Enterprise components are free to evaluate. They can be used in non-production setups with a trial license ; production use requires an Enterprise contract.

VictoriaMetrics Cloud is built on top of VictoriaMetrics Enterprise, so it is a third option for teams that prefer not to operate the stack themselves.

How to get it #