Bitnami alternatives

Bitnami alternatives for pinned and end-of-life images

The best Bitnami alternative for a pinned or end-of-life image is one that keeps your Helm charts working and patches the exact version you run. OSSeva ships signed, patched, Bitnami-compatible images for PostgreSQL, Redis, Kafka, ZooKeeper, RabbitMQ, MongoDB and Elasticsearch, including versions upstream no longer fixes. If you run current versions and will rewrite your charts anyway, the official image with a Kubernetes operator is the cheaper long-term route. Enter your work email and the images you run, and an engineer replies within 1 business day.

Keeps your Bitnami Helm charts working
OSSeva drop-in images, or Bitnami Secure Images
Patches a version past upstream end of life
OSSeva, for the exact version you pin; Docker Hardened Images with Extended Lifecycle Support
Free, for current versions only
The official upstream image, usually with a Kubernetes operator
Stay on bitnamilegacy
No updates of any kind. A short stopgap at most

Dates, tags and vendor facts checked 20 October 2026 against Bitnami's GitHub announcement, bitnami.com, Docker Hub, Broadcom's announcements and each vendor's own pages.

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

What changed with Bitnami images

Bitnami packaged open source applications as container images and Helm charts, and its free images on Docker Hub were the default way to run PostgreSQL, Redis, Kafka and RabbitMQ on Kubernetes. VMware acquired Bitnami, and Broadcom acquired VMware. The versioned images now sit in bitnamilegacy, which gets no updates, and maintained versions are sold as Bitnami Secure Images. The full timeline and what broke is on its own page.

Bitnami catalogue changes, 2025 to 2026
DateWhat happened
16 July 2025Bitnami posts the catalogue change on its containers repository (issue 83267).
28 August 2025The public catalogue switches to a limited free subset at latest tags. Versioned images are archived in docker.io/bitnamilegacy, which gets no updates or support. The first of three scheduled brownouts runs.
29 September 2025The public docker.io/bitnami catalogue is deleted, after the brownouts and a postponement. Charts remain at docker.io/bitnamicharts but receive no updates, except for the free-tier images they bundle.
10 June 2026Broadcom removes Bitnami containers, Helm charts and AMIs from AWS Marketplace, Lightsail and ECR (announced 20 May 2026).
31 August 2026Broadcom announces TrueSource at VMware Explore 2026; the Bitnami Secure Images catalogue is part of TrueSource Trusted Artifacts.
20 October 2026Docker Hub labels every bitnamilegacy repository "Legacy Bitnami images (no longer updated)". The Bitnami charts repository still defaults the PostgreSQL chart to bitnami/postgresql:17.6.0-debian-12-r4 and the Redis chart to bitnami/redis:8.2.1-debian-12-r0. Docker Hub returns 404 for both tags in docker.io/bitnami and 200 in bitnamilegacy.

Sources: Bitnami containers announcement, Docker Hub bitnamilegacy, Bitnami charts repository, Broadcom notice on AWS availability, Broadcom TrueSource announcement. Checked 20 October 2026.

Bitnami legacy images: the risk of staying put

Legacy images still pull, so every deployment keeps working. That is the problem. Each image in the archive is frozen at the day it was last built: no patch for the application, none for the base image, none for any bundled dependency. The ten repositories in the tables below alone have more than 80 million pulls, and the newest tag in each was pushed in August 2025 at the latest.

Older lines stopped earlier. The newest PostgreSQL 14 tag was pushed on 22 July 2025 and the newest MongoDB 6.0 tag on 21 July 2025, so teams that pinned those lines have been unpatched for longer than the archive has existed. 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.

Options compared

Two questions decide the right alternative to Bitnami: do your existing Helm charts need to keep working, and do you run versions that are past upstream end of life?

