Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
A FIPS-compliant AI chat application.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev:
Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.
LibreChat is an open-source AI chat application that allows users to interact with various AI models through a unified interface. Chainguard's librechat-fips container image is a FIPS-compliant version comparable to the upstream LibreChat image available on Docker Hub.
Important:* When deploying the Chainguard LibreChat image to Kubernetes, you must use the Chainguard IAMGuarded MongoDB Helm chart as a separate installation:
These FIPS-compliant images include OpenSSL FIPS provider and are built with FIPS-validated cryptographic modules. Key FIPS features include:
The FIPS version is rigorously tested with TLS-enabled Redis connections to ensure all cryptographic operations comply with FIPS 140-2 requirements.
LibreChat FIPS requires a MongoDB database and several environment variables for encryption and authentication. Below are examples for both Docker and Kubernetes deployments.
First, start a MongoDB container:
Generate required secrets:
Run LibreChat FIPS:
Access the application at http://localhost:3080.
For production deployments requiring FIPS-compliant TLS connections with Redis:
Start Redis with TLS:
Start LibreChat FIPS with TLS Redis:
Verify TLS connection:
LibreChat FIPS can be deployed to Kubernetes using the official Helm chart with Chainguard FIPS images.
First, create a values file with your configuration:
Create Kubernetes secrets for sensitive values:
Deploy MongoDB using Helm (if not using an external database):
Install LibreChat FIPS:
Verify the deployment:
You should see logs indicating:
Connected to MongoDBServer listening on all interfaces at port 3080LibreChat FIPS requires the following environment variables:
| Variable | Description | Example | 
|---|---|---|
| 
 | MongoDB connection string | 
 | 
| 
 | Secret for JWT token signing | Generated with  | 
| 
 | Secret for refresh token signing | Generated with  | 
| 
 | Encryption key for credentials | Generated with  | 
| 
 | Initialization vector for encryption | Generated with  | 
Optional environment variables for Redis and additional configuration:
| Variable | Description | Default | 
|---|---|---|
| 
 | Enable Redis caching | 
 | 
| 
 | Redis connection URI (use  | - | 
| 
 | Path to Redis CA certificate for TLS | - | 
| 
 | Enable user registration | 
 | 
| 
 | Enable social authentication | 
 | 
| 
 | API key for OpenAI integration | - | 
| 
 | API key for Anthropic Claude integration | - | 
Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.
All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.
The main features of Chainguard Containers include:
For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.
In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.
Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.
To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.
To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
Artistic-1.0-Perl
Artistic-2.0
BSD-1-Clause
BSD-2-Clause
BSD-3-Clause
BSD-4-Clause-UC
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementThis is a FIPS validated image for FedRAMP compliance.
This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.
Learn more about STIGsGet started with STIGs