1. Blog
    2. /
  2. FIPS 140-3 Compatible Builds for VictoriaMetrics Enterprise Components
FIPS 140-3 Compatible Builds for VictoriaMetrics Enterprise Components

FIPS 140-3 Compatible Builds for VictoriaMetrics Enterprise Components

Share: Share on LinkedIn Share on X (Twitter)

VictoriaMetrics introduces FIPS 140-3 compatible builds for its components, starting with version 1.117.0. These builds utilize Google’s FIPS 140-3 validated BoringCrypto module.

This is critical for customers in regulated environments (federal government, finance, healthcare) to meet FIPS 140-3 cryptographic requirements for data encryption, TLS, and secure communications.

While VictoriaMetrics itself is not a FIPS-certified cryptographic module, these builds ensure all cryptographic operations are handled by the validated BoringCrypto module. This simplifies compliance for system integrators and customers undergoing FedRAMP, HIPAA, or similar audits.

Availability

#

FIPS-compatible binaries are on our GitHub repository; images are on DockerHub or Quay registries.

  • Binaries: Attached to enterprise assets, alongside regular versions. Example: victoria-metrics-darwin-amd64-v1.117.0-enterprise.tar.gz (There is a victoriametrics-prod-fips binary in the archive).
  • Container Images: scratch-based, with a -fips suffix in tags. Example: v1.117.1-enterprise-cluster-fips.
  • Architecture Support: Available for arm64 and amd64.

Performance

#

Our internal tests show no measurable impact on resource consumption or read/write request efficiency with FIPS-compatible builds.

CGO support for vmagent’s Kafka integration was disabled for simplification. This only affects the underlying library choice (Go-native vs. C-libraries) and does not impact functionality.

Please Note

#

These VictoriaMetrics builds use FIPS 140-3 validated cryptographic modules (BoringCrypto).

However, VictoriaMetrics as a complete software solution has not undergone formal FIPS 140-3 certification under the CMVP.

Get Started & Try VictoriaMetrics Enterprise

#

Ready to enhance your observability stack with FIPS 140-3 compatible components?

Request a VictoriaMetrics Enterprise Trial License, or contact our Sales team to get more information.

Leave a comment below or Contact Us if you have any questions!
comments powered by Disqus

You might also like:

VictoriaLogs Basics: What You Need to Know, with Examples & Visuals

Cluster mode in VictoriaLogs is not a separate build. It is the same victoria-logs binary started with different flags, so you can scale out without a migration step. Storage nodes persist data on disk, while gateway nodes can stay stateless by pointing to storage with -storageNode. It also ships with practical safety switches, like read-only protection when -storageDataPath runs low and optional partial results when a storage node is down.

What's New in VictoriaMetrics Cloud Q4 2025? New tiers, more deployment options, IaC and alerting rules.

In the last quarter of 2025, VictoriaMetrics Cloud brings many great features: New powerful Capacity Tiers, the expansion to the us-east-1 (N.Virginia) AWS region in the US, new Notification Groups, a Terraform provider to complete your IaC, 9 brand new Alerting Rule Integrations and much more.

Vibe coding tools observability with VictoriaMetrics Stack and OpenTelemetry

Learn how to add observability to Vibe Coding Tools using OpenTelemetry and the VictoriaMetrics Stack. This guide explains how to configure popular vibe coding tools to export their metrics telemetry and get insights about your vibe coding sessions.

How a US Software Provider Improved Traffic Alerting with VictoriaMetrics Anomaly Detection

VictoriaMetrics Anomaly Detection enables reliable alerting for highly variable, multi-domain traffic without relying on static thresholds. In this case study, fine-tuned models, backtesting, and clear visualization helped reduce alert noise, improve confidence in anomaly detection, and lower operational overhead.