AlternativeKeeps Bitnami layoutEnd-of-life versionsHow it is pricedBest for
OSSeva drop-in imagesYes. Same variables, /bitnami paths and non-root userYes. Patched builds of the exact version you pin, for seven image familiesSubscription for the image families you run, priced by quoteKeeping existing Bitnami charts, and pinned versions nobody else maintains
Bitnami Secure ImagesYes. Broadcom describes them as drop-in replacements for the former free imagesNot published. Ask Broadcom in writing which end-of-life versions it patchesCommercial subscription within Broadcom TrueSource; no public list priceTeams already buying from Broadcom, on supported versions
Official upstream imagesNo. Different variables, paths and usersNo. Current versions onlyFreeTeams rewriting charts or moving to operators anyway
Kubernetes operatorsNo. Replaces the chart entirelyDepends on the images the operator runsFree, open sourceLong-term replacement of Bitnami charts for databases and brokers
Docker Hardened ImagesNo. Docker's own layout, Alpine or Debian basedExtended Lifecycle Support, an Enterprise add-on: up to five years past upstream end of lifeFree community catalogue under Apache 2.0; Enterprise and Extended Lifecycle Support by quoteHardened images on Docker's platform, with or without extended lifecycle cover
Chainguard ImagesNo. Minimal images with their own layoutGrace period of up to six months after upstream end of life; the end-of-life application itself is not patchedFree images at :latest only; versioned tags need a paid planMinimal, low-CVE images for current versions
Stay on bitnamilegacyYesNo updates of any kindFreeNothing beyond a short stopgap

Bitnami competitors side by side: Secure Images, Chainguard, Docker Hardened Images and OSSeva

The four routes teams shortlist most often. OSSeva publishes this page and is one of the four; every other fact comes from that vendor's own site, checked 20 October 2026.

Bitnami Secure Images, Chainguard, Docker Hardened Images and OSSeva compared
Bitnami Secure ImagesChainguardDocker Hardened ImagesOSSeva
Catalogue350+ container images and 140+ Helm chartsMinimal images across many languages and applicationsHardened images catalogue on Docker Hub, free under Apache 2.0Seven data and messaging families: PostgreSQL, Redis, Kafka, ZooKeeper, RabbitMQ, MongoDB, Elasticsearch
Keeps Bitnami charts workingYes. Photon-based images sold as drop-in replacementsNo. Own image layout; separate forked charts for teams leaving BitnamiNo. Docker's own layoutYes. Same variables, /bitnami paths and non-root user
Version past upstream end of lifeNot published. Ask Broadcom which end-of-life versions it keeps patchingUp to six months of grace; it updates the other packages, does not backport fixes to the end-of-life package, and makes no exceptions to the limitExtended Lifecycle Support, an Enterprise add-on, up to five years past upstream end of lifePatched builds of the exact version you pin, for the seven families above
Evidence with each imageSBOM, VEX documents, CVE scan results and SLSA 3 attestation signatures, per Bitnami's siteSee the vendor's documentationSee the vendor's documentationSigned images with an SBOM and a VEX statement for each build
Pricing modelSubscription; not published, contact salesFree at :latest; versioned images are paidCommunity free; Enterprise by quoteSubscription for the image families you run; contact us for a quote
Free tierA portion of the catalogue for non-production use, latest tag onlyFree images at :latestCommunity catalogue, no usage restrictionsNone

Sources: bitnami.com, Chainguard EOL grace period, docker.com/products/hardened-images. Full detail on OSSeva vs Bitnami Secure Images and OSSeva vs Chainguard.

Bitnami pricing: how each option is priced

Broadcom publishes no list price for Bitnami Secure Images. Full catalogue access is a subscription you request by contacting Broadcom, and a portion of the catalogue is free for non-production use at the latest tag only. Docker Hardened Images has a free community catalogue, with Enterprise and Extended Lifecycle Support by quote. Chainguard's free images are at :latest; versioned images need a paid plan.

OSSeva prices drop-in images as a subscription for the image families you run, quoted after we see your image list. How OSSeva prices support sets out what moves a quote, and the database support cost calculator compares it with what you pay today.

