Alternatives to CloudBolt logo

Alternatives to CloudBolt

Scalr, Morpheus, Terraform, RightScale, and Ansible are the most popular alternatives and competitors to CloudBolt.
6
15
+ 1
0

What is CloudBolt and what are its top alternatives?

Deploys in minutes. Simple to use. Easy to extend. Centralize workload automation and orchestration, achieve unparalleled hybrid cloud visibility and cost-savings, and deliver self-service IT for your developers.
CloudBolt is a tool in the Multi Cloud Management category of a tech stack.

Top Alternatives to CloudBolt

  • Scalr
    Scalr

    Scalr is a remote state & operations backend for Terraform with access controls, policy as code, and many quality of life features. ...

  • Morpheus
    Morpheus

    Morpheus is a cloud application management and orchestration platform that works on any cloud or infrastructure, from AWS to bare metal. Enjoy complete cloud freedom with Morpheus. ...

  • Terraform
    Terraform

    With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel. ...

  • RightScale
    RightScale

    Automation is the core of RightScale, freeing you to run efficient, scalable, and highly-available applications. Our multi-cloud integration enables you to choose your own clouds, providing freedom to work with any vendor in a rapidly changing market. And rest assured knowing that you have visibility and control over all of your resources in one place. To take advantage of best practices, we encourage you to tap into cloud expertise provided by our service, support, and partner networks when building and managing your infrastructure. ...

  • Ansible
    Ansible

    Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use. ...

  • MongoDB Cloud Manager
    MongoDB Cloud Manager

    It is a hosted platform for managing MongoDB on the infrastructure of your choice. It saves you time, money, and helps you protect your customer experience by eliminating the guesswork from running MongoDB. ...

  • OpenNebula
    OpenNebula

    It provides a simple but feature-rich and flexible solution for the comprehensive management of virtualized data centers to enable on-premise enterprise clouds in existing infrastructures. It can be primarily used as a virtualization tool to manage your virtual infrastructure in the data-center or cluster, which is usually referred as Private Cloud. It supports Hybrid Cloud to combine local infrastructure with public cloud-based infrastructure, enabling highly scalable hosting environments. ...

  • Crossplane
    Crossplane

    Crossplane introduces workload and resource abstractions on-top of existing managed services that enables a high degree of workload portability across cloud providers. A single crossplane enables the provisioning and full-lifecycle management of services and infrastructure across a wide range of providers, offerings, vendors, regions, and clusters. ...

CloudBolt alternatives & related posts

Scalr logo

Scalr

37
33
26
Scalr is a remote state & operations backend for Terraform with access controls and policy as code
37
33
+ 1
26
PROS OF SCALR
  • 5
    Image Builder
  • 3
    Open Source
  • 3
    Auto Scaling
  • 2
    Orchestration
  • 2
    Multi-Cloud Support
  • 2
    Cost Analytics
  • 2
    Chef Integration
  • 2
    Hybrid Cloud Management
  • 2
    User Friendly
  • 1
    Terraform CLI Integration
  • 1
    Open Policy Agent
  • 1
    Cost
