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:

Upcoming Conferences & Meetups: Where to Meet Our Team

We love connecting with our community in person, and the next few months are packed with opportunities to do just that. Our team will be attending (and in some cases, speaking at) several conferences and meetups. If you’re planning to be there, we’d love to meet you—here’s where you can find us.

VictoriaMetrics Long-Term Support (LTS): H2 2025 Update

As we’re half-way through the year, we’d like to take this opportunity to provide an update on the most recent changes in our Long-Term Support (LTS) releases.

Creating a Sustainable Open Source Business Model - Introduction

Open source defies everything you’ve ever heard or learned about business before. This blog post is an introduction to how we’re creating a sustainable business model rooted in open source.

Full-Stack Observability with VictoriaMetrics in the OTel Demo

The OpenTelemetry Astronomy Shop demo has long served as a reference environment for exploring observability in distributed systems, but until now it shipped with only a Prometheus datasource. VictoriaMetrics forked the demo and extended it with VictoriaMetrics, VictoriaLogs, and VictoriaTraces, providing insights into VictoriaMetrics’ observability stack where metrics, logs, and traces flow into a unified backend.