// Bitnami alternatives
Bitnami alternatives in 2026.
Every way to replace Bitnami images, compared.
Since Broadcom moved versioned Bitnami images to the unmaintained bitnamilegacy repository, teams have been looking for a Bitnami replacement that does not break their Helm charts. The ten images below alone account for roughly 75 million bitnamilegacy pulls. This page compares every alternative, then gives a migration guide for each image.
Trusted globally by enterprises
What happened to Bitnami
Bitnami packaged open source applications as ready-to-run container images and Helm charts, and for years its free images on Docker Hub were the default way to deploy PostgreSQL, Redis, Kafka, RabbitMQ and dozens of other workloads on Kubernetes. VMware acquired Bitnami, and Broadcom acquired VMware.
On 16 July 2025 Bitnami announced the change. From 28 August 2025, versioned image tags moved to docker.io/bitnamilegacy, which receives no further updates, and the free tier shrank to latest tags of a limited set of images for development. The public docker.io/bitnami catalog was removed on 29 September 2025. Maintained, versioned images are now sold as Bitnami Secure Images, part of Broadcom TrueSource since 31 August 2026.
The risk of staying on bitnamilegacy
Legacy images still pull, so every deployment keeps working. That is the problem. Each container image in the archive is frozen at the day it moved: no patch for the application, no patch for the base image, no update to any bundled dependency. Every CVE disclosed since then stays open, and container scanners report a growing count at every audit.
A repository that receives no updates is also a supply-chain dependency you cannot influence. If it is removed or rate-limited, pods fail to start with ImagePullBackOff.
Bitnami alternatives compared
Two questions decide the right Bitnami replacement: do you need your existing Bitnami Helm charts to keep working, and do you run versions that are past upstream end of life?
| Alternative | Keeps Bitnami layout | End-of-life versions | Cost | Best for |
|---|---|---|---|---|
| OSSeva drop-in images | Yes. Same variables, paths and user | Yes, patched past upstream end of life | Subscription per image family | Keeping existing Bitnami charts, and pinned versions nobody else maintains |
| Bitnami Secure Images | Yes | Follows upstream support | Commercial subscription within Broadcom TrueSource; no public list price | Teams already buying from Broadcom |
| Official upstream images | No. Different variables, paths and users | No. Current versions only | Free | Teams rewriting charts or moving to operators anyway |
| Kubernetes operators | No. Replaces the chart entirely | Depends on the images the operator runs | Free, open source | Long-term replacement of Bitnami charts for databases and brokers |
| Docker Hardened Images | No. Docker's own layout | Paid Extended Lifecycle Support: five years past upstream EOL | Free catalog under Apache 2.0; paid Enterprise and ELS tiers | Hardened current images on Docker's platform |
| Chainguard Images | No. Minimal images with their own layout | Commercial tiers | Free images at latest tags; version-pinned images are paid | Minimal, low-CVE images for current versions |
| Stay on bitnamilegacy | Yes | No updates of any kind | Free | Nothing beyond a short stopgap |
Replace a specific Bitnami image
Each guide maps the Bitnami environment variables and data paths to the official image, lists what breaks, and shows how to repoint the Bitnami chart.
Bitnami PostgreSQL alternative
Drop-in availablebitnamilegacy/postgresql · 16.9 million pulls
Bitnami Redis alternative
Drop-in availablebitnamilegacy/redis · 15.1 million pulls
Bitnami Apache Kafka alternative
Drop-in availablebitnamilegacy/kafka · 14.3 million pulls
Bitnami Apache ZooKeeper alternative
Drop-in availablebitnamilegacy/zookeeper · 6.9 million pulls
Bitnami RabbitMQ alternative
Drop-in availablebitnamilegacy/rabbitmq · 6.1 million pulls
Bitnami MongoDB alternative
Drop-in availablebitnamilegacy/mongodb · 4.1 million pulls
Bitnami Elasticsearch alternative
Drop-in availablebitnamilegacy/elasticsearch · 1.4 million pulls
Bitnami MySQL alternative
Guidebitnamilegacy/mysql · 3.9 million pulls
Bitnami MariaDB alternative
Guidebitnamilegacy/mariadb · 3.5 million pulls
Bitnami Keycloak alternative
Guidebitnamilegacy/keycloak · 2.4 million pulls
How to migrate from Bitnami
- Inventory every bitnami and bitnamilegacy image reference in running workloads, values files and CI, including init containers and helper images.
- Record the version each workload pins, and flag any that are past upstream end of life.
- Choose a replacement per image: a Bitnami-compatible image to keep the chart, or the upstream image with an operator.
- Mirror the new images into your own registry and scan them.
- Roll out stateless workloads first, then stateful ones one replica at a time, checking data paths and file ownership.
- Remove every remaining legacy reference so nothing falls back to the archive.
How long it takes depends on the route. Repointing charts to Bitnami-compatible images is usually days of work per cluster. Rewriting charts for upstream images or adopting operators is a project measured in weeks per application, mostly spent on stateful workloads.
How to choose
- If you can rewrite charts and only run current versions, move to official images with an operator.
- If you need charts to keep working with a registry change, pick an image that keeps Bitnami's layout.
- If any workload pins a version past upstream end of life, only a vendor that patches old versions keeps it covered.
- Whatever you choose, mirror the images into your own registry so production never again depends on one public catalog.
Pull counts are Docker Hub bitnamilegacy figures on 28 September 2026. Dates are from the Bitnami containers repository announcement; Docker Hardened Images terms from Docker's December 2025 announcement.
Frequently asked questions
What is the best Bitnami alternative?
It depends on what you run. For current versions and teams willing to change charts, official images with a Kubernetes operator are the cleanest long-term choice. To keep existing Bitnami charts working, choose images that keep Bitnami's layout: Bitnami Secure Images for current versions, or OSSeva drop-in images, which also cover versions past upstream end of life.
Are Bitnami images still free?
Only in a limited way. Since 28 August 2025, versioned Bitnami images live in the bitnamilegacy repository, which gets no updates, and the free tier offers latest tags of a limited set of images for development. Maintained, versioned images are sold as Bitnami Secure Images.
How much do Bitnami Secure Images cost?
Broadcom does not publish list pricing. Bitnami Secure Images is sold as a commercial subscription and, since 31 August 2026, as part of the Broadcom TrueSource portfolio.
What replaced Bitnami Helm charts?
The charts are still published, but their default images are no longer free and versioned. Teams either point the charts at maintained Bitnami-compatible images, or replace the charts with operators such as CloudNativePG, Strimzi and the RabbitMQ Cluster Operator.
Is bitnamilegacy safe to use in production?
No. Bitnami describes the legacy repository as receiving no further updates or support. The images still pull, so deployments keep working while vulnerabilities accumulate.
Is Bitnami owned by Broadcom?
Yes. Bitnami was acquired by VMware, and VMware by Broadcom, which made the catalog change in 2025.
Can I migrate from Bitnami without changing my Helm charts?
Yes, if the replacement image keeps Bitnami's environment variables, data paths and user. Change image.registry and image.repository in your values file, and allow non-Bitnami images in recent charts with global.security.allowInsecureImages.
Send us your image list.
We map every Bitnami image you run to a replacement and tell you which ones we can cover drop-in.