Alternatives to CloudStick logo

Alternatives to CloudStick

ServerPilot, Ploi, Runcloud, Terraform, and Ansible are the most popular alternatives and competitors to CloudStick.
1
5
+ 1
0

What is CloudStick and what are its top alternatives?

It is an All-in-one cloud-based control panel designed to manage servers from Digital Ocean, Linode, AWS, Google Cloud, Vultr, or any KVM or Dedicated servers you prefer.
CloudStick is a tool in the Server Configuration and Automation category of a tech stack.

Top Alternatives to CloudStick

  • ServerPilot
    ServerPilot

    It is a SaaS platform for hosting PHP websites on Ubuntu servers. You can think of it as a modern, centralized hosting control panel. Manage all servers and sites through a single control panel or automate using our API. ...

  • Ploi
    Ploi

    Rapidly deploy any site you like - PHP, HTML and many, many more. You can use Github, Gitlab, Bitbucket, 1-click-install WordPress or just SFTP. ...

  • Runcloud
    Runcloud

    SaaS based PHP cloud server control panel. Support Digital Ocean, Linode, AWS, Vultr, Azure and other custom VPS. GIT deployment webhook and easiest control panel to manage Laravel, Cake, Symphony or WordPress. ...

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

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

  • Plesk
    Plesk

    Build and manage multiple sites from a single dashboard. You can also run updates, monitor performance and onboard new prospects all from the same place. It is a WebOps platform to run, automate and grow applications, websites and hosting businesses. ...

  • Capistrano
    Capistrano

    Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows. ...

  • Chef
    Chef

    Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others. ...

CloudStick alternatives & related posts

ServerPilot logo

ServerPilot