CONS OF SCALR
    Be the first to leave a con

    related Scalr posts

    Morpheus logo

    Morpheus

    30
    60
    18
    Orchestrate, Automate, and Manage Across Any Cloud
    30
    60
    + 1
    18
    PROS OF MORPHEUS
    • 2
      Easy to deploy and use
    • 1
      Hybrid Cloud Management
    • 1
      Life cycle management
    • 1
      App provisioning
    • 1
      UI, API and CLI
    • 1
      Governance
    • 1
      SDN - ACI, NSX, Neutron
    • 1
      Config Management-Chef,Puppet,Salt,Ansible,AnsibleTower
    • 1
      Reporting
    • 1
      Analytics
    • 1
      Scheduling
    • 1
      Tagging, Env variables, cypher
    • 1
      Automation - Tasks and Workflows
    • 1
      Image builder
    • 1
      Infrastrcuture as Code
    • 1
      Platform as a Service
    • 1
      Infrastructure as Code, Platform as a Service
    CONS OF MORPHEUS
      Be the first to leave a con

      related Morpheus posts

      Terraform logo

      Terraform

      19.2K
      12K
      338
      Describe your complete infrastructure as code and build resources across providers
      19.2K
      12K
      + 1
      338
      PROS OF TERRAFORM
      • 119
        Infrastructure as code
      • 73
        Declarative syntax
      • 44
        Planning
      • 28
        Simple
      • 24
        Parallelism
      • 8
        Cloud agnostic
      • 8
        Well-documented
      • 6
        Immutable infrastructure
      • 6
        It's like coding your infrastructure in simple English
      • 5
        Platform agnostic
      • 4
        Portability
      • 4
        Extendable
      • 4
        Automation
      • 4
        Automates infrastructure deployments
      • 2
        Scales to hundreds of hosts
      • 2
        Lightweight
      CONS OF TERRAFORM
      • 1
        Doesn't have full support to GKE

      related Terraform posts

      Emanuel Evans
      Senior Architect at Rainforest QA · | 20 upvotes · 1.1M 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
      Praveen Mooli
      Engineering Manager at Taylor and Francis · | 18 upvotes · 2.7M views

      We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

      To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

      To build #Webapps we decided to use Angular 2 with RxJS

      #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

      See more
      RightScale logo

      RightScale

      18
      27
      0
      Manage all of your cloud infrastructure with a single, integrated solution.
      18
      27
      + 1
      0
      PROS OF RIGHTSCALE
        Be the first to leave a pro
        CONS OF RIGHTSCALE
          Be the first to leave a con

          related RightScale posts

          Ansible logo

          Ansible

          17.2K
          13.9K
          1.3K
          Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine
          17.2K
          13.9K
          + 1
          1.3K
          PROS OF ANSIBLE
          • 283
            Agentless
          • 209
            Great configuration
          • 198
            Simple
          • 176
            Powerful
          • 154
            Easy to learn
          • 68
            Flexible
          • 55
            Doesn't get in the way of getting s--- done
          • 35
            Makes sense
          • 30
            Super efficient and flexible
          • 27
            Powerful
          • 11
            Dynamic Inventory
          • 9
            Backed by Red Hat
          • 7
            Works with AWS
          • 6
            Easy to maintain
          • 6
            Cloud Oriented
          • 4
            Vagrant provisioner
          • 4
            Because SSH
          • 4
            Multi language
          • 4
            Easy
          • 4
            Simple
          • 4
            Procedural or declarative, or both
          • 4
            Simple and powerful
          • 3
            Consistency
          • 2
            Masterless
          • 2
            Well-documented
          • 2
            Fast as hell
          • 2
            Merge hash to get final configuration similar to hiera
          • 2
            Debugging is simple
          • 1
            Manage any OS
          • 1
            Work on windows, but difficult to manage
          • 1
            Certified Content
          CONS OF ANSIBLE
          • 8
            Dangerous
          • 5
            Hard to install
          • 3
            Doesn't Run on Windows
          • 3
            Bloated
          • 3
            Backward compatibility
          • 2
            No immutable infrastructure

          related Ansible posts

          Tymoteusz Paul
          Devops guy at X20X Development LTD · | 23 upvotes · 5.6M 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
          Sebastian Gębski

          Heroku was a decent choice to start a business, but at some point our platform was too big, too complex & too heterogenic, so Heroku started to be a constraint, not a benefit. First, we've started containerizing our apps with Docker to eliminate "works in my machine" syndrome & uniformize the environment setup. The first orchestration was composed with Docker Compose , but at some point it made sense to move it to Kubernetes. Fortunately, we've made a very good technical decision when starting our work with containers - all the container configuration & provisions HAD (since the beginning) to be done in code (Infrastructure as Code) - we've used Terraform & Ansible for that (correspondingly). This general trend of containerisation was accompanied by another, parallel & equally big project: migrating environments from Heroku to AWS: using Amazon EC2 , Amazon EKS, Amazon S3 & Amazon RDS.

          See more
          MongoDB Cloud Manager logo

          MongoDB Cloud Manager

          60
          81
          0
          A hosted platform for managing MongoDB
          60
          81
          + 1
          0
          PROS OF MONGODB CLOUD MANAGER
            Be the first to leave a pro
            CONS OF MONGODB CLOUD MANAGER
              Be the first to leave a con

              related MongoDB Cloud Manager posts

              OpenNebula logo

              OpenNebula

              29
              98
              0
              A cloud computing platform for managing heterogeneous distributed data center infrastructures
              29
              98
              + 1
              0
              PROS OF OPENNEBULA
                Be the first to leave a pro
                CONS OF OPENNEBULA
                  Be the first to leave a con

                  related OpenNebula posts

                  Crossplane logo

                  Crossplane

                  27
                  48
                  0
                  Open Source Multicloud Control Plane
                  27
                  48
                  + 1
                  0
                  PROS OF CROSSPLANE
                    Be the first to leave a pro
                    CONS OF CROSSPLANE
                      Be the first to leave a con

                      related Crossplane posts