Enterprise

VictoriaMetrics, VictoriaLogs and VictoriaTraces components are provided in two kinds - Community edition and Enterprise edition .

The community components are open source and are free to use:

Both open-source and enterprise components are available at the following places:

Enterprise executables and Docker images have enterprise suffix in their names and tags.

Valid cases for VictoriaMetrics Enterprise #

The use of Enterprise components is permitted in the following cases:

  • Evaluation use in non-production setups. Pass the -eula command-line flag {% available_from “#” %} to accept the ESA as described in these docs .

  • Production use if you have a valid enterprise contract or valid permit from VictoriaMetrics company. Please contact us via this page if you are interested in such a contract.

  • VictoriaMetrics Cloud is built on top of VictoriaMetrics Enterprise.

See these docs for details on how to run Enterprise components of VictoriaMetrics and VictoriaLogs.

VictoriaMetrics Enterprise features #

VictoriaMetrics Enterprise includes all the features of the community edition , plus the following additional features:

  • Stable releases with long-term support, which contains important bugfixes and security fixes. See these docs .
  • First-class consulting and technical support provided by the core VictoriaMetrics dev team.
  • Monitoring of monitoring - this feature allows forecasting and preventing possible issues in VictoriaMetrics setups.
  • Enterprise security compliance .
  • Prioritizing of feature requests from Enterprise customers.

On top of this, Enterprise package of VictoriaMetrics includes the following features:

Contact us via this page if you are interested in VictoriaMetrics Enterprise.

VictoriaLogs Enterprise features #

VictoriaLogs enterprise includes all the features of the community edition , plus the following additional features:

  • Stable releases with long-term support, which contains important bugfixes and security fixes. See these docs .
  • First-class consulting and technical support provided by the core VictoriaMetrics dev team.
  • Monitoring of monitoring - this feature allows forecasting and preventing possible issues in VictoriaLogs setups.
  • Enterprise security compliance .
  • Prioritizing of feature requests from Enterprise customers.

On top of this, Enterprise package of VictoriaLogs includes the following features:

Contact us via this page if you are interested in VictoriaLogs Enterprise.

Running VictoriaMetrics Enterprise #

Enterprise components are available in the following forms:

Binary releases #

It is allowed to run Enterprise components in cases listed here .

Binary releases of Enterprise components are available at the releases page for VictoriaMetrics , the releases page for VictoriaLogs and the releases page for VictoriaTraces . Enterprise binaries and packages have enterprise suffix in their names. For example, victoria-metrics-linux-amd64-v1.155.0-enterprise.tar.gz.

In order to run binary release of Enterprise component, please download the *-enterprise.tar.gz archive for your OS and architecture from the corresponding releases page and unpack it. Then run the unpacked binary.

All the Enterprise components require specifying the -eula command-line flag {% available_from “#” %} to accept the ESA .

LTS lines support -eula flag starting from releases v1.136.x and v1.148.x. If you need another Enterprise version, please contact the Sales team .

For example, the following command runs VictoriaMetrics Enterprise binary:

      wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.155.0/victoria-metrics-linux-amd64-v1.155.0-enterprise.tar.gz
tar -xzf victoria-metrics-linux-amd64-v1.155.0-enterprise.tar.gz
./victoria-metrics-prod -eula

Docker images #

It is allowed to run Enterprise components in cases listed here .

Docker images for Enterprise components are available at VictoriaMetrics Docker Hub and VictoriaMetrics Quay . Enterprise docker images have enterprise suffix in their names. For example, victoriametrics/victoria-metrics:v1.155.0-enterprise.

In order to run Docker image of VictoriaMetrics Enterprise component, pass the -eula command-line flag {% available_from “#” %} to accept the ESA .

For example, the following command runs VictoriaMetrics Enterprise Docker image:

      docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.155.0-enterprise -eula

Example docker-compose configuration:

      version: "3.5"
services:
  victoriametrics:
    container_name: victoriametrics
    image: victoriametrics/victoria-metrics:v1.155.0-enterprise
    ports:
      - 8428:8428
    volumes:
      - vmdata:/storage
    command:
      - "-storageDataPath=/storage"
      - "-eula"
volumes:
  vmdata: {}

Helm charts #

It is allowed to run Enterprise components in cases listed here .

Helm charts for Enterprise components are available in our VictoriaMetrics Helm repository .

In order to run Enterprise helm chart it is required to accept the ESA and adjust the image tag to the Enterprise one as described in the docker-images section.

For example, the following values file for VictoriaMetrics single-node chart is used to pass -eula command-line flag {% available_from “#” %} to accept the ESA :

      server:
  image:
    tag: v1.155.0-enterprise
  extraArgs:
    eula: "true"

Kubernetes operator #

It is allowed to run Enterprise components in cases listed here .

Enterprise components can be deployed via VictoriaMetrics operator . In order to use Enterprise components it is required to accept the ESA and adjust the image tag to the enterprise one.

For example, the following custom resource for VictoriaMetrics single-node is used to pass -eula command-line flag {% available_from “#” %} to accept the ESA :

      apiVersion: operator.victoriametrics.com/v1beta1
kind: VMSingle
metadata:
  name: example-vmsingle
spec:
  retentionPeriod: "1"
  image:
    tag: v1.155.0-enterprise
  extraArgs:
    eula: "true"

See the full list of the CRD specifications in the Operator API .

FIPS Compatibility #

VictoriaMetrics Enterprise supports FIPS 140-3 compliant mode starting with version Available from v1.118.0 , using the Go FIPS 140-3 Cryptographic Module . This ensures all cryptographic operations use a validated FIPS module.

Builds are available for amd64 and arm64 architectures.

Example archive:

victoria-metrics-linux-amd64-v1.155.0-enterprise.tar.gz

Includes:

  • victoria-metrics-prod (standard)
  • victoria-metrics-fips (FIPS-compatible)

Example Docker image:

victoriametrics/victoria-metrics:v1.155.0-enterprise-fips – uses the FIPS-compatible binary and based on scratch image. #

Section below contains backward-compatible anchors for links that were moved or renamed.

Updating the license key #

License key is no longer needed to run VictoriaMetrics Enterprise. Please see how to run VictoriaMetrics enterprise .

What Happens to Licensed Components When a License Expires #

License key is no longer needed to run VictoriaMetrics Enterprise. Please see how to run VictoriaMetrics enterprise .

Monitoring license expiration #

License key is no longer needed to run VictoriaMetrics Enterprise. Please see how to run VictoriaMetrics enterprise .

Previous Streaming aggregation Next Cluster Per Tenant Statistic