Alternatives to Bitnami logo

Alternatives to Bitnami

Docker, Heroku, DigitalOcean, XAMPP, and MAMP are the most popular alternatives and competitors to Bitnami.
114
152
+ 1
6

What is Bitnami and what are its top alternatives?

Our library provides trusted virtual machines for every major development stack and open source server application, ready to run in your infrastructure.
Bitnami is a tool in the Server Software category of a tech stack.

Top Alternatives to Bitnami

  • Docker

    Docker

    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere ...

  • Heroku

    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

  • DigitalOcean

    DigitalOcean

    We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel. ...

  • XAMPP

    XAMPP

    It consists mainly of the Apache HTTP Server, MariaDB database, and interpreters for scripts written in the PHP and Perl programming languages. ...

  • MAMP

    MAMP

    It can be installed under macOS and Windows with just a few clicks. It provides them with all the tools they need to run WordPress on their desktop PC for testing or development purposes, for example. It doesn't matter if you prefer Apache or Nginx or if you want to work with PHP, Python, Perl or Ruby. ...

  • Helm

    Helm

    Helm is the best way to find, share, and use software built for Kubernetes.

  • Local by Flywheel

    Local by Flywheel

    It is a free local development environment designed to simplify the workflow of WordPress developers and designers. It makes creating a local WordPress site a light breeze. Any site created with it, will automatically have a self-signed certificate created. ...

  • WordPress

    WordPress

    The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family. ...

Bitnami alternatives & related posts

Docker logo

Docker

103.1K
81.8K
3.8K
Enterprise Container Platform for High-Velocity Innovation.
103.1K
81.8K
+ 1
3.8K
PROS OF DOCKER
  • 821
    Rapid integration and build up
  • 688
    Isolation
  • 517
    Open source
  • 504
    Testa­bil­i­ty and re­pro­ducibil­i­ty
  • 459
    Lightweight
  • 217
    Standardization
  • 182
    Scalable
  • 105
    Upgrading / down­grad­ing / ap­pli­ca­tion versions
  • 86
    Security
  • 84
    Private paas environments
  • 33
    Portability
  • 25
    Limit resource usage
  • 15
    I love the way docker has changed virtualization
  • 15
    Game changer
  • 12
    Fast
  • 11
    Concurrency
  • 7
    Docker's Compose tools
  • 4
    Fast and Portable
  • 4
    Easy setup
  • 4
    Because its fun
  • 3
    Makes shipping to production very simple
  • 2
    It's dope
  • 1
    Highly useful
  • 1
    MacOS support FAKE
  • 1
    Its cool
  • 1
    Docker hub for the FTW
  • 1
    Very easy to setup integrate and build
  • 1
    Package the environment with the application
  • 1
    Does a nice job hogging memory
  • 1
    Open source and highly configurable
  • 1
    Simplicity, isolation, resource effective
CONS OF DOCKER
  • 7
    New versions == broken features
  • 4
    Unreliable networking
  • 4
    Documentation not always in sync
  • 3
    Moves quickly
  • 1
    Not Secure

related Docker posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.8M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Tymoteusz Paul
Devops guy at X20X Development LTD · | 22 upvotes · 4.4M views

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Heroku logo

Heroku

18.5K
14.2K
3.2K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
18.5K
14.2K
+ 1
3.2K
PROS OF HEROKU
  • 703
    Easy deployment
  • 459
    Free for side projects
  • 374
    Huge time-saver
  • 348
    Simple scaling
  • 261
    Low devops skills required
  • 190
    Easy setup
  • 174
    Add-ons for almost everything
  • 154
    Beginner friendly
  • 150
    Better for startups
  • 133
    Low learning curve
  • 48
    Postgres hosting
  • 41
    Easy to add collaborators
  • 30
    Faster development
  • 24
    Awesome documentation
  • 19
    Focus on product, not deployment
  • 19
    Simple rollback
  • 15
    Natural companion for rails development
  • 15
    Easy integration
  • 12
    Great customer support
  • 8
    GitHub integration
  • 6
    No-ops
  • 6
    Painless & well documented
  • 4
    Free
  • 3
    Great UI
  • 3
    I love that they make it free to launch a side project
  • 3
    Just works
  • 2
    PostgreSQL forking and following
  • 2
    MySQL extension
CONS OF HEROKU
  • 23
    Super expensive
  • 6
    No usable MySQL option
  • 6
    Not a whole lot of flexibility
  • 5
    Storage
  • 4
    Low performance on free tier

related Heroku posts

Russel Werner
Lead Engineer at StackShare · | 29 upvotes · 1.4M views

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.8M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
DigitalOcean logo

DigitalOcean

