Alternatives to Armory logo

Alternatives to Armory

Spinnaker, Godot, AWS CodePipeline, Buddy, and Google Cloud Build are the most popular alternatives and competitors to Armory.
7
24
+ 1
0

What is Armory and what are its top alternatives?

Armory.io makes deployments boring (like ‘waiting for your code to compile’ boring), non-events that happen continuously, and always in the background. We do that by simplifying the installation and configuration of Spinnaker - an open source continuous delivery platform from Netflix.
Armory is a tool in the Continuous Deployment category of a tech stack.

Top Alternatives to Armory

  • Spinnaker

    Spinnaker

    Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers. ...

  • Godot

    Godot

    It is an advanced, feature-packed, multi-platform 2D and 3D open source game engine. It is developed by hundreds of contributors from all around the world. ...

  • AWS CodePipeline

    AWS CodePipeline

    CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define. ...

  • Buddy

    Buddy

    Git platform for web and software developers with Docker-based tools for Continuous Integration and Deployment. ...

  • Google Cloud Build

    Google Cloud Build

    Cloud Build lets you build software quickly across all languages. Get complete control over defining custom workflows for building, testing, and deploying across multiple environments such as VMs, serverless, Kubernetes, or Firebase. ...

  • DeployBot

    DeployBot

    DeployBot makes it simple to deploy your work anywhere. You can compile or process your code in a Docker container on our infrastructure, and we'll copy it to your servers once everything has been successfully built. ...

  • Deployer

    Deployer

    A deployment tool written in PHP with support for popular frameworks out of the box ...

  • Cloud 66

    Cloud 66

    Cloud 66 makes Ops easy for developers. It is a single tool built for developers to build, configure and maintain servers and Docker containers on your own servers. ...

Armory alternatives & related posts

Spinnaker logo

Spinnaker

180
268
9
Multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence
180
268
+ 1
9
PROS OF SPINNAKER
  • 9
    Mature
CONS OF SPINNAKER
  • 2
    No GitOps
  • 1
    Configuration time
  • 1
    Management overhead
  • 1
    Ease of use

related Spinnaker posts

John Kodumal

LaunchDarkly is almost a five year old company, and our methodology for deploying was state of the art... for 2014. We recently undertook a project to modernize the way we #deploy our software, moving from Ansible-based deploy scripts that executed on our local machines, to using Spinnaker (along with Terraform and Packer) as the basis of our deployment system. We've been using Armory's enterprise Spinnaker offering to make this project a reality.

See more
Godot logo

Godot

103
115
19
Free and open source 2D and 3D game engine
103
115
+ 1
19
PROS OF GODOT
  • 6
    Open source
  • 4
    Easy to port
  • 2
    Supports both C++, C# and GDScript
  • 2
    Simple
  • 2
    Cross-Platform
  • 1
    GDScript is Based On Python
  • 1
    Very Popular in Reddit
  • 1
    Avaible on Steam For Free
CONS OF GODOT
  • 1
    Performance in 3D
  • 1
    Somewhat poor 3D performance and lacks automatic LODs

related Godot posts

AWS CodePipeline logo

AWS CodePipeline

375
642
30
Continuous delivery service for fast and reliable application updates
375
642
+ 1
30
PROS OF AWS CODEPIPELINE
  • 13
    Simple to set up
  • 8
    Managed service
  • 4
    GitHub integration
  • 3
    Parallel Execution
  • 2
    Automatic deployment
  • 0
    Manual Steps Available
CONS OF AWS CODEPIPELINE
  • 2
    No project boards
  • 1
    No integration with "Power" 365 tools

related AWS CodePipeline posts

Khauth György
CTO at SalesAutopilot Kft. · | 12 upvotes · 359.7K views

I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

See more
Oliver Burn

We recently added new APIs to Jira to associate information about Builds and Deployments to Jira issues.

The new APIs were developed using a spec-first API approach for speed and sanity. The details of this approach are described in this blog post, and we relied on using Swagger and associated tools like Swagger UI.

A new service was created for managing the data. It provides a REST API for external use, and an internal API based on GraphQL. The service is built using Kotlin for increased developer productivity and happiness, and the Spring-Boot framework. PostgreSQL was chosen for the persistence layer, as we have non-trivial requirements that cannot be easily implemented on top of a key-value store.