Bitnami EOL: which alternative fits a pinned or end-of-life version?

The answer depends on how far past upstream support the version you pin has gone.

A pinned version that upstream still supports

Any of the routes works. If you keep Bitnami charts, Bitnami Secure Images or OSSeva keep them untouched; if you will rewrite charts anyway, the official image or a Docker Hardened Image with an operator is the cheaper long-term route.

A version that reached end of life in the last six months

Chainguard's grace period can bridge it, but only the other packages in the image are updated, not the end-of-life application, and the limit has no exceptions. Treat it as a short bridge with an upgrade date.

A version past upstream end of life that you cannot upgrade yet

You need a vendor that patches the application itself. Docker Hardened Images offers Extended Lifecycle Support on Enterprise, up to five years past upstream end of life, in Docker's layout. OSSeva patches the exact version you pin in the Bitnami layout, for PostgreSQL, Redis, Kafka, ZooKeeper, RabbitMQ, MongoDB and Elasticsearch. Bitnami Secure Images does not publish which end-of-life versions it covers, so get that list in writing first.

An image outside those seven families

OSSeva does not ship it as a drop-in image. Use Bitnami Secure Images if you want to keep the charts, or the upstream image with an operator, and check each vendor's list against your exact versions.

Image by image: the last bitnamilegacy tag and what is open on it

For each line below, the last tag Bitnami pushed to bitnamilegacy and the advisories in OSSeva's CVE directory that name that version. The directory is not a full mirror of NVD and this is not a scan of the image, so treat each count as a floor. Tags and push dates were read from Docker Hub on 20 October 2026.

Last bitnamilegacy tag per pinned version line, with advisories that name it
Pinned lineLast bitnamilegacy tagPushedAdvisories naming itHighest CVSSOSSeva drop-in
PostgreSQL 1414.18.0-debian-12-r022 Jul 202598.8Patched PostgreSQL 14 image
PostgreSQL 1313.18.0-debian-12-r222 Jul 202518.8Patched PostgreSQL 13 image
Redis 7.27.2.5-debian-12-r618 Jul 202559.9Patched Redis 7.2 image
Redis 6.26.2.16-debian-12-r318 Jul 202549.9Patched Redis 6.2 image
Kafka 3.93.9.0-debian-12-r1318 Jul 202548.8Patched Kafka 3.x image
Kafka 3.33.3.2-debian-11-r26718 Jul 202588.8Patched Kafka 3.x image
ZooKeeper 3.83.8.4-debian-12-r173 Jul 202557.5Patched ZooKeeper 3.8 image
RabbitMQ 3.133.13.7-debian-12-r521 Jul 2025159.2Patched RabbitMQ 3.13 image with patched Erlang/OTP
MongoDB 6.06.0.13-debian-11-r2121 Jul 202538.8Patched MongoDB 6.0 image
MongoDB 5.05.0.24-debian-11-r2021 Jul 202538.8Patched MongoDB 5.0 image
MongoDB 4.44.4.1521 Jul 202528.8Patched MongoDB 4.4 image
Elasticsearch 7.177.17.26-debian-12-r019 Jul 202547.4Patched Elasticsearch 7.17 image

The PostgreSQL 13 row counts one advisory because the directory marks PostgreSQL 13 and older as not assessed for the 2026 releases. MongoDB, Redis and Kafka rows count only advisories whose affected-version text names the line. Highest CVSS links to the advisory.

Bitnami replacement for each image

Newest tag in each of ten popular repositories, and where to go for the variable-by-variable guide. Together they account for more than 80 million pulls.