13.3K
9.3K
2.6K
Deploy an SSD cloud server in less than 55 seconds with a dedicated IP and root access.
13.3K
9.3K
+ 1
2.6K
PROS OF DIGITALOCEAN
  • 559
    Great value for money
  • 363
    Simple dashboard
  • 357
    Good pricing
  • 300
    Ssds
  • 248
    Nice ui
  • 192
    Easy configuration
  • 155
    Great documentation
  • 137
    Ssh access
  • 134
    Great community
  • 24
    Ubuntu
  • 12
    IPv6 support
  • 12
    Docker
  • 10
    Private networking
  • 7
    99.99% uptime SLA
  • 7
    Great tutorials
  • 7
    Simple API
  • 6
    55 Second Provisioning
  • 5
    One Click Applications
  • 4
    CoreOS
  • 4
    Dokku
  • 4
    Node.js
  • 4
    Debian
  • 4
    LAMP
  • 3
    Ghost
  • 3
    1Gb/sec Servers
  • 3
    Simple Control Panel
  • 3
    LEMP
  • 3
    Word Press
  • 2
    Runs CoreOS
  • 2
    Mean
  • 2
    Speed
  • 2
    GitLab
  • 2
    Django
  • 2
    Quick and no nonsense service
  • 2
    Good Tutorials
  • 2
    Ruby on Rails
  • 2
    Hex Core machines with dedicated ECC Ram and RAID SSD s
  • 1
    Spaces
  • 1
    My go to server provider
  • 1
    Ease and simplicity
  • 1
    Nice
  • 1
    Find it superfitting with my requirements (SSD, ssh.
  • 1
    Easy Setup
  • 1
    Transfer Globally
  • 1
    Drupal
  • 1
    FreeBSD Amp
  • 1
    Amazing Hardware
  • 1
    Magento
  • 1
    KVM Virtualization
  • 1
    ownCloud
  • 1
    RedMine
  • 1
    CentOS
  • 1
    Fedora
  • 1
    FreeBSD
  • 1
    Cheap
  • 1
    Static IP
  • 1
    It's the easiest to get started for small projects
  • 1
    Automatic Backup
  • 1
    Great support
  • 1
    Quick and easy to set up
  • 1
    Servers on demand - literally
  • 1
    Reliability
  • 0
    Variety of services
  • 0
    Managed Kubernetes
CONS OF DIGITALOCEAN
  • 3
    Pricing
  • 2
    No live support chat

related DigitalOcean posts

Hi, I'm a beginner at using MySQL, I currently deployed my crud app on Heroku using the ClearDB add-on. I didn't see that coming, but the increased value of the primary key instead of being 1 is set to 10, and I cannot find a way to change it. Now I`m considering switching and deploying the full app and MySql to DigitalOcean any advice on that? Will I get the same issue? Thanks in advance!

See more

I am going to build a backend which will serve my React site. It will need to interact with a PostgreSQL database where it will store and read users and create and use JSON Web Token for authenticating HTTP requests. I know EF core has good migration tooling, can Go provide the same or better? I am a one man team and I'll be hosting this either on Heroku or DigitalOcean.

See more
XAMPP logo

XAMPP

88
173
3
A free and open-source cross-platform web server solution stack package
88
173
+ 1
3
PROS OF XAMPP
  • 3
    Easy set up and installation of files
CONS OF XAMPP
    Be the first to leave a con

    related XAMPP posts

    Helfried Plenk
    Senior Partner at IBS IT-DL GmbH · | 1 upvote · 53.3K views
    Shared insights
    on
    MAMP
    XAMPP
    Joomla!

    installing a local Joomla! 3.9 website for testing - I already downloaded an installed XAMPP - when now reading some other docs I found mentioned MAMP ... have I to change?

    See more
    MAMP logo

    MAMP

    43
    88
    1
    A free, local server environment
    43
    88
    + 1
    1
    PROS OF MAMP
    • 1
      Great Support of Native Languages
    CONS OF MAMP
      Be the first to leave a con

      related MAMP posts

      Helfried Plenk
      Senior Partner at IBS IT-DL GmbH · | 1 upvote · 53.3K views
      Shared insights
      on
      MAMP
      XAMPP
      Joomla!

      installing a local Joomla! 3.9 website for testing - I already downloaded an installed XAMPP - when now reading some other docs I found mentioned MAMP ... have I to change?

      See more
      Helm logo

      Helm

      878
      594
      10
      The Kubernetes Package Manager
      878
      594
      + 1
      10
      PROS OF HELM
      • 4
        Infrastructure as code
      • 3
        Open source
      • 2
        Easy setup
      • 1
        Testa­bil­i­ty and re­pro­ducibil­i­ty
      CONS OF HELM
        Be the first to leave a con

        related Helm posts

        Emanuel Evans
        Senior Architect at Rainforest QA · | 15 upvotes · 606.5K views

        We recently moved our main applications from Heroku to Kubernetes . The 3 main driving factors behind the switch were scalability (database size limits), security (the inability to set up PostgreSQL instances in private networks), and costs (GCP is cheaper for raw computing resources).

        We prefer using managed services, so we are using Google Kubernetes Engine with Google Cloud SQL for PostgreSQL for our PostgreSQL databases and Google Cloud Memorystore for Redis . For our CI/CD pipeline, we are using CircleCI and Google Cloud Build to deploy applications managed with Helm . The new infrastructure is managed with Terraform .

        Read the blog post to go more in depth.

        See more
        Robert Zuber

        Our backend consists of two major pools of machines. One pool hosts the systems that run our site, manage jobs, and send notifications. These services are deployed within Docker containers orchestrated in Kubernetes. Due to Kubernetes’ ecosystem and toolchain, it was an obvious choice for our fairly statically-defined processes: the rate of change of job types or how many we may need in our internal stack is relatively low.

        The other pool of machines is for running our users’ jobs. Because we cannot dynamically predict demand, what types of jobs our users need to have run, nor the resources required for each of those jobs, we found that Nomad excelled over Kubernetes in this area.

        We’re also using Helm to make it easier to deploy new services into Kubernetes. We create a chart (i.e. package) for each service. This lets us easily roll back new software and gives us an audit trail of what was installed or upgraded.

        See more
        Local by Flywheel logo

        Local by Flywheel

        28
        62
        3
        A way to develop WordPress locally
        28
        62
        + 1
        3
        PROS OF LOCAL BY FLYWHEEL
        • 1
          Optimized for Wordpress development
        • 1
          Superior user interface
        • 1
          Faster setup
        CONS OF LOCAL BY FLYWHEEL
          Be the first to leave a con

          related Local by Flywheel posts

          WordPress logo

          WordPress

          79.2K
          24.5K
          2K
          A semantic personal publishing platform with a focus on aesthetics, web standards, and usability.
          79.2K
          24.5K
          + 1
          2K
          PROS OF WORDPRESS
          • 408
            Customizable
          • 359
            Easy to manage
          • 349
            Plugins & themes
          • 258
            Non-tech colleagues can update website content
          • 245
            Really powerful
          • 143
            Rapid website development
          • 76
            Best documentation
          • 50
            Codex
          • 43
            Product feature set
          • 34
            Custom/internal social network
          • 13
            Open source
          • 7
            Great for all types of websites
          • 5
            Huge install and user base
          • 4
            Best
          • 4
            It's simple and easy to use by any novice
          • 4
            Most websites make use of it
          • 4
            Open Source Community
          • 4
            Perfect example of user collaboration
          • 4
            I like it like I like a kick in the groin
          • 3
            Community
          • 3
            API-based CMS
          • 2
            Easy To use
          • 1
            <a href="https://secure.wphackedhel">Easy Beginner</a>
          CONS OF WORDPRESS
          • 11
            Hard to keep up-to-date if you customize things
          • 10
            Plugins are of mixed quality
          • 8
            Not best backend UI
          • 1
            Complex Organization
          • 1
            Great Security

          related WordPress posts

          Dale Ross
          Independent Contractor at Self Employed · | 22 upvotes · 915.1K views

          I've heard that I have the ability to write well, at times. When it flows, it flows. I decided to start blogging in 2013 on Blogger. I started a company and joined BizPark with the Microsoft Azure allotment. I created a WordPress blog and did a migration at some point. A lot happened in the time after that migration but I stopped coding and changed cities during tumultuous times that taught me many lessons concerning mental health and productivity. I eventually graduated from BizSpark and outgrew the credit allotment. That killed the WordPress blog.

          I blogged about writing again on the existing Blogger blog but it didn't feel right. I looked at a few options where I wouldn't have to worry about hosting cost indefinitely and Jekyll stood out with GitHub Pages. The Importer was fairly straightforward for the existing blog posts.

          Todo * Set up redirects for all posts on blogger. The URI format is different so a complete redirect wouldn't work. Although, there may be something in Jekyll that could manage the redirects. I did notice the old URLs were stored in the front matter. I'm working on a command-line Ruby gem for the current plan. * I did find some of the lost WordPress posts on archive.org that I downloaded with the waybackmachinedownloader. I think I might write an importer for that. * I still have a few Disqus comment threads to map

          See more
          Siddhant Sharma
          Tech Connoisseur at Channelize.io · | 12 upvotes · 748.6K views

          WordPress Magento PHP Java Swift JavaScript

          Back in the days, we started looking for a date on different matrimonial websites as there were no Dating Applications. We used to create different profiles. It all changed in 2012 when Tinder, an Online Dating application came into India Market.

          Tinder allowed us to communicate with our potential soul mates. That too without paying any extra money. I too got 4-6 matches in 6 years. It changed the life of many Millennials. Tinder created a revolution of its own. P.S. - I still don't have a date :(

          Posting my first article. Please have a look and do give feedback.

          Communication InAppChat Dating Matrimonial #messaging

          See more