The front-end has been built using React and querying the back-end service using an internal GraphQL API. We have plans of providing a public GraphQL API in the future.

New Jira Integrations: Bitbucket CircleCI AWS CodePipeline Octopus Deploy jFrog Azure Pipelines

See more
Buddy logo

Buddy

283
317
607
Build, test and deploy on push in seconds.
283
317
+ 1
607
PROS OF BUDDY
  • 56
    Easy setup
  • 53
    Docker
  • 50
    Continuous Integration
  • 49
    Integrations
  • 46
    Beautiful dashboard
  • 45
    Git hosting
  • 43
    Free
  • 41
    Unlimited pipelines
  • 39
    Backup
  • 39
    Monitoring
  • 37
    Great UX
  • 32
    On-Premises
  • 31
    Awesome support
  • 6
    AWS Integrations
  • 5
    Great UI
  • 3
    Bitbucket integration
  • 3
    Slack integration
  • 3
    Simple deployments
  • 3
    Hosted internally (Enterprise)
  • 3
    Continuous deployment
  • 2
    Github integration
  • 2
    UI and YML configuration
  • 2
    Node.js support
  • 2
    Azure integration
  • 2
    Amazing + free
  • 2
    Fast execution
  • 1
    Shopify integration
  • 1
    Docker support
  • 1
    Gitlab integration
  • 1
    Android support
  • 1
    Pushover integration
  • 1
    DigitalOcean integration
  • 1
    UpCloud integration
  • 1
    Support for build pipelines
  • 0
    New Relic integration
  • 0
    Rollbar integration
  • 0
    Sentry integration
  • 0
    Loggly integration
  • 0
    Datadog integration
  • 0
    Bugsnag integration
  • 0
    Honeybadger integration
  • 0
    Telegram integration
  • 0
    HipChat integration
  • 0
    Discord integration
  • 0
    Pushbulet integration
  • 0
    AWS integration
  • 0
    Slack Integration
  • 0
    Google Cloud integration
  • 0
    Heroku integration
  • 0
    Rackspace integration
  • 0
    Kubernetes support
CONS OF BUDDY
  • 1
    Deleted account after 1 month of not pushing code

related Buddy posts

CDG

I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

See more
Google Cloud Build logo

Google Cloud Build

112
125
2
Continuously build, test, and deploy.
112
125
+ 1
2
PROS OF GOOGLE CLOUD BUILD
  • 1
    Container based
  • 1
    GCP easy integration
CONS OF GOOGLE CLOUD BUILD
  • 2
    Vendor lock-in

related Google Cloud Build posts

Emanuel Evans
Senior Architect at Rainforest QA · | 13 upvotes · 578.2K 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

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
DeployBot logo

DeployBot

89
80
74
Instantly deploy from Github, Bitbucket, or Gitlab without complex scripts, commands or configs.
89
80
+ 1
74
PROS OF DEPLOYBOT
  • 26
    Easy setup
  • 20
    Seamless integrations
  • 17
    Free
  • 10
    Rocks
  • 1
    Docker
CONS OF DEPLOYBOT
  • 1
    Not reliable

related DeployBot posts

Deployer logo

Deployer

52
65
21
Deployment Tool for PHP
52
65
+ 1
21
PROS OF DEPLOYER
  • 8
    Simply to use
  • 7
    Easy to customize
  • 6
    Easy setup
CONS OF DEPLOYER
    Be the first to leave a con

    related Deployer posts

    CDG

    I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

    Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

    As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

    To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

    CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

    Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

    See more
    Cloud 66 logo

    Cloud 66

    32
    31
    83
    Full Stack Container Management as a Service
    32
    31
    + 1
    83
    PROS OF CLOUD 66
    • 13
      Easy provisioning
    • 11
      Easy scaling
    • 10
      Security
    • 8
      Great Support
    • 8
      Monitoring
    • 7
      Container deployments
    • 7
      Backup
    • 6
      Team access control
    • 3
      Turnkey DevOps
    • 3
      The right balance of control and ease-of-development
    • 1
      Command Line Interface
    • 1
      Load balancing
    • 1
      API
    • 1
      Rails Deployments
    • 1
      Kubernetes Management
    • 1
      Kubernetes deployment
    • 1
      Multicloud
    CONS OF CLOUD 66
      Be the first to leave a con

      related Cloud 66 posts