Newest bitnamilegacy tag and OSSeva coverage for ten Bitnami images
ImageNewest tag in bitnamilegacyPushedPullsOSSeva drop-in
Bitnami PostgreSQL alternative17.6.0-debian-12-r428 Aug 202518.5 millionPostgreSQL 11 to 14, including versions past community end of life
Bitnami Redis alternative8.2.1-debian-12-r022 Aug 202516.6 millionRedis 6.x and 7.2, the BSD-licensed lines, plus Valkey
Bitnami Apache Kafka alternative4.0.0-debian-12-r1022 Aug 202515.5 millionKafka 2.8 to 3.9, including ZooKeeper-mode clusters
Bitnami Apache ZooKeeper alternative3.9.3-debian-12-r2220 Aug 20257.2 millionZooKeeper 3.6 to 3.8 (3.5 custom)
Bitnami RabbitMQ alternative4.1.3-debian-12-r113 Aug 20256.9 millionRabbitMQ 3.8 to 3.13 with a patched Erlang/OTP runtime
Bitnami MongoDB alternative8.0.13-debian-12-r023 Aug 20254.5 millionMongoDB 4.2 to 6.0, including hardware without AVX
Bitnami Elasticsearch alternative9.1.2-debian-12-r022 Aug 20251.5 millionElasticsearch 7.10.2 and 7.17
Bitnami MySQL alternative9.4.0-debian-12-r113 Aug 20254.2 millionNot shipped. Use the guide and the upstream image or an operator
Bitnami MariaDB alternative12.0.2-debian-12-r023 Aug 20253.8 millionNot shipped. Use the guide and the upstream image or an operator
Bitnami Keycloak alternative26.3.3-debian-12-r020 Aug 20252.6 millionNot shipped. Use the guide and the upstream image or an operator

Bitnami Helm charts alternative: keep the chart or move to an operator

Pinning a chart version does not pin a maintained image. A chart's default values name a docker.io/bitnami tag. On 20 October 2026 the main-branch PostgreSQL chart defaults to bitnami/postgresql:17.6.0-debian-12-r4, and Docker Hub no longer has that tag in docker.io/bitnami. An older chart names an older tag, which is also gone.

To keep the chart, override the image and allow a non-Bitnami registry. The replacement image has to keep Bitnami's variables, paths and user, or the chart's templates will not work with it.

# values-override.yaml
global:
  security:
    allowInsecureImages: true   # recent Bitnami charts reject non-Bitnami images without this
image:
  registry: registry.example.com   # your mirror of the replacement image
  repository: postgresql
  tag: "<the version you pin>"

Charts to operators: the data migration

Replacing a Bitnami chart with an operator is not a chart swap. It is a data migration. Bitnami images keep data under their own paths and run as their own non-root user, and an operator or an official image lays data out differently, so a volume from a Bitnami release does not simply attach to the new workload. Teams typically restore a logical dump or replicate into the new cluster, then cut over.

Bitnami and official data paths, and the usual operator, per image
ImageBitnami data pathOfficial image data pathUsual operator
PostgreSQL/bitnami/postgresql/var/lib/postgresql (PGDATA)CloudNativePG
Apache Kafka/bitnami/kafkalog.dirs as configuredStrimzi
RabbitMQ/bitnami/rabbitmq/mnesia/var/lib/rabbitmqRabbitMQ Cluster Operator
MySQL/bitnami/mysql/data/var/lib/mysqlPercona Operator for MySQL or MySQL Operator for Kubernetes
MariaDB/bitnami/mariadb/data/var/lib/mysqlmariadb-operator
Keycloak/bitnami/keycloakExternal database; no local data volumeKeycloak Operator

What sets the scope of a chart-to-operator move:

  • How many charts and values files name a Bitnami image, including init containers and helper images.
  • How much of the estate is stateful. Stateless workloads change a registry reference; stateful ones move data.
  • Data volume per database or broker, and the downtime window each application can accept.
  • Whether you change the image, the chart and the major version in one step. Doing all three at once removes the ability to tell which change broke what.
  • How many images sit on end-of-life lines, because those have no upstream image to move to.