22
31
0
The best way to run WordPress and PHP sites
22
31
+ 1
0
PROS OF SERVERPILOT
    Be the first to leave a pro
    CONS OF SERVERPILOT
      Be the first to leave a con

      related ServerPilot posts

      Ploi logo

      Ploi

      17
      33
      0
      Server management tool that rapidly deploy any site you like
      17
      33
      + 1
      0
      PROS OF PLOI
        Be the first to leave a pro
        CONS OF PLOI
          Be the first to leave a con

          related Ploi posts

          Runcloud logo

          Runcloud

          24
          63
          0
          PHP web application & server management panel
          24
          63
          + 1
          0
          PROS OF RUNCLOUD
            Be the first to leave a pro
            CONS OF RUNCLOUD
              Be the first to leave a con

              related Runcloud posts

              Terraform logo

              Terraform

              19.1K
              12K
              338
              Describe your complete infrastructure as code and build resources across providers
              19.1K
              12K
              + 1
              338
              PROS OF TERRAFORM
              • 118
                Infrastructure as code
              • 73
                Declarative syntax
              • 44
                Planning
              • 28
                Simple
              • 24
                Parallelism
              • 8
                Well-documented
              • 7
                Cloud agnostic
              • 6
                It's like coding your infrastructure in simple English
              • 5
                Immutable infrastructure
              • 5
                Platform agnostic
              • 4
                Automates infrastructure deployments
              • 4
                Extendable
              • 4
                Automation
              • 4
                Portability
              • 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
              Ansible logo

              Ansible

              17.2K
              13.8K
              1.3K
              Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine
              17.2K
              13.8K
              + 1
              1.3K
              PROS OF ANSIBLE
              • 282
                Agentless
              • 208
                Great configuration
              • 197
                Simple
              • 175
                Powerful
              • 153
                Easy to learn
              • 67
                Flexible
              • 54
                Doesn't get in the way of getting s--- done
              • 34
                Makes sense
              • 30
                Super efficient and flexible
              • 27
                Powerful
              • 11
                Dynamic Inventory
              • 9
                Backed by Red Hat
              • 7
                Works with AWS
              • 6
                Cloud Oriented
              • 6
                Easy to maintain
              • 4
                Because SSH
              • 4
                Multi language
              • 4
                Easy
              • 4
                Simple
              • 4
                Procedural or declarative, or both
              • 4
                Simple and powerful
              • 3
                Consistency
              • 3
                Vagrant provisioner
              • 2
                Debugging is simple
              • 2
                Fast as hell
              • 2
                Well-documented
              • 2
                Merge hash to get final configuration similar to hiera
              • 2
                Masterless
              • 1
                Manage any OS
              • 1
                Certified Content
              • 1
                Work on windows, but difficult to manage
              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
              Plesk logo

              Plesk

              1.6K
              82
              4
              A web hosting platform with a control panel
              1.6K
              82
              + 1
              4
              PROS OF PLESK
              • 1
                Free
              • 1
                Not free
              • 1
                Reliable
              • 1
                Easy to use
              CONS OF PLESK
                Be the first to leave a con

                related Plesk posts

                Shared insights
                on
                MySQLMySQLcPanelcPanelPleskPleskHostGatorHostGator

                Hello,

                I’ve been using a Reseller account to host my client's websites for many years ago.

                I noticed in the last few years low performance and weakness in technical support services, so I intended to move to another provider just like "HostGator," the problem is I'm using currently Plesk "Direct Admin" but the intended new reseller using "cPanel," the question is could I move my reseller without interrupting my clients? "No change from client-side will be performed ex (FTP accounts, control panel credentials, MySQL databases, users, DNS configuration, webmail boxes, and messages)."

                I would love your insights on where I should go. (Experienced)

                Note: I called the HostGator support, and they will make a migration manually; they also assure me that it wouldn't be any interruption, but I'm also not sure.

                See more
                Capistrano logo

                Capistrano

                1.4K
                632
                232
                A remote server automation and deployment tool written in Ruby
                1.4K
                632
                + 1
                232
                PROS OF CAPISTRANO
                • 121
                  Automated deployment with several custom recipes
                • 63
                  Simple
                • 23
                  Ruby
                • 11
                  Release-folders with symlinks
                • 9
                  Multistage deployment
                • 2
                  Cryptic syntax
                • 2
                  Integrated rollback
                • 1
                  Supports aws
                CONS OF CAPISTRANO
                  Be the first to leave a con

                  related Capistrano posts

                  Julien DeFrance
                  Principal Software Engineer at Tophatter · | 16 upvotes · 2.6M views

                  Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

                  I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

                  For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

                  Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

                  Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

                  Future improvements / technology decisions included:

                  Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

                  As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

                  One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

                  See more
                  Kir Shatrov
                  Engineering Lead at Shopify · | 13 upvotes · 143.6K views

                  Shipit, our deployment tool, is at the heart of Continuous Delivery at Shopify. Shipit is an orchestrator that runs and tracks progress of any deploy script that you provide for a project. It supports deploying to Rubygems, Pip, Heroku and Capistrano out of the box. For us, it's mostly kubernetes-deploy or Capistrano for legacy projects.

                  We use a slightly tweaked GitHub flow, with feature development going in branches and the master branch being the source of truth for the state of things in production. When your PR is ready, you add it to the Merge Queue in ShipIt. The idea behind the Merge Queue is to control the rate of code that is being merged to master branch. In the busy hours, we have many developers who want to merge the PRs, but at the same time we don't want to introduce too many changes to the system at the same time. Merge Queue limits deploys to 5-10 commits at a time, which makes it easier to identify issues and roll back in case we notice any unexpected behaviour after the deploy.

                  We use a browser extension to make Merge Queue play nicely with the Merge button on GitHub:

                  Both Shipit and kubernetes-deploy are open source, and we've heard quite a few success stories from companies who have adopted our flow.

                  #BuildTestDeploy #ContainerTools #ApplicationHosting #PlatformAsAService

                  See more
                  Chef logo

                  Chef

                  1.2K
                  1.1K
                  345
                  Build, destroy and rebuild servers on any public or private cloud
                  1.2K
                  1.1K
                  + 1
                  345
                  PROS OF CHEF
                  • 110
                    Dynamic and idempotent server configuration
                  • 76
                    Reusable components
                  • 47
                    Integration testing with Vagrant
                  • 43
                    Repeatable
                  • 30
                    Mock testing with Chefspec
                  • 14
                    Ruby
                  • 8
                    Can package cookbooks to guarantee repeatability
                  • 7
                    Works with AWS
                  • 3
                    Has marketplace where you get readymade cookbooks
                  • 3
                    Matured product with good community support
                  • 2
                    Less declarative more procedural
                  • 2
                    Open source configuration mgmt made easy(ish)
                  CONS OF CHEF
                    Be the first to leave a con

                    related Chef posts

                    In late 2013, the Operations Engineering team at PagerDuty was made up of 4 engineers, and was comprised of generalists, each of whom had one or two areas of depth. Although the Operations Team ran its own on-call, each engineering team at PagerDuty also participated on the pager.

                    The Operations Engineering Team owned 150+ servers spanning multiple cloud providers, and used Chef to automate their infrastructure across the various cloud providers with a mix of completely custom cookbooks and customized community cookbooks.

                    Custom cookbooks were managed by Berkshelf, andach custom cookbook contained its own tests based on ChefSpec 3, coupled with Rspec.

                    Jenkins was used to GitHub for new changes and to handle unit testing of those features.

                    See more
                    Marcel Kornegoor

                    Since #ATComputing is a vendor independent Linux and open source specialist, we do not have a favorite Linux distribution. We mainly use Ubuntu , Centos Debian , Red Hat Enterprise Linux and Fedora during our daily work. These are also the distributions we see most often used in our customers environments.

                    For our #ci/cd training, we use an open source pipeline that is build around Visual Studio Code , Jenkins , VirtualBox , GitHub , Docker Kubernetes and Google Compute Engine.

                    For #ServerConfigurationAndAutomation, we have embraced and contributed to Ansible mainly because it is not only flexible and powerful, but also straightforward and easier to learn than some other (open source) solutions. On the other hand: we are not affraid of Puppet Labs and Chef either.

                    Currently, our most popular #programming #Language course is Python . The reason Python is so popular has to do with it's versatility, but also with its low complexity. This helps sysadmins to write scripts or simple programs to make their job less repetitive and automating things more fun. Python is also widely used to communicate with (REST) API's and for data analysis.

                    See more