Bitnami is gone. We keep maintaining.
Drop-in AMI replacements for the Bitnami stacks teams relied on most — LAMP, WordPress, MariaDB, nginx, Node.js, SMTP — patched every week, audited daily and with a real person on the other end.
Bitnami turned off the free catalog
For over a decade Bitnami packaged half the internet: AMIs, containers and charts ready to bring up a WordPress, a LAMP or a Memcached in two clicks, with nothing to configure. After the move to Broadcom, that free catalog stopped being maintained: the images were pushed off to a «legacy» repository that no longer gets updates, and the AMIs were withdrawn from the AWS Marketplace.
The problem does not arrive the day they stop publishing. It arrives the next day: your instance still boots exactly as it did yesterday, but nobody patches the base system or the software inside it any more, and every CVE from then on stays open in production. There is no new image to relaunch, and nobody to open a ticket with.
Your Bitnami stack, already covered
Same architecture, same paths, same zero learning curve. Only maintained.
Don't see your stack on the map? Write to us: we prioritize new replacements based on what migrating customers ask for most.
The same as before, better maintained
Weekly patches
CVEs and security updates applied to the base image every week, without you lifting a finger.
Daily audit
Automated vulnerability scanning and CIS hardening verified daily.
Human support
Tickets that reach the team that builds the images. No bots, no tier-one escalations.
Three steps, without rewriting anything
Launch the replacement
Deploy the equivalent AMI from AWS Marketplace in the same region and instance type.
Migrate your data
Restore your dump or mount the data volume: the paths and services match Bitnami.
Move the IP
Reassign the EIP to the new instance. Your clients don't notice the change.
Stop maintaining orphaned images
Migrate to an AMI someone watches for you. Start with the replacement catalog.