How to migrate from Bitnami

  1. Inventory every bitnami and bitnamilegacy image reference in running workloads, values files and CI, including init containers and helper images.
  2. Record the version each workload pins, and flag any that are past upstream end of life.
  3. Choose a replacement per image: a Bitnami-compatible image to keep the chart, or the upstream image with an operator.
  4. Mirror the new images into your own registry and scan them.
  5. Roll out stateless workloads first, then stateful ones one replica at a time, checking data paths and file ownership.
  6. Remove every remaining legacy reference so nothing falls back to the archive.

Repointing charts to Bitnami-compatible images changes registry references and values. Rewriting charts for upstream images or adopting operators is a project whose size follows the scope factors above, mostly in the stateful workloads.

What OSSeva's Bitnami-compatible images include

What OSSeva drop-in images include and what they do not
IncludedNot included
Patched images that keep Bitnami's variables, paths and non-root user, for the exact version you pin, including end-of-life versions.Images outside the seven families (MySQL, MariaDB and Keycloak have guides here but no OSSeva image).
Signed images with an SBOM and a VEX statement for each build.A free tier, or a general catalogue of minimal images for current versions.
Patch SLA: Critical fixes within 48 hours, High within 7 days.Chart rewrites or operator migrations, unless scoped with you.
Assure includes 24/7 reactive support; Operate adds managed operations with a 15-minute P1 response. Delivery from a private registry or mirrored into yours.Support for images you did not send us.

Coverage and tiers are on the drop-in images page; the supported versions table lists every line.

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 catalogue.

Pull counts are Docker Hub bitnamilegacy figures read on 20 October 2026. Dates are from the Bitnami containers repository announcement and Broadcom's notices; Docker Hardened Images terms from docker.com/products/hardened-images.

Questions

Frequently asked questions

Book a 15-minute call

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 supported versions, or OSSeva drop-in images, which also cover versions past upstream end of life.

What are the best Bitnami alternatives for pinned Helm chart versions?

A pinned chart version still names a docker.io/bitnami tag, and those tags are gone from that repository. Keep the chart and override image.registry, image.repository and image.tag with a Bitnami-compatible image that is maintained for the version you pin, and set global.security.allowInsecureImages to true, because recent Bitnami charts refuse non-Bitnami images without it. OSSeva drop-in images are built for this; Bitnami Secure Images is the other route that keeps the layout.

Are there patched bitnamilegacy images for PostgreSQL and Redis?

Not from Bitnami: every bitnamilegacy repository is labelled as no longer updated. The newest PostgreSQL tag there is 17.6.0-debian-12-r4, pushed on 28 August 2025, and the newest Redis tag is 8.2.1-debian-12-r0, pushed on 22 August 2025. OSSeva ships patched, signed Bitnami-compatible images for PostgreSQL 11 to 14 and Redis 6.x and 7.2, including versions past community 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 non-production use. Maintained, versioned images are sold as Bitnami Secure Images.

How much do Bitnami Secure Images cost?

Broadcom does not publish a list price. Bitnami Secure Images is sold as a commercial subscription by contacting Broadcom and, since 31 August 2026, as part of the TrueSource portfolio. A portion of the catalogue is free for non-production use at the latest tag only.

What replaced Bitnami Helm charts?

The charts are still published, but they no longer receive updates except for the free-tier images they bundle, and their default image tags point at docker.io/bitnami tags that no longer exist. 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. Docker Hub labels the repositories as legacy images that are no longer updated. The images still pull, so deployments keep working while advisories published after the archive froze stay open.

Is Bitnami owned by Broadcom?

Yes. Bitnami was acquired by VMware, and VMware by Broadcom, which made the catalogue 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.

What does OSSeva include with its Bitnami-compatible images?

Signed images with an SBOM and a VEX statement for each build, patched on a fixed schedule (Critical within 48 hours, High within 7 days), delivered from a private registry or mirrored into yours. Assure support includes 24/7 reactive support; the Operate tier adds managed operations with a 15-minute P1 response.

Get a quote

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.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call